Polymake blocks system updates by strict Perl dependence: polymake-3.0r2-1.fc25.x86_64 requires perl = 4:5.24.0 and the new perl package is tagged 4:5.24.1 This blocks upgrades for dependent packages (perl*, git*, vim*), while polymake can't just be bypassed because it is a dependency of quite a bit of other packages (python*, gap*, sage*, ocaml*), so it's a stalemate. I reported that in https://bugzilla.redhat.com/show_bug.cgi?id=1415548 Now, the reason I mention it here is that I noticed a number of update hiccups recently, resulting from strict checks by DNF. I don't think it's DNF's fault: here, it just enforces a strict requirement specified by 'polymake'. I reported other cases, where the file specifications cause conflicts between the old and new version of the package: https://bugzilla.redhat.com/show_bug.cgi?id=1404897 https://bugzilla.redhat.com/show_bug.cgi?id=1396848 https://bugzilla.redhat.com/show_bug.cgi?id=1396319 https://bugzilla.redhat.com/show_bug.cgi?id=1396849 and people commented that they also are all packaging errors. Still, they do block upgrades. My question is: is reporting them individually the best approach? I am happy to keep doing it, but there's been more than the usual amount recently, and I am wondering if there's some automation that should be done to detect that in packaging. |
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx