https://bugzilla.redhat.com/show_bug.cgi?id=1816936 Bug ID: 1816936 Summary: perl-PAR-Packer conflicts with perl package Product: Fedora Version: 31 Status: NEW Component: perl-PAR-Packer Severity: urgent Assignee: jplesnik@xxxxxxxxxx Reporter: jvromans@xxxxxxxxxxx QA Contact: extras-qa@xxxxxxxxxxxxxxxxx CC: anon.amish@xxxxxxxxx, jplesnik@xxxxxxxxxx, mmaslano@xxxxxxxxxx, perl-devel@xxxxxxxxxxxxxxxxxxxxxxx Target Milestone: --- Classification: Fedora Description of problem: perl-PAR-Packer conflicts with perl package. The perl-PAR-Packer package has a hard dependency on the exact version of perl-libs. A newer version of perl-libs requires the package to be built against the newer libs. However, perl-libs gets updated independently from perl-PAR-Packer, resulting in install/update conflicts. Version-Release number of selected component (if applicable): perl-PAR-Packer-1.049-2.fc31.x86_64 perl-libs-4:5.30.2-450.fc31.x86_64 How reproducible: Always Steps to Reproduce: 1. Install latest perl-libs (perl-libs-4:5.30.2-450) 2. Install latest perl-PAR-Packer (perl-PAR-Packer-1.049-2) Actual results: Something similar to "package perl-PAR-Packer-1.049-3.fc31.x86_64 requires perl(:VERSION) = 5.30.1, but none of the providers can be installed" or "cannot install both perl-libs-4:5.30.0-446.fc31.x86_64 and perl-libs-4:5.30.2-450.fc31.x86_64" Expected results: Flawless install. Additional info: This happens every time the perl packages are updated. There need to be some way to automatically rebuild perl-PAR-Packer when a new perl package is released. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ perl-devel mailing list -- perl-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to perl-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/perl-devel@xxxxxxxxxxxxxxxxxxxxxxx
