All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John Willis" <John.Willis@Distant-earth.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: beagleboard-demo-image, and the evil that is "gnome-games"
Date: Sun, 17 Jan 2010 18:27:33 -0000	[thread overview]
Message-ID: <009501ca97a2$bd9bc940$38d35bc0$@Willis@Distant-earth.com> (raw)
In-Reply-To: <hivjon$vmv$1@ger.gmane.org>

> >   that package was the final obstacle to getting a BB-demo-image
> > build.  other packages that were failing -- e2fsprogs, mplayer --
> > have recently been fixed, leaving gnome-games as the sole remaining
> > cause of build grief.
> >
> >   a suggestion -- until the issue with gnome-games is resolved, why
> > not just remove its inclusion from the bb-demo-image task?  i'm being
> > quite serious -- it's obviously not a critical package, and if it's
> > the only thing keeping people from building and testing the OE dev
> > branch for the beagleboard, take it out so folks can get back to
> > testing.

Just to chip in on this,

I build 3 or 4 images daily that feature gnome-games (inc. bb-demo) on
several build hosts (ok, none are Fedora based, mostly DEB based setups). 

Can't say I have had any build issues with gnome-games on any of those
setups (gnome-system-tools is my nemesis today and that's no in bb-demo
;-)).

I personally don't favour taking packages out of an image if there are build
issues on a small subset of systems. I think Phil (or someone else) suggest
you consider contributing your build logs to OESTATS/TinderBox
(http://wiki.openembedded.net/index.php/How_do_I_send_automatic_success_and_
failure_reports) at least with that setup you leave a reference the failing
logs in bug reports/mails so people can have a look into all the gory
details :).

Cheers,

John






  reply	other threads:[~2010-01-17 18:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-17 16:47 beagleboard-demo-image, and the evil that is "gnome-games" Robert P. J. Day
2010-01-17 16:54 ` Martin Jansa
2010-01-17 17:06   ` Robert P. J. Day
2010-01-17 17:18     ` Paul Menzel
2010-01-17 16:57 ` Paul Menzel
2010-01-17 18:09 ` Koen Kooi
2010-01-17 18:27   ` John Willis [this message]
2010-01-17 20:20     ` Robert P. J. Day
2010-01-17 21:24       ` Paul Menzel
2010-01-17 19:16   ` Robert P. J. Day
2010-01-17 19:43     ` Rolf Leggewie
     [not found]   ` <37208.8112672374$1263753418@news.gmane.org>
2010-01-17 19:43     ` Rolf Leggewie
2010-01-17 20:09       ` Robert P. J. Day
2010-01-17 20:15         ` Rolf Leggewie
2010-01-17 21:33           ` Paul Menzel

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='009501ca97a2$bd9bc940$38d35bc0$@Willis@Distant-earth.com' \
    --to=john.willis@distant-earth.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 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.