From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: dpkg's admindir: /var/dpkg or /var/lib/dpkg?
Date: Wed, 18 May 2011 08:39:27 -0500 [thread overview]
Message-ID: <4DD3CC0F.7070702@windriver.com> (raw)
In-Reply-To: <1865303E0DED764181A9D882DEF65FB694322A3FD4@shsmsx502.ccr.corp.intel.com>
On 5/18/11 4:27 AM, Cui, Dexuan wrote:
> Hi, I happened to find a bug: in target, "dpkg --list" shows "dpkg-query: failed to open package info file `/var/lib/dpkg/status' for reading: No such file or directory"
>
> Actually the files(status and available) does exist, but not in /var/lib/dpkg/ -- they're in /var/dpkg/. "ln -s /var/dpkg/{status, available} /var/lib/dpkg" can resolve the issue.
>
> grepping '/var/dpkg' shows there are many files(package_deb.bbclass, rootfs_deb.bbclass, populate_sdk_deb.bbclas, apt.conf ) in which '/var/dpkg' is used and /var/lib/dpkg is not used at all.
>
> However, looks dpkg's default admindir is /var/lib/dpkg -- e.g., Ubuntu uses this.
>
> What should we do? Looks fixing the package dpkg's admindir in the do_configure needs the least coding.
I would say that /var/lib/dpkg is the "correct" directory to use. This matches
the behavior on other deb bases systems. (It also mimics other pkg managers who
place their data into /var/lib/...)
--Mark
> Thanks,
> -- Dexuan
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-05-18 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 9:27 dpkg's admindir: /var/dpkg or /var/lib/dpkg? Cui, Dexuan
2011-05-18 13:39 ` Mark Hatle [this message]
2011-05-19 1:48 ` Cui, Dexuan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DD3CC0F.7070702@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox