Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1814716 - Polymake needs to be updated for perl 5.30.2-451
Summary: Polymake needs to be updated for perl 5.30.2-451
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: polymake
Version: 32
Hardware: x86_64
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Jerry James
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1814888 1816476 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-18 14:55 UTC by Eugene Mah
Modified: 2021-02-02 21:06 UTC (History)
5 users (show)

Fixed In Version: polymake-4.0.1-2.fc32 polymake-3.6-2.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 08:00:35 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Eugene Mah 2020-03-18 14:55:07 UTC 
Description of problem:
polymake-4.0.1-1.fc32 needs to be updated for perl-5.30.2-451.fc32 currently in testing

Version-Release number of selected component (if applicable):


How reproducible:
dnf upgrade

Steps to Reproduce:
1. dnf upgrade
2.
3.

Actual results:
Problem 1: package polymake-singular-4.0.1-1.fc32.x86_64 requires perl-interpreter = 4:5.30.1, but none of the providers can be installed
- cannot install both perl-interpreter-4:5.30.2-451.fc32.x86_64 and perl-interpreter-4:5.30.1-450.fc32.x86_64
- cannot install both perl-interpreter-4:5.30.1-450.fc32.x86_64 and perl-interpreter-4:5.30.2-451.fc32.x86_64
- cannot install the best update candidate for package polymake-singular-4.0.1-1.fc32.x86_64
- cannot install the best update candidate for package perl-interpreter-4:5.30.1-450.fc32.x86_64
- package perl-interpreter-4:5.30.1-449.module_f32+7155+1847c895.x86_64 is filtered out by modular filtering
- package perl-interpreter-4:5.30.1-449.module_f32+8055+f9bd3002.x86_64 is filtered out by modular filtering
Problem 2: package python3-jupymake-0.9-3.20190509.031cc3a.fc32.x86_64 requires libpolymake.so.4.0()(64bit), but none of the providers canbe installed
- package polymake-singular-4.0.1-1.fc32.x86_64 requires perl-interpreter = 4:5.30.1, but none of the providers can be installed
- cannot install both perl-interpreter-4:5.30.2-451.fc32.x86_64 and perl-interpreter-4:5.30.1-450.fc32.x86_64
- cannot install both perl-interpreter-4:5.30.1-450.fc32.x86_64 and perl-interpreter-4:5.30.2-451.fc32.x86_64
- package perl-4:5.30.2-451.fc32.x86_64 requires perl-interpreter(x86-64) = 4:5.30.2-451.fc32, but none of the providers can be installed
- cannot install the best update candidate for package python3-jupymake-0.9-3.20190509.031cc3a.fc32.x86_64
- cannot install the best update candidate for package perl-4:5.30.1-450.fc32.x86_64
- package perl-interpreter-4:5.30.1-449.module_f32+7155+1847c895.x86_64 is filtered out by modular filtering
- package perl-interpreter-4:5.30.1-449.module_f32+8055+f9bd3002.x86_64 is filtered out by modular filtering
Problem 3: package polymake-4.0.1-1.fc32.x86_64 requires polymake-singular(x86-64) = 4.0.1-1.fc32, but none of the providers can be installed
- package polymake-singular-4.0.1-1.fc32.x86_64 requires perl-interpreter = 4:5.30.1, but none of the providers can be installed
- package perl-interpreter-4:5.30.1-450.fc32.x86_64 requires perl-libs(x86-64) = 4:5.30.1-450.fc32, but none of the providers can be installed
- cannot install both perl-libs-4:5.30.2-451.fc32.x86_64 and perl-libs-4:5.30.1-450.fc32.x86_64
- cannot install both perl-libs-4:5.30.1-450.fc32.x86_64 and perl-libs-4:5.30.2-451.fc32.x86_64
- cannot install the best update candidate for package polymake-4.0.1-1.fc32.x86_64
- cannot install the best update candidate for package perl-libs-4:5.30.1-450.fc32.x86_64
- package perl-interpreter-4:5.30.1-449.module_f32+7155+1847c895.x86_64 is filtered out by modular filtering
- package perl-interpreter-4:5.30.1-449.module_f32+8055+f9bd3002.x86_64 is filtered out by modular filtering
Problem 4: problem with installed package polymake-singular-4.0.1-1.fc32.x86_64
- package polymake-singular-4.0.1-1.fc32.x86_64 requires perl-interpreter = 4:5.30.1, but none of the providers can be installed
- package perl-interpreter-4:5.30.1-450.fc32.x86_64 requires perl-libs(x86-64) = 4:5.30.1-450.fc32, but none of the providers can be installed
- cannot install both perl-libs-4:5.30.2-451.fc32.x86_64 and perl-libs-4:5.30.1-450.fc32.x86_64
- cannot install both perl-libs-4:5.30.1-450.fc32.x86_64 and perl-libs-4:5.30.2-451.fc32.x86_64
- package perl-Errno-1.30-451.fc32.x86_64 requires perl-libs(x86-64) = 4:5.30.2-451.fc32, but none of the providers can be installed
- cannot install the best update candidate for package perl-Errno-1.30-450.fc32.x86_64
- package perl-interpreter-4:5.30.1-449.module_f32+7155+1847c895.x86_64 is filtered out by modular filtering
- package perl-interpreter-4:5.30.1-449.module_f32+8055+f9bd3002.x86_64 is filtered out by modular filtering
Problem 5: problem with installed package python3-jupymake-0.9-3.20190509.031cc3a.fc32.x86_64
- package python3-jupymake-0.9-3.20190509.031cc3a.fc32.x86_64 requires libpolymake.so.4.0()(64bit), but none of the providers can be installed
- package polymake-singular-4.0.1-1.fc32.x86_64 requires perl-interpreter = 4:5.30.1, but none of the providers can be installed
- package perl-interpreter-4:5.30.1-450.fc32.x86_64 requires perl-libs(x86-64) = 4:5.30.1-450.fc32, but none of the providers can be installed
- cannot install both perl-libs-4:5.30.2-451.fc32.x86_64 and perl-libs-4:5.30.1-450.fc32.x86_64
- cannot install both perl-libs-4:5.30.1-450.fc32.x86_64 and perl-libs-4:5.30.2-451.fc32.x86_64
- package perl-devel-4:5.30.2-451.fc32.x86_64 requires perl-libs(x86-64) = 4:5.30.2-451.fc32, but none of the providers can be installed
- cannot install the best update candidate for package perl-devel-4:5.30.1-450.fc32.x86_64
- package perl-interpreter-4:5.30.1-449.module_f32+7155+1847c895.x86_64 is filtered out by modular filtering
- package perl-interpreter-4:5.30.1-449.module_f32+8055+f9bd3002.x86_64 is filtered out by modular filtering
Problem 6: package perl-4:5.30.1-450.fc32.x86_64 requires perl-libs(x86-64) = 4:5.30.1-450.fc32, but none of the providers can be installed
- problem with installed package perl-4:5.30.1-450.fc32.x86_64
- cannot install both perl-libs-4:5.30.2-451.fc32.x86_64 and perl-libs-4:5.30.1-450.fc32.x86_64
- cannot install both perl-libs-4:5.30.1-450.fc32.x86_64 and perl-libs-4:5.30.2-451.fc32.x86_64
- perl-libs-4:5.30.2-451.fc32.i686 has inferior architecture
- package perl-utils-5.30.2-451.fc32.noarch requires perl-libs = 4:5.30.2-451.fc32, but none of the providers can be installed
- cannot install the best update candidate for package perl-utils-5.30.1-450.fc32.noarch
- package perl-4:5.30.2-451.fc32.x86_64 requires perl-interpreter(x86-64) = 4:5.30.2-451.fc32, but none of the providers can be installed
- package polymake-doc-4.0.1-1.fc32.x86_64 requires polymake(x86-64) = 4.0.1-1.fc32, but none of the providers can be installed
- package polymake-4.0.1-1.fc32.x86_64 requires polymake-singular(x86-64) = 4.0.1-1.fc32, but none of the providers can be installed
- package polymake-singular-4.0.1-1.fc32.x86_64 requires perl-interpreter = 4:5.30.1, but none of the providers can be installed
- cannot install both perl-interpreter-4:5.30.2-451.fc32.x86_64 and perl-interpreter-4:5.30.1-450.fc32.x86_64
- cannot install both perl-interpreter-4:5.30.1-450.fc32.x86_64 and perl-interpreter-4:5.30.2-451.fc32.x86_64
- cannot install the best update candidate for package polymake-doc-4.0.1-1.fc32.x86_64
- package perl-interpreter-4:5.30.1-449.module_f32+7155+1847c895.x86_64 is filtered out by modular filtering
- package perl-interpreter-4:5.30.1-449.module_f32+8055+f9bd3002.x86_64 is filtered out by modular filtering
===========================================================================================================================================
Package                            Architecture             Version                               Repository                         Size
===========================================================================================================================================
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
perl-interpreter                   x86_64                   4:5.30.2-451.fc32                     updates-testing                   6.1 M
perl-libs                          x86_64                   4:5.30.2-451.fc32                     updates-testing                   1.7 M
Skipping packages with broken dependencies:
perl                               x86_64                   4:5.30.2-451.fc32                     updates-testing                    20 k
perl-Errno                         x86_64                   1.30-451.fc32                         updates-testing                    24 k
perl-devel                         x86_64                   4:5.30.2-451.fc32                     updates-testing                   711 k
perl-utils                         noarch                   5.30.2-451.fc32                       updates-testing                    76 k

Transaction Summary
===========================================================================================================================================
Skip  6 Packages

Expected results:
perl-5.30.2-451.fc32 should be updated

Additional info:
Also happens with Fedora 31
Comment 1 Fedora Update System 2020-03-18 22:31:02 UTC 
FEDORA-2020-157f87857c has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-157f87857c
Comment 2 Fedora Update System 2020-03-19 03:14:25 UTC 
polymake-3.6-2.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-157f87857c
Comment 3 Fedora Update System 2020-03-19 04:26:11 UTC 
FEDORA-2020-05a659204f has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-05a659204f
Comment 4 Jerry James 2020-03-19 22:14:37 UTC 
*** Bug 1814888 has been marked as a duplicate of this bug. ***
Comment 5 Jerry James 2020-03-19 22:38:38 UTC 
I have told a few people to visit this bug for more information on why polymake and its dependent packages cannot be updated in Fedora 31.  Consider this an infomercial. :-)

First, polymake depends on the specific version of perl it was built with.  For example, the version of polymake currently available in F31 depends on perl 5.30.1, rather than on any 5.30.x.  This is by design.  The polymake code reaches deep into the guts of perl to do its work.  This makes it highly version specific.  Even small changes in the perl engine can require polymake to be rebuilt, or even patched.

Second, perl updates tend to go stable very quickly.  Take this latest perl build for example.  The F31 build finished at Mon, 16 Mar 2020 08:52:36 UTC (see https://koji.fedoraproject.org/koji/buildinfo?buildID=1477834).  The update was created at 08:58:13 UTC, pushed to the testing repository at 14:53:58 UTC, and had +3 karma at Tue, 17 Mar 2020 11:09:08 UTC, a mere 26 hours after the build finished (see https://bodhi.fedoraproject.org/updates/FEDORA-2020-64ac8a1df1).

When a new perl version shows up, I have a choice: try to get build overrides in place for all of the necessary packages, then proceed with the build, or just wait a day until it all goes stable and build then.  I usually choose the latter, not out of laziness (necessarily!), but due to time considerations and a desire to not break the buildroot for others.  So after the update showed up in my local mirror on Wednesday morning, I launched a build at 13:35:18 UTC (see https://koji.fedoraproject.org/koji/buildinfo?buildID=1478782).  This bug was filed almost an hour and a half later.  Polymake builds take a long time.  This one finished at 22:28:17 UTC.  I then submitted the update, which so far has karma of only +1, so it has not been pushed stable yet.

The thing to understand is that this is going to happen every time there is a perl update that changes the version number.  All you polymake users are going to have to consider this normal.  The system is working the way it is supposed to work.  DNF is refusing to let you install a perl version that might break polymake.  Now, polymake might be just fine with the new perl version ... but it might not.  Until a build done with that specific version of perl is available, DNF is going to protect you.

I should put all that text on a web page somewhere.  Suggestions for a good place are welcome.
Comment 6 Eugene Mah 2020-03-20 01:28:27 UTC 
Thanks for the explanation.  Didn't realize polymake builds take such a long time.  Now that I know what goes on behind the scenes I'll remember to be more patient :)
Comment 7 Fedora Update System 2020-03-20 01:58:38 UTC 
polymake-4.0.1-2.fc32 has been pushed to the Fedora 32 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-05a659204f
Comment 8 Jerry James 2020-03-20 02:14:11 UTC 
If it doesn't look like I've started a build in a timely fashion, it is perfectly alright to poke me.  Also, if anybody wants to comaintain this package, I would welcome the help.

The real problem with polymake builds is 32-bit ARM, of course.  The x86_64 builds do not take anywhere near that long.  My personal opinion is that you'd have to be a serious masochist to actually run polymake on a 32-bit ARM, but its one of the supported Fedora architectures, so we build there.
Comment 9 Jerry James 2020-03-24 14:52:23 UTC 
*** Bug 1816476 has been marked as a duplicate of this bug. ***
Comment 10 Fedora Update System 2020-03-27 08:00:35 UTC 
FEDORA-2020-05a659204f has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 11 Fedora Update System 2020-03-27 13:08:56 UTC 
FEDORA-2020-157f87857c has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.