From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Paul D. DeRocco" <pderocco@ix.netcom.com>
Cc: yocto@yoctoproject.org
Subject: Re: My stuff is missing from rootfs
Date: Fri, 16 Aug 2013 10:07:39 +0100 [thread overview]
Message-ID: <1855392.ynQjeqAi5O@helios> (raw)
In-Reply-To: <8D8C809E9ACF41CF9227B7A89C675A27@PAULD>
On Thursday 15 August 2013 15:38:37 Paul D. DeRocco wrote:
> > On Thursday 15 August 2013 13:01:54 Paul D. DeRocco wrote:
> > > This smells like one of those situations where nuking tmp
> > > and rebuilding will fix it, and we'll never know what was wrong. I'll let
> > > you know if that fixes it.
> >
> > If you keep on doing this we'll never figure out what the
> > problem is. Wiping out tmp just removes any way we might have to diagnose
> > the issue.
>
> I didn't wipe it out, I renamed it to something else, so I can switch back
> to it if I need to.
Apologies, I just assumed that's what you meant by "nuking". If there's a bug
or otherwise undesirable behaviour that is causing this problem I'd really
like to figure out what it is so we can fix it for everyone.
> I certainly don't have the faintest idea about how to
> diagnose it, beyond the naive steps I've already taken. And I need to get
> back to my real job, which is writing apps for this system, instead of
> building the distro. If there's anything you can think of that I should
> try, I'd be happy to do so.
You didn't mention in your reply to Saul whether the foo package was mentioned
in log.do_rootfs or installed_pkgs.txt files in your old tmpdir; was it?
> That said, rebuilding tmp (preserving downloads and sstate-cache) did
> indeed fix that problem, but it was replaced with another. Now, do_rootfs
> is failing, complaining that it "cannot satisfy the following dependencies
> for samba: libpam (>= 1.1.6)". Yet there's libpam, version 1.1.6, right
> where it's always been in the metadata. Doing a clean and a cleansstate on
> libpam didn't help.
Does samba.inc used by the samba recipe you are building have a PACKAGECONFIG
line referring to pam? I think that was added recently in meta-oe master (and
shortly to be merged into the meta-oe dylan branch). Without it there will be
a floating dependency on pam, which may account for this latter issue.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-08-16 9:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 18:37 My stuff is missing from rootfs Paul D. DeRocco
2013-08-15 18:55 ` Saul Wold
2013-08-15 19:30 ` Paul D. DeRocco
2013-08-15 19:47 ` Saul Wold
2013-08-15 20:01 ` Paul D. DeRocco
2013-08-15 21:43 ` Paul Eggleton
2013-08-15 22:38 ` Paul D. DeRocco
2013-08-16 0:22 ` Paul D. DeRocco
2013-08-16 9:07 ` Paul Eggleton [this message]
2013-08-16 20:05 ` Paul D. DeRocco
2013-08-15 23:28 ` Mark Hatle
2013-08-16 0:20 ` Paul D. DeRocco
2013-08-16 14:29 ` Mark Hatle
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=1855392.ynQjeqAi5O@helios \
--to=paul.eggleton@linux.intel.com \
--cc=pderocco@ix.netcom.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.