| Message ID | 20250429194325.4184267-1-ross.burton@arm.com |
|---|---|
| State | New |
| Headers | show |
| Series | autoconf: set PKGV to avoid version-goes-backwards | expand |
diff --git a/meta/recipes-devtools/autoconf/autoconf_2.72.bb b/meta/recipes-devtools/autoconf/autoconf_2.72.bb index f2d2781fec9..b599f270c79 100644 --- a/meta/recipes-devtools/autoconf/autoconf_2.72.bb +++ b/meta/recipes-devtools/autoconf/autoconf_2.72.bb @@ -24,6 +24,10 @@ SRC_URI:append:class-native = " file://no-man.patch" SRC_URI[sha256sum] = "afb181a76e1ee72832f6581c0eddf8df032b83e2e0239ef79ebedc4467d92d6e" +# Remove this when upgrading past 2.72, as package managers sort 2.72e (the +# fifth release candidate) after 2.72. +PKGV = "2.72e+really${PV}" + RDEPENDS:${PN} = "m4 gnu-config \ perl \ perl-module-bytes \
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. We could set a convoluted PV but that gets messy as it then means SRC_URI needs to set manually. Instead, set a convoluted PKGV to fix the sorting order in a way that only alters the output packages and nothing else, which 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(+)