From: Mike Looijmans <mike.looijmans@topic.nl>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [CONSOLIDATED PULL 00/41] Selected Updates and fixes
Date: Sat, 23 Feb 2013 10:33:11 +0100 [thread overview]
Message-ID: <51288CD7.2070800@topic.nl> (raw)
In-Reply-To: <CAJTo0LaWCAtjiQWq5=FUWq68ty+O2fPYJ8DLLPT-35zqwWn6eg@mail.gmail.com>
On 02/22/2013 10:52 AM, Burton, Ross wrote:
> On 22 February 2013 07:11, Mike Looijmans <mike.looijmans@topic.nl> wrote:
>> If there's anything I can do to help let me know. Is this now blocking the
>> integration?
>>
>> I haven't found any issues with the dependencies, but I've only tested with
>> the util-linux-mount/umount pacakges, and the sfdisk package (which does not
>> depend on libmount).
>
> Can you verify that util-linux-fsck is no longer depending on
> util-linux with this patch? Maybe I've got a confused build area.
This is what opkg reports on my running systems, with the libmount patch
applied, looks fine to me, a few require libmount1, and none require
util-linux itself. For example:
Package: util-linux-mount
Version: 2.22.2-r1
Depends: libmount1 (>= 2.22.2), update-alternatives-cworth, libc6 (>= 2.17)
Package: util-linux-fdisk
Version: 2.22.2-r1
Depends: update-alternatives-cworth, libblkid1 (>= 2.22.2), libc6 (>= 2.17)
Package: util-linux-fsck
Version: 2.22.2-r1
Depends: libmount1 (>= 2.22.2), update-alternatives-cworth, libblkid1
(>= 2.22.2), libc6 (>= 2.17)
--
Mike Looijmans - Topic Automation
next prev parent reply other threads:[~2013-02-23 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 16:31 [CONSOLIDATED PULL 00/41] Selected Updates and fixes Saul Wold
2013-02-21 16:39 ` Burton, Ross
2013-02-22 7:11 ` Mike Looijmans
2013-02-22 9:52 ` Burton, Ross
2013-02-23 9:33 ` Mike Looijmans [this message]
2013-02-23 10:17 ` Burton, Ross
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=51288CD7.2070800@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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