From: Mike Looijmans <mike.looijmans@topic.nl>
To: openembedded-core@lists.openembedded.org
Subject: Re: [oe-commits] MiLo : util-linux: Add package for libmount
Date: Wed, 06 Mar 2013 09:08:30 +0100 [thread overview]
Message-ID: <5136F97E.1030906@topic.nl> (raw)
In-Reply-To: <20130306062358.GC14869@jama>
On 03/06/2013 07:23 AM, Martin Jansa wrote:
> On Thu, Feb 28, 2013 at 11:15:51PM +0000, git@git.openembedded.org wrote:
>> Module: openembedded-core.git
>> Branch: master
>> Commit: 2e79110e31da940728d42411cad3d019d570fc31
>> URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=2e79110e31da940728d42411cad3d019d570fc31
>>
>> Author: MiLo <milo-software@users.sourceforge.net>
>> Date: Tue Feb 19 18:23:15 2013 +0100
>>
>> util-linux: Add package for libmount
>>
>> The libmount shared library was part of util-linux. This caused
>> util-linux-mount to RDEPEND on util-linux, so including that would
>> also drag in all of util-linux and all its recommendations.
>>
>> To break this circular dependency, add a libmount package that holds
>> the libmount.so.* files, just like the other libraries built by util-
>> linux.
>
> Breaks upgrade path:
>
> * check_data_file_clashes: Package libmount1 wants to install file
> * /lib/libmount.so.1.1.0
> But that file is already provided by package * util-linux
> * check_data_file_clashes: Package libmount1 wants to install file
> * /lib/libmount.so.1
> But that file is already provided by package * util-linux
>
> RREPLACES is probably needed.
Indeed, I can reproduce that too. But I'm not sure how to fix this, as I
cannot bluntly claim that libmount replaces util-linux, because it
really doesn't. So RREPLACES_util-linux-libmount = "util-linux" is
probably not the way to go here. Or is it? It does not "feel" right
anyway, because the old situation should have never happened.
Prior to the libmount patch, it was not possible to remove util-linux
from any system that installed util-linux-mount (or any other that
requires libmount), without applying "force". And util-linux itself
depends on packages that in turn depend on util-linux. That's the circle
I wanted to break out of.
How does one properly inform opkg that a file has moved from one
(installed) package to another?
>>
>> Signed-off-by: MiLo <milo-software@users.sourceforge.net>
>> Signed-off-by: Saul Wold <sgw@linux.intel.com>
>>
>> ---
>>
>> meta/recipes-core/util-linux/util-linux.inc | 3 +++
>> meta/recipes-core/util-linux/util-linux_2.22.2.bb | 2 +-
>> 2 files changed, 4 insertions(+), 1 deletions(-)
>>
>> diff --git a/meta/recipes-core/util-linux/util-linux.inc b/meta/recipes-core/util-linux/util-linux.inc
>> index 10439c0..bd7b089 100644
>> --- a/meta/recipes-core/util-linux/util-linux.inc
>> +++ b/meta/recipes-core/util-linux/util-linux.inc
>> @@ -31,6 +31,7 @@ SRC_URI = "${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-lin
>> PACKAGES =+ "util-linux-agetty util-linux-fdisk util-linux-cfdisk util-linux-sfdisk \
>> util-linux-swaponoff util-linux-losetup util-linux-umount \
>> util-linux-mount util-linux-readprofile util-linux-libblkid \
>> + util-linux-libmount util-linux-libmount-dev \
>> util-linux-libblkid-dev util-linux-libuuid util-linux-libuuid-dev \
>> util-linux-uuidgen util-linux-lscpu util-linux-fsck util-linux-blkid \
>> util-linux-mkfs util-linux-mcookie util-linux-reset"
>> @@ -64,6 +65,8 @@ FILES_util-linux-reset = "${base_bindir}/reset"
>>
>> FILES_util-linux-libblkid = "${base_libdir}/libblkid.so.*"
>> FILES_util-linux-libblkid-dev = "${base_libdir}/libblkid.so ${base_libdir}/libblkid.la ${includedir}/blkid ${libdir}/pkgconfig/blkid.pc"
>> +FILES_util-linux-libmount = "${base_libdir}/libmount.so.*"
>> +FILES_util-linux-libmount-dev = "${base_libdir}/libmount.so ${base_libdir}/libmount.la ${includedir}/libmount ${libdir}/pkgconfig/mount.pc"
>> FILES_util-linux-libuuid = "${base_libdir}/libuuid.so.*"
>> FILES_util-linux-libuuid-dev = "${base_libdir}/libuuid.so ${base_libdir}/libuuid.la ${includedir}/uuid ${libdir}/pkgconfig/uuid.pc"
>> FILES_util-linux-lscpu = "${bindir}/lscpu"
>> diff --git a/meta/recipes-core/util-linux/util-linux_2.22.2.bb b/meta/recipes-core/util-linux/util-linux_2.22.2.bb
>> index dd95573..f91784b 100644
>> --- a/meta/recipes-core/util-linux/util-linux_2.22.2.bb
>> +++ b/meta/recipes-core/util-linux/util-linux_2.22.2.bb
>> @@ -1,5 +1,5 @@
>> MAJOR_VERSION = "2.22"
>> -PR = "r0"
>> +PR = "r1"
>> require util-linux.inc
>>
>> # note that `lscpu' is under GPLv3+
>>
>>
>> _______________________________________________
>> Openembedded-commits mailing list
>> Openembedded-commits@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-commits
>
--
Mike Looijmans - Topic Automation
next prev parent reply other threads:[~2013-03-06 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130228231551.3998F5022B@opal>
2013-03-06 6:23 ` [oe-commits] MiLo : util-linux: Add package for libmount Martin Jansa
2013-03-06 8:08 ` Mike Looijmans [this message]
2013-03-19 14:45 ` Busybox mdev INITSCRIPT_PARAMS gets lost Mike Looijmans
2013-04-10 10:07 ` Burton, Ross
2013-04-10 10:24 ` Burton, Ross
2013-04-10 10:58 ` Mike Looijmans
2013-03-22 11:37 ` [oe-commits] MiLo : util-linux: Add package for libmount Martin Jansa
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=5136F97E.1030906@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-core@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