From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <ross.burton@arm.com>, <openembedded-core@lists.openembedded.org>
Cc: <koen.kooi@oss.qualcomm.com>
Subject: Re: [OE-core] [PATCH] autoconf: mangle PV to avoid version-goes-backwards
Date: Tue, 22 Apr 2025 18:05:08 +0200 [thread overview]
Message-ID: <D9DANIBXMJQM.21HMU2B4AA96R@bootlin.com> (raw)
In-Reply-To: <20250422131112.2392350-1-ross.burton@arm.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
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-04-22 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 13:11 [PATCH] autoconf: mangle PV to avoid version-goes-backwards Ross Burton
2025-04-22 14:05 ` [OE-core] " Alexander Kanavin
2025-04-22 16:05 ` Mathieu Dubois-Briand [this message]
2025-04-22 16:06 ` Ross Burton
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=D9DANIBXMJQM.21HMU2B4AA96R@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=koen.kooi@oss.qualcomm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.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