Automatic check for bodhi updates not to break RPM dependencies

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 07. 11. 23 12:17, Sandro Mani wrote:
Hi

Due to an unfortunate oversight of an incorrect branch merge a couple of months ago, a recently backported security fix caused an unwanted gdal soname bump in F37, due to an update from the 3.5.x series to the 3.6.x series.

I'm preparing a gdal-3.6.2-8.really3.5.3.fc37 to address this, please don't rebuild any dependencies in the meantime, as the new package will bring back the previous soname.

Apologies for the troubles.

Hello,

this is not the first time I saw a bodhi update that breaks dozens of dependencies, goes unnoticed for a week and is automatically pushed stable, only to discover many packages fail to install.

How come we don't have an automatic check for this? What can be done?

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux