* Panu Matilainen:
> It seems that rpm-4.16.1.2-1.fc33.x86_64 can parse the RPM just
fine.
> But rpm-4.14.3-4.el8.x86_64 does not like it, either.
Based on a quick random sampling, this would appear to be a very
recent thing, the only affected packages I could find (which doesn't
mean others couldn't exist) were built in the last few days, such as
the above and these:
https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everyth...
https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everyth...
...which were all built on Jan 18th. The only recent change to rpm is
the DWARF-5 support but based on changelogs that seems to have landed
the day after, so I dunno.
Here's a non-debug example:
<
https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everyth...
It seems that the corruption only occurs after signing. This package
has the same payload and is fine:
<
https://kojipkgs.fedoraproject.org//packages/NetworkManager/1.30.0/0.2.fc...
It's not the libgomp ABI break (the thing leading to the s390x crashes)
because that NetworkManager build use gcc-11.0.0-0.14.fc34.
Hence my question whether this was a deliberate header format change.
If not, then there's a potential infrastructure issue here, and we need
to investigate this before starting the mass rebuild.
Thanks,
Florian
--
Red Hat GmbH,
https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill