Bug 1966342

Summary:	maven update errors when updating alternatives
Product:	[Fedora] Fedora	Reporter:	Michal Jaegermann <michal.jnn>
Component:	maven	Assignee:	Mikolaj Izdebski <mizdebsk>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	java-maint-sig, java-sig-commits, mizdebsk, msrb, sochotni
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:	2021-06-05 08:37:56 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:

Description Michal Jaegermann 2021-05-31 21:34:44 UTC

Description of problem:

I noticed the following while running a rawhide update:

Running scriptlet: maven-1:3.6.3-9.fc35.noarch                       815/2413 
failed to link /usr/share/man/man1/mvn.1.gz -> /etc/alternatives/mvn1: /usr/share/man/man1/mvn.1.gz exists and it is not a symlink
failed to link /usr/share/man/man1/mvnDebug.1.gz -> /etc/alternatives/mvnDebug1: /usr/share/man/man1/mvnDebug.1.gz exists and it is not a symlink

Indeed, this cannot work unless /usr/share/man/man1/mvn.1.gz and /usr/share/man/man1/mvnDebug.1.gz are removed first.

Version-Release number of selected component (if applicable):
maven-1:3.6.3-9.fc35

How reproducible:
on every run of 'update-alternatives ....

Additional info:
Quite possible this bug lingers for a while but I did not pay attention earlier

Comment 1 Mikolaj Izdebski 2021-06-01 04:25:44 UTC

I don't see the issue from spec file examination.
The problem is not reproducible during F34 -> F35 upgrade.
I tried rawhide upgrade from Fedora-Rawhide-20210520.n.1 to Fedora-Rawhide-20210529.n.0, but the issue is not reproducible either.

Michal, can you specify which version-release of maven package where upgrading from? That is the version-release you hand installed before starting the upgrade. Without that information I'm unable to reproduce the issue.

Comment 2 Michal Jaegermann 2021-06-01 15:29:16 UTC

(In reply to Mikolaj Izdebski from comment #1)
> I don't see the issue from spec file examination.
> The problem is not reproducible during F34 -> F35 upgrade.

Quite likely.  As I wrote this is probably a leftover from many versions back and I simply never paid attention before.  The files in question in /usr/share/man/man1/ have timestamps
from 2018.  I bumped into this while searching for another possible issue.

It seems to me that one never knows from which version an upgrade runs and what was really on a disk.  Besides it is enough just to add suitable 'rm -f ...' in a package script just
before 'update-alternatives ...'.  OTOH if you just want to ignore that then this is your call.

Comment 3 Mikolaj Izdebski 2021-06-05 08:37:56 UTC

Since the problem is not reproducible I'll have to close it without a fix.
Feel free to reopen it if there is a way to reproduce it.