From: Jesse Lackey <jesse@celestialaudio.com>
To: openembedded-devel@lists.openembedded.org
Subject: fakeroot 1.15.1 issues
Date: Thu, 22 Dec 2011 01:08:16 -0800 [thread overview]
Message-ID: <4EF2F380.80704@celestialaudio.com> (raw)
I'm have exactly the same problem. "git pull" says up to date.
I'm continuing on by running "bitbake -k". But things appear to be
indeed broken, by the presumably recent removal of
fakeroot_1.15.1.orig.tar.bz2 from the debian ftp site.
Any assistance greatly appreciated. I'm a total newbie with bitbake and OE.
J
> Christopher Sarra chris.sarra at gmail.com
> Wed Dec 21 20:52:32 CET 2011
> I tried `git pull` but apparently everything is "Already up-to-date." Am I
> missing something else?
>
> Thanks,
> Chris
>
next reply other threads:[~2011-12-22 9:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 9:08 Jesse Lackey [this message]
2011-12-23 9:13 ` fakeroot 1.15.1 issues Marco Cavallini
2011-12-23 22:37 ` Denys Dmytriyenko
2011-12-25 20:11 ` Frans Meulenbroeks
2011-12-26 4:12 ` Denys Dmytriyenko
2012-01-04 10:08 ` Angus Lees
2012-01-17 20:45 ` Tom Rini
2012-01-17 21:04 ` Frans Meulenbroeks
-- strict thread matches above, loose matches on Subject: below --
2011-12-20 14:16 Christopher Sarra
2011-12-21 16:04 ` Tom Rini
2011-12-21 19:52 ` Christopher Sarra
2011-12-22 14:10 ` Marco Cavallini
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=4EF2F380.80704@celestialaudio.com \
--to=jesse@celestialaudio.com \
--cc=openembedded-devel@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