| Message ID | 20250422131112.2392350-1-ross.burton@arm.com |
|---|---|
| State | New |
| Headers | show |
| Series | autoconf: mangle PV to avoid version-goes-backwards | expand |
Sadly upstream check will report ‘broken’ with this, that’s why I was hesitant to send the update myself. It will start working again when there is a new release (assuming it will sort higher than 2.72e). Alex On Tue 22. Apr 2025 at 15.12, Ross Burton via lists.openembedded.org <ross.burton=arm.com@lists.openembedded.org> wrote: > I previously upgrade autoconf 2.72e (the fifth release candidate) to the > final release 2.72, but unfortunately failed to notice that the version > appears to go backwards as the package managers sort 2.72e _after_ 2.72. > > We could resolve this with an epoch (via PE) but epochs are forever and > this mistake is temporary, so set a convoluted PV to fix the sorting > order that can be removed when the next major release is made. > > [1] oe-core 11ff8dba0ce ("autoconf: upgrade to final 2.72 release") > > Signed-off-by: Ross Burton <ross.burton@arm.com> > --- > meta/recipes-devtools/autoconf/autoconf_2.72.bb | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/meta/recipes-devtools/autoconf/autoconf_2.72.bb > b/meta/recipes-devtools/autoconf/autoconf_2.72.bb > index f2d2781fec9..04b771d05a8 100644 > --- a/meta/recipes-devtools/autoconf/autoconf_2.72.bb > +++ b/meta/recipes-devtools/autoconf/autoconf_2.72.bb > @@ -11,6 +11,10 @@ DEPENDS:remove:class-native = "autoconf-native > automake-native help2man-native" > LIC_FILES_CHKSUM = "file://COPYING;md5=cc3f3a7596cb558bbd9eb7fbaa3ef16c \ > file://COPYINGv3;md5=1ebbd3e34237af26da5dc08a4e440464" > > +# Remove this when upgrading past 2.72, as package managers sort 2.72e > (the > +# fifth release candidate) after 2.72. > +PV = "2.72e+really2.72" > + > SRC_URI = " \ > ${GNU_MIRROR}/autoconf/${BP}.tar.gz \ > file://program_prefix.patch \ > -- > 2.43.0 > > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#215208): > https://lists.openembedded.org/g/openembedded-core/message/215208 > Mute This Topic: https://lists.openembedded.org/mt/112394175/1686489 > Group Owner: openembedded-core+owner@lists.openembedded.org > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ > alex.kanavin@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- > >
On Tue Apr 22, 2025 at 3:11 PM CEST, Ross Burton via lists.openembedded.org wrote: > I previously upgrade autoconf 2.72e (the fifth release candidate) to the > final release 2.72, but unfortunately failed to notice that the version > appears to go backwards as the package managers sort 2.72e _after_ 2.72. > > We could resolve this with an epoch (via PE) but epochs are forever and > this mistake is temporary, so set a convoluted PV to fix the sorting > order that can be removed when the next major release is made. > > [1] oe-core 11ff8dba0ce ("autoconf: upgrade to final 2.72 release") > > Signed-off-by: Ross Burton <ross.burton@arm.com> > --- It looks like this will be used in the fetch URL and so the fetch step fails: ERROR: autoconf-2.72e+really2.72-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export PATH="/srv/pokybuild/yocto-worker/a-full/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/srv/pokybuild/yocto-worker/a-full/build/scripts:/srv/pokybuild/yocto-worker/a-full/build/build/tmp/work/core2-64-poky-linux/autoconf/2.72e+really2.72/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/srv/pokybuild/yocto-worker/a-full/build/build/tmp/work/core2-64-poky-linux/autoconf/2.72e+really2.72/recipe-sysroot/usr/bin/crossscripts:/srv/pokybuild/yocto-worker/a-full/build/build/tmp/work/core2-64-poky-linux/autoconf/2.72e+really2.72/recipe-sysroot-native/usr/sbin:/srv/pokybuild/yocto-worker/a-full/build/build/tmp/work/core2-64-poky-linux/autoconf/2.72e+really2.72/recipe-sysroot-native/usr/bin:/srv/pokybuild/yocto-worker/a-full/build/build/tmp/work/core2-64-poky-linux/autoconf/2.72e+really2.72/recipe-sysroot-native/sbin:/srv/pokybuild/yocto-worker/a-full/build/build/tmp/work/core2-64-poky-linux/autoconf/2.72e+really2.72/recipe-sysroot-native/bin:/srv/pokybuild/yocto-worker/a-full/build/bitbake/bin:/srv/pokybuild/yocto-worker/a-full/build/build/tmp/hosttools"; export HOME="/srv/pokybuild"; /usr/bin/env wget --tries=2 --timeout=100 --output-document=/srv/autobuilder/valkyrie.yocto.io/current_sources/autoconf-2.72e+really2.72.tar.gz.tmp --continue --directory-prefix=/srv/autobuilder/valkyrie.yocto.io/current_sources 'https://ftp.gnu.org/gnu/autoconf/autoconf-2.72e+really2.72.tar.gz' --progress=dot --verbose failed with exit code 8, see logfile for output ERROR: autoconf-2.72e+really2.72-r0 do_fetch: Bitbake Fetcher Error: FetchError('Unable to fetch URL from any source.', 'https://ftp.gnu.org/gnu/autoconf/autoconf-2.72e+really2.72.tar.gz') https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/1435/steps/13/logs/stdio
On 22 Apr 2025, at 17:05, Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> wrote: > > On Tue Apr 22, 2025 at 3:11 PM CEST, Ross Burton via lists.openembedded.org wrote: >> I previously upgrade autoconf 2.72e (the fifth release candidate) to the >> final release 2.72, but unfortunately failed to notice that the version >> appears to go backwards as the package managers sort 2.72e _after_ 2.72. >> >> We could resolve this with an epoch (via PE) but epochs are forever and >> this mistake is temporary, so set a convoluted PV to fix the sorting >> order that can be removed when the next major release is made. >> >> [1] oe-core 11ff8dba0ce ("autoconf: upgrade to final 2.72 release") >> >> Signed-off-by: Ross Burton <ross.burton@arm.com> >> --- > > It looks like this will be used in the fetch URL and so the fetch step > fails: Yes, of course. Obvious lack of retesting after rewriting the patch again. Sorry, v2 coming shortly. Ross
diff --git a/meta/recipes-devtools/autoconf/autoconf_2.72.bb b/meta/recipes-devtools/autoconf/autoconf_2.72.bb index f2d2781fec9..04b771d05a8 100644 --- a/meta/recipes-devtools/autoconf/autoconf_2.72.bb +++ b/meta/recipes-devtools/autoconf/autoconf_2.72.bb @@ -11,6 +11,10 @@ DEPENDS:remove:class-native = "autoconf-native automake-native help2man-native" LIC_FILES_CHKSUM = "file://COPYING;md5=cc3f3a7596cb558bbd9eb7fbaa3ef16c \ file://COPYINGv3;md5=1ebbd3e34237af26da5dc08a4e440464" +# Remove this when upgrading past 2.72, as package managers sort 2.72e (the +# fifth release candidate) after 2.72. +PV = "2.72e+really2.72" + SRC_URI = " \ ${GNU_MIRROR}/autoconf/${BP}.tar.gz \ file://program_prefix.patch \
I previously upgrade autoconf 2.72e (the fifth release candidate) to the final release 2.72, but unfortunately failed to notice that the version appears to go backwards as the package managers sort 2.72e _after_ 2.72. We could resolve this with an epoch (via PE) but epochs are forever and this mistake is temporary, so set a convoluted PV to fix the sorting order that can be removed when the next major release is made. [1] oe-core 11ff8dba0ce ("autoconf: upgrade to final 2.72 release") Signed-off-by: Ross Burton <ross.burton@arm.com> --- meta/recipes-devtools/autoconf/autoconf_2.72.bb | 4 ++++ 1 file changed, 4 insertions(+)