Bug 1755563

Summary:	maven-doxia does not update without '--best --allowerasing'
Product:	[Fedora] Fedora	Reporter:	Michal Jaegermann <michal.jnn>
Component:	maven-doxia	Assignee:	Stewardship SIG <stewardship-sig>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	akurtako, dbhole, decathorpe, java-sig-commits, mefoster, mhroncok, mizdebsk, sochotni, stewardship-sig
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-26 17:54:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1755570
Bug Blocks:

Description Michal Jaegermann 2019-09-25 17:03:43 UTC

Description of problem:

Attempts to run updates bumps into the following:

 Problem 1: package maven-doxia-1.9-1.fc32.noarch obsoletes maven-doxia-module-markdown < 1.9-1.fc32 provided by maven-doxia-module-markdown-1.7-12.fc32.noarch
  - package maven-site-plugin-3.6-6.fc30.noarch requires mvn(org.apache.maven.doxia:doxia-module-markdown), but none of the providers can be installed
  - cannot install the best update candidate for package maven-doxia-1.7-12.fc32.noarch
  - problem with installed package maven-site-plugin-3.6-6.fc30.noarch
 Problem 2: cannot install both maven-doxia-core-1.9-1.fc32.noarch and maven-doxia-core-1.7-12.fc32.noarch
  - package maven-doxia-module-itext-1.7-10.fc30.noarch requires mvn(org.apache.maven.doxia:doxia-core) = 1.7, but none of the providers can be installed
  - cannot install the best update candidate for package maven-doxia-core-1.7-12.fc32.noarch
  - problem with installed package maven-doxia-module-itext-1.7-10.fc30.noarch

Version-Release number of selected component (if applicable):
maven-doxia-1.9-1.fc32

Additional info:
Forcing a removal of maven-site-plugin and maven-doxia-module-itext allows an update to proceed.

Comment 1 Fabio Valentini 2019-09-25 17:29:31 UTC

These are actually two different issues:

- maven-site-plugin was retired
- maven-doxia-module-itext was removed but not obsoleted

I will push a maven-doxia build fixing the second issue to rawhide later.

I think the first issue qualifies as a case where maven-site-plugin should be added to fedora-obsolete-packages, since its presence is actually causing upgrade issues in / to rawhide. I will submit a Pull Request.

Comment 2 Fabio Valentini 2019-09-25 17:40:41 UTC

Alright, I fixed the issue with the removed -itext module in this build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=37861034

I also filed a request to add maven-site-plugin to the list of obsolete packages in fedora 32.

Comment 3 Michal Jaegermann 2019-09-25 20:56:32 UTC

(In reply to Fabio Valentini from comment #2)
> Alright, I fixed the issue with the removed -itext module in this build:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=37861034
> 
> I also filed a request to add maven-site-plugin to the list of obsolete
> packages in fedora 32.

Looking at related stuff it seem that there are also hanging around packages like
maven-downloader-1.1-16.fc29.noarch
maven-jxr-2.5-8.fc29.noarch
maven-plugin-jxr-2.5-8.fc29.noarch
which seems to be gone.  Maybe they should be added to obsolete packages too?

Comment 4 Fabio Valentini 2019-09-28 12:47:12 UTC

Are these packages causing dependency issues as well?
If not, then there's no reason to obsolete them.

Comment 5 Michal Jaegermann 2019-09-28 14:32:58 UTC

(In reply to Fabio Valentini from comment #4)
> Are these packages causing dependency issues as well?
> If not, then there's no reason to obsolete them.

They do not seem to be available any longer and a past experience indicates that some day they will become dependency issues.  Your call.

Comment 6 Fabio Valentini 2019-09-28 14:37:03 UTC

Unless they cause upgrade issues, there's no reason to obsolete them.
Only broken packages should be removed from user's systems this way.

> maven-downloader-1.1-16.fc29.noarch
> maven-jxr-2.5-8.fc29.noarch
> maven-plugin-jxr-2.5-8.fc29.noarch

Also, I'm not really the right person to do / decide this, since I am not associated with these 3 packages at all :)

Comment 7 Fabio Valentini 2019-10-26 17:54:34 UTC

Alright, the original two problems are fixed now.