Bug 1648197 - httpcomponents-client-4.5.6-1.fc30.noarch is excluded
Summary: httpcomponents-client-4.5.6-1.fc30.noarch is excluded
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: httpcomponents-client
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Mikolaj Izdebski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-09 05:26 UTC by George R. Goffe
Modified: 2019-01-21 09:21 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-21 09:21:16 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description George R. Goffe 2018-11-09 05:26:26 UTC 
Description of problem:

Attempting to upgrade FC30 x86_64 caused error messages

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

httpcomponents-client-4.5.5-5.fc29.noarch

How reproducible:


Steps to Reproduce:
1.dnf -y --best --skip-broken upgrade httpcomponents-client-cache.noarch
2.
3.

Actual results:

See below

Expected results:


Additional info:

dnf -y --best --skip-broken upgrade httpcomponents-client-cache.noarch
Last metadata expiration check: 0:00:29 ago on Thu 08 Nov 2018 09:17:32 PM PST.
Error: 
 Problem: package httpcomponents-client-cache-4.5.6-1.fc30.noarch requires mvn(org.apache.httpcomponents:httpclient) = 4.5.6, but none of the providers can be installed
  - cannot install the best update candidate for package httpcomponents-client-cache-4.5.5-5.fc29.noarch
Comment 1 Marián Konček 2019-01-18 10:46:26 UTC 
The bug is not reproducible. Is it possible that the issue is already resolved?
Comment 2 Marián Konček 2019-01-18 10:55:38 UTC 
Can the reporter provide additional information on how to reproduce this bug?
Comment 3 George R. Goffe 2019-01-19 00:00:52 UTC 
Marian,

My current levels for this package are higher than those reported here so I would "assume" that the problem is resolved.

Thanks for your help and time,

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