All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: fakeroot fails to build
Date: Wed, 25 Feb 2009 16:04:27 +0100	[thread overview]
Message-ID: <go3mlr$29l$1@ger.gmane.org> (raw)
In-Reply-To: <1235550209.2621.28.camel@andromeda>

On 25-02-09 09:23, Michael 'Mickey' Lauer wrote:
> Am Mittwoch, den 25.02.2009, 08:57 +0100 schrieb Koen Kooi:
>> On 25-02-09 07:53, Mike (mwester) wrote:
>>> fakeroot fails to build -- any idea how we can fix this?
>> By reverting the merge of the sane-defaults branch that got merged with
>> zero review
>
> Ah right, I probably didn't wait long enough.

I think we should get rid of the "silence is approval" dogma, especially 
since I needed to commit this today:

http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&id=d6a0ddf22540c930f8ab9033870eb6509713e5b7

and

http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&id=98238944c784e673cab4691a861f3d9fa61f85a4

Since both automake and fakeroot are pretty important, dare I say 
'core', a simple test would be nice before checking in changes. While 
the automake problem wouldn't have shown up in review, the missing 
fakeroot checksums would have.




  reply	other threads:[~2009-02-25 15:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25  6:53 fakeroot fails to build Mike (mwester)
2009-02-25  7:57 ` Koen Kooi
2009-02-25  8:23   ` Michael 'Mickey' Lauer
2009-02-25 15:04     ` Koen Kooi [this message]
2009-02-25 15:14     ` Mike (mwester)
2009-02-25 15:43       ` OE breakages, was: " Koen Kooi
2009-02-26 13:05         ` Bernhard Guillon
2009-02-27 19:30           ` Rodrigo Vivi
2009-02-25 18:25       ` Minimal distro (was: fakeroot fails to build) Michael 'Mickey' Lauer
2009-02-25 18:59         ` Tom Rini
2009-02-25  8:06 ` fakeroot fails to build Michael 'Mickey' Lauer

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='go3mlr$29l$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 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.