From: "Luca Bocassi" <luca.boccassi@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Cc: bluelightning@bluelightning.org,
Kory Maincent <kory.maincent@bootlin.com>
Subject: Re: [PATCH v9] util-linux: split uuid in separate recipe to allow bootstrapping
Date: Thu, 11 Mar 2021 10:15:02 +0000 [thread overview]
Message-ID: <291a86bde929406603821b08b1fe36cfecf19103.camel@gmail.com> (raw)
In-Reply-To: <539920c0108d13a48eb63650be96c97435c11dca.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3837 bytes --]
On Wed, 2021-03-10 at 18:28 +0000, Luca Boccassi wrote:
> On Tue, 2021-03-09 at 23:43 +0000, Richard Purdie wrote:
> > On Tue, 2021-03-09 at 13:56 +0000, luca.boccassi@gmail.com wrote:
> > > From: Luca Boccassi <luca.boccassi@microsoft.com>
> > >
> > > Recently util-linux gained an (optional) build dependency on libcryptsetup.
> > > But libcryptsetup build-depends on util-linux for blkid (optional, can be disabled)
> > > and uuid (mandatory).
> > > Split out util-linux-uuid in a different recipe to break the cycle.
> > >
> > > https://github.com/karelzak/util-linux/pull/898
> > >
> > > Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com>
> > > ---
> > > v1: util-linux 2.35 is not out yet, but I'd like to get the preparatory work
> > > underway as I'm not sure if this is the best approach or if there are
> > > alternatives. Suggestions and comments very welcome. Thanks!
> > > v2: changed packages names to reflect old ones (eg: libuuid1 -> util-linux-libuuid)
> > > and leave uuid build enable in main recipe to allow for uuidgen build to happen,
> > > as it does not have its own autoconf switch. Delete the library manualy from
> > > the main recipe after build instead, and add dependency.
> > > Might help to break loop python3 -> util-linux -> libselinux -> python3, as it's
> > > only libuuid that is needed, see https://lists.yoctoproject.org/g/yocto/message/47570
> > > v3: rebased and refactored to have a common util-linux.inc file
> > > v4: added RDEPENDS on util-linux-libuuid on various packages to fix QA warnings
> > > v5: remove RDEPENDS and instead have util-linux RDEPEND on util-linux-uuid.
> > > Removed PACKAGES_remove and instead filter out libuuid via the package generation
> > > regex.
> > > Rebased on util-linux 2.36.2.
> > > v6: install libuuid.a in libuuid-dev
> > > change rdepends on uuid to use binary package rather than source
> > > add rdepends on uuid-dev to libuuid-dev
> > > remove rprovides of libuuid-dev from uuid-dev
> > > v7: do not use '_append' for RDEPENDS, as it is not supported by BBCLASSEXTEND, use
> > > simply '+='
> > > v8: added missing libuuid-staticdev package
> > > remove libx32/libuuid* too
> > > v9: set RECIPE_MAINTAINER_pn-util-linux-uuid, same value as RECIPE_MAINTAINER_pn-util-linux
> >
> > Sorry, there are still issues:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/3207
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1608
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/3159
> >
> > :(
> >
> > I really want to get this into the release but we're past feature freeze and
> > running out of opportunity as each broken test run is delaying other patches.
>
> No problem at all, it's absolutely fine to postpone, I am in no
> immediate rush as I have local backports in use. As long as we get
> things sorted at some point it's all good for me, so please don't delay
> other patches because of this.
>
> > I'm a little unclear if debian renaming was allowed before the split and if
> > so, why it is disabled in the split version. I suspect there is a missing
> > MLPREFIX somewhere causing the multilib issue too.
>
> I do not remember why the DEBIAN_NOAUTONAME was added at this point.
> I'll try to send a new version tomorrow.
So without DEBIAN_NOAUTONAME these are the package names:
libuuid1-2.36.2-r0.core2_64.rpm
libuuid-dbg-2.36.2-r0.core2_64.rpm
libuuid-dev-2.36.2-r0.core2_64.rpm
util-linux-uuid-src-2.36.2-r0.core2_64.rpm
that's going to be a problem as they don't match anymore, right? Since
they used to be util-linux-libuuid, etc. Although the poky image build
completed just fine...
--
Kind regards,
Luca Boccassi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 499 bytes --]
next prev parent reply other threads:[~2021-03-11 10:15 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 20:13 [PATCH] util-linux: split uuid in separate recipe to allow bootstrapping luca.boccassi
2019-12-05 23:29 ` Ross Burton
2019-12-09 16:24 ` [PATCH v2] " luca.boccassi
2020-11-23 13:28 ` [PATCH v3] " Luca Bocassi
2020-12-10 15:52 ` [OE-core] " Richard Purdie
2020-12-10 18:47 ` Luca Boccassi
2020-12-10 20:04 ` Richard Purdie
2020-12-11 9:51 ` Luca Boccassi
2020-12-11 16:54 ` Richard Purdie
2020-12-14 16:32 ` Luca Boccassi
2020-12-10 18:46 ` [PATCH v4] " Luca Bocassi
2021-01-19 20:52 ` Richard Purdie
2021-01-19 23:13 ` [OE-core] " Paul Eggleton
2021-01-19 23:23 ` Richard Purdie
2021-01-19 23:28 ` Paul Eggleton
2021-02-25 15:31 ` Luca Bocassi
2021-02-25 15:30 ` [PATCH v5] " Luca Bocassi
2021-02-26 19:02 ` [OE-core] " Khem Raj
2021-03-02 19:01 ` Luca Bocassi
2021-02-27 14:52 ` Alexandre Belloni
2021-02-27 15:08 ` Alexandre Belloni
2021-02-27 15:15 ` Alexandre Belloni
2021-03-02 17:31 ` Luca Bocassi
2021-03-02 18:49 ` Alexandre Belloni
2021-03-03 22:30 ` Richard Purdie
2021-03-04 12:05 ` Luca Bocassi
2021-03-04 12:27 ` [PATCH v6] " Luca Bocassi
2021-03-05 0:13 ` Richard Purdie
2021-03-05 11:03 ` Luca Bocassi
2021-03-05 11:02 ` [PATCH v7] " Luca Bocassi
2021-03-08 19:29 ` Richard Purdie
2021-03-09 11:07 ` Luca Bocassi
2021-03-09 11:18 ` [OE-core] " Kory Maincent
2021-03-09 13:26 ` Luca Bocassi
2021-03-09 13:47 ` Kory Maincent
2021-03-09 13:48 ` Richard Purdie
2021-03-09 13:56 ` Luca Bocassi
2021-03-09 11:13 ` [PATCH v8] " Luca Bocassi
2021-03-09 13:56 ` [PATCH v9] " Luca Bocassi
2021-03-09 23:43 ` Richard Purdie
2021-03-10 18:28 ` Luca Bocassi
2021-03-11 10:15 ` Luca Bocassi [this message]
2021-03-11 10:31 ` Richard Purdie
2021-03-11 14:37 ` Luca Bocassi
2021-03-11 14:38 ` [PATCH v10] " Luca Bocassi
2021-03-11 14:44 ` Richard Purdie
2021-03-11 15:10 ` Luca Bocassi
2021-03-11 15:09 ` [PATCH v11] " Luca Bocassi
2021-03-14 22:10 ` Richard Purdie
2021-03-15 10:44 ` Luca Bocassi
2021-03-15 10:49 ` Richard Purdie
2021-03-15 11:50 ` Luca Bocassi
2021-03-15 12:21 ` Richard Purdie
2021-03-15 13:04 ` Luca Bocassi
2021-03-15 13:55 ` [OE-core] " Martin Jansa
2021-03-15 13:57 ` Richard Purdie
[not found] ` <166C88B2CBAB1BAF.20509@lists.openembedded.org>
2021-03-15 21:51 ` Richard Purdie
2021-03-24 16:52 ` Scott Branden
2021-03-24 17:03 ` Luca Boccassi
2021-03-24 17:37 ` Richard Purdie
2021-03-24 17:52 ` Luca Bocassi
2021-03-25 9:17 ` Oleksiy Obitotskyy
2021-03-25 9:34 ` Richard Purdie
2021-03-25 9:48 ` Luca Bocassi
2021-03-25 14:22 ` Peter Kjellerstedt
2021-03-25 14:27 ` Richard Purdie
2021-03-25 15:45 ` Luca Bocassi
2021-03-25 16:01 ` Khem Raj
2021-03-25 16:19 ` Peter Kjellerstedt
2021-03-25 16:51 ` Richard Purdie
2021-03-26 18:06 ` Peter Kjellerstedt
2021-03-26 18:12 ` Richard Purdie
2021-03-26 18:22 ` Andre McCurdy
2019-12-09 16:33 ` [PATCH] " Luca Boccassi
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=291a86bde929406603821b08b1fe36cfecf19103.camel@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=bluelightning@bluelightning.org \
--cc=kory.maincent@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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