Comments
tis
This likely shouldn't be pushed to epel because of https://bugzilla.redhat.com/show_bug.cgi?id=2374941
This likely shouldn't be pushed to 10.0 because of https://bugzilla.redhat.com/show_bug.cgi?id=2374345
Don't push this update, this is bigger release number than c10s version and you are not supposed to update this any more on epel.
mock 5.9 works.
This change breaks compatibility with all Centos Stream 9 based operating systems:
Make "dnf4" equivalent to "dnf"
There is no dnf4 in c9s or rhel9, only /usr/bin/dnf
INFO: Using 'dnf4' instead of 'dnf'
WARNING! WARNING! WARNING!
You are building package for distribution which uses DNF. However your system
does not support DNF. You can continue with DNF4, which will likely succeed,
but the installed chroot may look a little different.
1. Please consider --bootstrap-chroot option, or
2. install DNF on your host system.
Found another package breaking because of so version bump. That is hypre.
This update breaks armadillo because there is so version bump in SuperLU. Please compile armadillo and add to this update.
There is a wrong YEAR in changelog.
This is not complete update, matching python-rpmautospec-core is missing. (0.1.4-1.el9) - there is build in koji but it was not added to update.
I see there are builds of both on koji. Was this just a mistake and those two new packages were not included in this update?
This update is missing it's build dependencies.
Build dependencies qhexedit2 and qcustomplot are not available on epel8.
Sounds good.
It is not a very good idea to push this update. Reason being that python-pyside2 is already broken on centos stream 9. And because qt5-qtbase was updated there, python-pyside2 can't be rebuild any more (upstream of pyside2 is broken).
This is dead end.
I'm not adding bad karma, just warning about future issues requiring to retire whole pyside2 dependant software stuff.
Thank you for your effort!
I can understand - but how to fix situation? Should previous update be pulled back instead?
This update includes packages which can't even be build after FEDORA-EPEL-NEXT-2023-1215583109 went to epel9-next stable.
This is completely incompatible update with already published kf5 packages.
Bug in the package, Release does not have %{?dist}.
libabigail was added to rhel 9.2.
Is it intentional to move binary package name from python3-backoff to python-backoff?
Then it should be build with lower release number than rhel.