From: John Weber <rjohnweber@gmail.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: [Bug 4037] neard 0.9 build fails during package_write_rpm
Date: Sat, 16 Mar 2013 19:44:36 -0500 [thread overview]
Message-ID: <514511F4.7070406@gmail.com> (raw)
In-Reply-To: <bug-4037-472-euKlqFTkqI@https.bugzilla.yoctoproject.org/>
FYI - I reported this bug when neard failed to build. This affected
fsl-image-test, which depends on packagegroup-base, which adds neard.
I think that packagegroup-base should be called packagegroup-universe. It
brings in so many packages that I would not consider to be 'base' packages.
-------- Original Message --------
Subject: [Bug 4037] neard 0.9 build fails during package_write_rpm
Date: Sat, 16 Mar 2013 17:10:53 +0000
From: bugzilla-daemon@yoctoproject.org
To: rjohnweber@gmail.com
Richard Purdie <mailto:richard.purdie@linuxfoundation.org> changed bug 4037
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=4037>
What Removed Added
Status NEW RESOLVED
CC richard.purdie@linuxfoundation.org
Resolution --- FIXED
*Comment # 1 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=4037#c1> on bug
4037 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=4037> from Richard
Purdie <mailto:richard.purdie@linuxfoundation.org> *
Fixed in master with
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=b5e5d25c25f30db1f9855e24afef9d8f0bb77d35
--------------------------------------------------------------------------------
You are receiving this mail because:
* You reported the bug.
next parent reply other threads:[~2013-03-17 0:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-4037-472-euKlqFTkqI@https.bugzilla.yoctoproject.org/>
2013-03-17 0:44 ` John Weber [this message]
2013-03-18 1:51 ` [Bug 4037] neard 0.9 build fails during package_write_rpm Otavio Salvador
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=514511F4.7070406@gmail.com \
--to=rjohnweber@gmail.com \
--cc=meta-freescale@yoctoproject.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.