On Tue, 2022-04-26 at 16:02 +0200, Kevin Kofler via devel wrote: > Mikolaj Izdebski wrote: > > Do you have any evidence for this claim that the update will break any > > package? If so, please share it. > > You wrote yourself: "The new major version introduces API break and packages > may need to be ported to work with the new version." So it has to be assumed > that dependent packages can, and most likely will, break. At the very least > they will need to be rebuilt against the new soname (unless the API change > does not go with an soname bump, which would be a violation of Fedora > policies, too).
Thanks to Kevin and Mattia for being careful here! But looking at the packages, it seems not quite so clear-cut. These are Java packages; they don't build traditional shared libraries with sonames. Looking at the new modello package, it provides these: modello = 2.0.0-1.fc37 mvn(org.codehaus.modello:modello-core) = 2.0.0 mvn(org.codehaus.modello:modello-core:pom:) = 2.0.0 mvn(org.codehaus.modello:modello-maven-plugin) = 2.0.0 mvn(org.codehaus.modello:modello-maven-plugin:pom:) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-converters) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-converters:pom:) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-dom4j) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-dom4j:pom:) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-java) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-java:pom:) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-jdom) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-jdom:pom:) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-sax) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-sax:pom:) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-stax) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-stax:pom:) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-xdoc) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-xdoc:pom:) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-xml) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-xml:pom:) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-xpp3) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-xpp3:pom:) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-xsd) = 2.0.0 mvn(org.codehaus.modello:modello-plugin-xsd:pom:) = 2.0.0 mvn(org.codehaus.modello:modello-plugins:pom:) = 2.0.0 mvn(org.codehaus.modello:modello-test) = 2.0.0 mvn(org.codehaus.modello:modello-test:pom:) = 2.0.0 mvn(org.codehaus.modello:modello:pom:) = 2.0.0 note, no libraries, no sonames. So this is more like a major version bump to a Python package, for e.g., than a new soname for a shared library. If any other package explicitly required e.g. "mvn(org.codehaus.modello:modello-core) < 2.0.0" it will now not be installable. If any other package did not explicitly have such a requirement, but actually does not work properly with modello 2.0.0, it'll still be installable, but won't work properly until it's adapted. It would still be best practice to actually figure out how the dependent packages will be affected by the version bump before landing it in Rawhide, however the relevant maintainers want to do that. -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
