From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] util-linux-ng.inc, e2fsprogs.inc: Use update-alternatives for uuidd.
Date: Thu, 2 Dec 2010 16:50:36 +0100 [thread overview]
Message-ID: <20101202155036.GD20482@excalibur.local> (raw)
In-Reply-To: <4CF6FF0A.6090505@gmail.com>
Hello.
On Thu, 2010-12-02 at 12:36, Graham Gower wrote:
> Util-linux-ng put uuidd in ${sbindir}, e2fsprogs put it in ${base_sbindir}.
> This change puts both in ${base_sbindir}.
>
> Fixes a conflict when DISTRO=micro.
>
> | Collected errors:
> | * check_data_file_clashes: Package util-linux-ng wants to install file /mnt/oe/tmp/rootfs/native-sdk-image/sbin/uuidd
> | But that file is already provided by package * e2fsprogs
>
> Signed-off-by: Graham Gower <graham.gower@gmail.com>
I took all of your patches but the two automake and the one bind patch. Khem
reviewed and acked them all.
If I missed one please let me know. Patchwork is down right now and keeping the
overview is a bit of a hassle. :)
regards
Stefan Schmidt
prev parent reply other threads:[~2010-12-02 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 2:06 [PATCH] util-linux-ng.inc, e2fsprogs.inc: Use update-alternatives for uuidd Graham Gower
2010-12-02 15:50 ` Stefan Schmidt [this message]
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=20101202155036.GD20482@excalibur.local \
--to=stefan@datenfreihafen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox