Bug 1852003 - Unsatisfied deps
Summary: Unsatisfied deps
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-constant
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1852005 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-29 15:13 UTC by Jaroslav Škarvada
Modified: 2020-06-30 06:55 UTC (History)
3 users (show)

Fixed In Version: perl-constant-1.33-457.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-30 06:53:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Škarvada 2020-06-29 15:13:28 UTC
Description of problem:
I cannot install perl-Digest-SHA, it seems the problem is in unsatisfied deps of 
the perl-constant.

Version-Release number of selected component (if applicable):
perl-constant-1.33-441.fc32

How reproducible:
Always

Steps to Reproduce:
1. rebuild putty
2.
3.

Actual results:
DEBUG util.py:621:  Error: 
DEBUG util.py:621:   Problem: package perl-Digest-SHA-1:6.02-457.fc33.x86_64 requires perl(Getopt::Long), but none of the providers can be installed
DEBUG util.py:621:    - package perl-Getopt-Long-1:2.51-456.fc33.noarch requires perl(constant), but none of the providers can be installed
DEBUG util.py:621:    - conflicting requests
DEBUG util.py:621:    - nothing provides perl(:MODULE_COMPAT_5.30.1) needed by perl-constant-1.33-441.fc32.noarch

Expected results:
No unsatisfied deps

Additional info:
It's blocking rebuild of the putty package.

Comment 1 Petr Pisar 2020-06-30 06:53:42 UTC
You hit a window when relengs were merging rebuilt Perl into Fedora 33 <https://pagure.io/releng/issue/9528#comment-662005>. They cannot do it in an atomic way. It should be fixed now with perl-constant-1.33-457.fc33.

Comment 2 Petr Pisar 2020-06-30 06:55:30 UTC
*** Bug 1852005 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.