fedora-obsolete-packages for arch specific issues

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

 



We have specific issues during an Fedora upgrade.

In past, it was issue with rdma-core [1] during upgrade to F34. Nowadays, for upgrade to F36, we have an issue with lilv [2]

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1919864

[2] https://bugzilla.redhat.com/show_bug.cgi?id=2052588

Both issues happens, in generall, when you have multilib package A-1.0.i686 and A-1.0.x86_64 which is going to be upgraded to A-2.0.noarch.

We have package `fedora-obsolete-packages` for obsoleting problematic packages. But this package is noarch. And obviously noarch package cannot obsolete multilib package.

I am not aware of any trick that can solve this on rpm level - if you know, please comment in BZ [2].

I think this can be solved by introducing new package which will work like `fedora-obsolete-packages`, but will not be arch. I.e. we will have version for specific architecture and we can obsolete architecture specific packages.

Comments? Ideas?

Miroslav


_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure

[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