From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: should i submit detailed bugs for e2fsprogs and gnome-games?
Date: Thu, 17 Dec 2009 13:26:45 -0500 [thread overview]
Message-ID: <4B2A77E5.1040804@balister.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0912171137010.30166@localhost>
On 12/17/2009 11:39 AM, Robert P. J. Day wrote:
>
> just trying a beagleboard-demo-image build on the dev branch, last
> attempt still produced failed builds for:
>
> * e2fsprogs
> * gnome-games
>
> i don't see that the latest pull would change any of that, but i'm
> trying it anyway. if those two packages still fail, should i supply
> details? (fully-updated fedora 12, as always).
>
> philip? are you seeing the same things? i'll verify that i haven't
> done anything weird in my shell environment that might be causing
> this.
I saw the gnome-games problem. Steve says he has a later version in his
repo, when he figure out some other things we hope that update solves
the problem.
Philip
>
> rday
> --
>
> ========================================================================
> Robert P. J. Day Waterloo, Ontario, CANADA
>
> Linux Consulting, Training and Kernel Pedantry.
>
> Web page: http://crashcourse.ca
> Twitter: http://twitter.com/rpjday
> ========================================================================
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2009-12-17 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 16:39 should i submit detailed bugs for e2fsprogs and gnome-games? Robert P. J. Day
2009-12-17 18:26 ` Philip Balister [this message]
2009-12-17 19:02 ` Robert P. J. Day
2009-12-19 12:37 ` Paul Menzel
2009-12-19 13:01 ` Robert P. J. Day
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=4B2A77E5.1040804@balister.org \
--to=philip@balister.org \
--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 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.