Bug 1699852 - No seamless upgrade to fc30 because of httpcomponents-client
Summary: No seamless upgrade to fc30 because of httpcomponents-client
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora Modules
Classification: Fedora
Component: maven
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Mikolaj Izdebski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F30FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2019-04-15 11:42 UTC by Michael
Modified: 2019-04-27 02:35 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-26 20:22:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michael 2019-04-15 11:42:41 UTC
Description of problem:
An installation of Fedora 29 with the package group "Fedora Eclipse" installed cannot be upgraded seamlessly to Fedora 30 (beta) because of a dependency issue related to httpcomponents-client. 

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

How reproducible:


Steps to Reproduce:
1. Fedora 29 with package group "Fedora Eclipse" and all updates installed.
2. sudo dnf system-upgrade download --refresh --releasever=30 --setopt='module_platform_id=platform:f30' --enablerepo=updates-testing-modular --enablerepo=updates-testing

Actual results:

Error: 
 Problem 1: problem with installed package httpcomponents-client-cache-4.5.5-5.fc29.noarch
  - package httpcomponents-client-cache-4.5.6-3.fc30.noarch requires mvn(org.apache.httpcomponents:httpclient) = 4.5.6, but none of the providers can be installed
  - httpcomponents-client-cache-4.5.5-5.fc29.noarch does not belong to a distupgrade repository
  - package httpcomponents-client-4.5.6-3.fc30.noarch is excluded

sudo repoquery --whatrequires httpcomponents-client-cache --installed
eclipse-epp-logging-0:2.0.7-5.fc29.noarch


Expected results:
No errors.

Additional info:
A workaround is to use the --allowerasing option.

Comment 1 Stuart D Gathman 2019-04-15 21:00:28 UTC
Should I submit 4.5.7 as an update?  Or is the problem that Eclipse requires 4.5.5 specifically?  I am still able to build 4.5.7, and I don't understand modules yet.  There is no non-modular package on f30, so I'll go ahead and submit 4.5.7 on f30.  The whole point of modules is that something like Eclipse can get a specific version from a module, right?

Comment 2 Fedora Update System 2019-04-15 21:02:21 UTC
httpcomponents-client-4.5.7-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-b654b79076

Comment 3 Geoffrey Marr 2019-04-15 21:09:27 UTC
Discussed during the 2019-04-15 blocker review meeting: [1]

The decision to classify this bug as an "AcceptedFreezeException" was made as this is another typical 'packaging issue affects upgrade' bug, we always like to fix these during freeze so upgrades work (also seems different from 1698504).

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2019-04-15/f30-blocker-review.2019-04-15-16.03.txt

Comment 4 Mat Booth 2019-04-15 22:13:33 UTC
IMO this is nothing to do with Eclipse, since there is already a sufficiently new package for F30: https://koji.fedoraproject.org/koji/buildinfo?buildID=1189114

The problem seems to be that modular package always trump the non-module package, even if the non-module package is newer (this seems crazy to me, but there we are) so shouldn't this bug be filed against the module that provides httpcomponents-client?

Comment 5 Fedora Update System 2019-04-16 01:35:50 UTC
httpcomponents-client-4.5.7-1.fc30 has been pushed to the Fedora 30 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-2019-b654b79076

Comment 6 Stuart D Gathman 2019-04-16 20:14:57 UTC
dnf does not use this update.  With the module enabled, it will only use an update in the module stream.  So, I think maybe it won't hurt anything to have the non-modular update, but it won't fix this problem either.  Should I try to submit an update for the module stream?  Or just wait for the module owner?

Comment 7 Fedora Update System 2019-04-16 21:24:23 UTC
maven-3.5-2820190416211833.819b5873 has been submitted as an update to Fedora 30 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-dd28e893bc

Comment 8 Fedora Update System 2019-04-17 13:41:43 UTC
maven-3.5-2820190416211833.819b5873 has been pushed to the Fedora 30 Modular 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-MODULAR-2019-dd28e893bc

Comment 9 Fedora Update System 2019-04-25 19:33:17 UTC
maven-3.5-2820190416211833.819b5873 has been pushed to the Fedora 30 Modular stable repository. If problems still persist, please make note of it in this bug report.

Comment 10 Adam Williamson 2019-04-26 18:15:16 UTC
The non-modular httpcomponents-client update was not yet pushed stable, so re-opening to do that.

Comment 11 Mikolaj Izdebski 2019-04-26 20:22:01 UTC
Actually the problem reported here is in maven module, stream 3.5, not in "ursine" httpcomponents-client package.
Update to non-modular httpcomponents-client package doesn't fix the problem, nor is required to fix the problem.
Therefore the non-modular update should be a zero-day update, and not included in GA due to change freeze.
Since the issue reported in the bug is already fixed in Fedora 30 GA (RC 1.2), CLOSED/CURRENTRELEASE is the right resolution for this bug report.

Comment 12 Adam Williamson 2019-04-27 02:35:50 UTC
The httpcomponents-client update was already in RC2. Because it was in RC2, it needed to be pushed stable as part of the final stable updates push before we freeze the F30 repo. And for it to show up in the request blockerbugs generates for us, the bug could not be closed. That's why I re-opened it.


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