Bug 1708356 - apache-commons-logging isn't installable
Summary: apache-commons-logging isn't installable
Keywords:
Status: CLOSED DUPLICATE of bug 1708661
Alias: None
Product: Fedora
Classification: Fedora
Component: apache-commons-logging
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stuart D Gathman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1695499
TreeView+ depends on / blocked
 
Reported: 2019-05-09 17:07 UTC by Alex Scheel
Modified: 2019-05-13 15:35 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-13 15:35:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alex Scheel 2019-05-09 17:07:47 UTC
Description of problem:

The following fails on Fedora Rawhide (F31):

# dnf install apache-commons-logging
Last metadata expiration check: 0:34:53 ago on Thu 09 May 2019 04:31:46 PM UTC.
No match for argument: apache-commons-logging
Error: Unable to find a match

This breaks pki-ca:

Error: 
 Problem: package pki-server-10.7.0-1.fc31.noarch requires pki-tools = 10.7.0, but none of the providers can be installed
  - package pki-tools-10.7.0-1.fc31.x86_64 requires pki-base-java = 10.7.0, but none of the providers can be installed
  - package pki-ca-10.7.0-1.fc31.noarch requires pki-server = 10.7.0, but none of the providers can be installed
  - package pki-base-java-10.7.0-1.fc31.noarch requires apache-commons-logging, but none of the providers can be installed
  - conflicting requests
  - package apache-commons-logging-1.2-17.fc30.noarch is excluded
(try to add '--skip-broken' to skip uninstallable packages)


Please rebuild apache-commons-logging for F30 and F31. Note that this package is maintained as an ursine package as per here: 

https://src.fedoraproject.org/rpms/apache-commons-logging/tree/master

Comment 1 Alex Scheel 2019-05-13 15:35:05 UTC

*** This bug has been marked as a duplicate of bug 1708661 ***


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