[Bug 1020833] Re: the filename /var/dpkg/info/e2fslibs.list does not match

Dmitrijs Ledkovs launchpad at surgut.co.uk
Tue Jul 10 03:23:54 UTC 2012


Let me elaborate.

/var/lib/dpkg/* is internal and private to dpkg state/database. Parsing
/var/lib/dpkg/* externally is not a supported, nor it is a guaranteed
interface. Therefore this bug is marked as invalid.

Quantal, Wheezy and Sid have a major new dpkg version (w.r.t. internal
state/database structures), hence the file names are different there.

Can you please show how the file names of internal data structures you
described above affect or introduce bugs in higher level tools: e.g.
dpkg, dpkg-query, apt, aptitude, etc. ?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dpkg in Ubuntu.
https://bugs.launchpad.net/bugs/1020833

Title:
  the filename /var/dpkg/info/e2fslibs.list does not match

Status in “dpkg” package in Ubuntu:
  Invalid
Status in “e2fsprogs” package in Ubuntu:
  Invalid

Bug description:
  Wile investigating package information i found that i have about 400
  packages wich do not have the correct
  /var/lib/dpkg/info/packagename.list. (and md5sums file)

  Is there a specific reason for not naming the list file as the
  packagename as shown by dpkg -l, but instead e.g. creating
  /varlib/dpkg/info/e2fslibs:amd64.list?

  This does not seem consistent.

  I would expect that the packagename should be e2flibs:amd64 wich has a
  corresponding /var/lib/dpkg/info/e2fslibs:amd64.list or on i386
  e2fslibs:i386 with the corresponding name
  /var/lib/dpkg/info/e2fslibs:i386.list

  Regards,

  William van de Velde

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1020833/+subscriptions




More information about the foundations-bugs mailing list