Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: .dev broken after gettext changes
Date: Thu, 09 Oct 2008 10:01:37 +0200	[thread overview]
Message-ID: <gckdp2$qo7$1@ger.gmane.org> (raw)

Hi,

Somewhere last night OE started giving

ERROR: Unbuildable tasks were found.
These are usually caused by circular dependencies and any circular 
dependency chains found will be printed below. Increase the debug level 
to see a list of unbuildable tasks.

Thanks to the autobuild we can see that last good commit is:

http://amethyst.openembedded.net/oe/viewmtn/viewmtn.py/revision/info/f2ebdb1826372581987a96a662d30d97b544c438

and this one is bad:

http://amethyst.openembedded.net/oe/viewmtn/viewmtn.py/revision/info/9f79c6b2ba1ff673c6a3fa4d02579b720046d1cf

So inbetween those commits OE became unbuildable.





             reply	other threads:[~2008-10-09  8:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09  8:01 Koen Kooi [this message]
2008-10-09  9:40 ` .dev broken after gettext changes Leon Woestenberg
2008-10-09 11:54   ` Koen Kooi

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='gckdp2$qo7$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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