Bug 1766697

Summary:	I cannot upgrade f30 to f31 because of eclipse-m2e-core
Product:	[Fedora] Fedora	Reporter:	Jan Vlug <jan.public>
Component:	eclipse-m2e-core	Assignee:	Mat Booth <mat.booth>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	eclipse-sig, fedora, mat.booth, mizdebsk
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-12-05 11:01:36 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 Jan Vlug 2019-10-29 16:56:18 UTC

When I do:
# dnf system-upgrade download --releasever=31 --skip-broken

I get:
Error: 
 Problem: problem with installed package eclipse-m2e-core-1.11.0-8.module_f30+5264+0fe54b96.noarch
  - eclipse-m2e-core-1.11.0-8.module_f30+5264+0fe54b96.noarch does not belong to a distupgrade repository
  - package eclipse-m2e-core-1.11.0-8.module_f31+6519+12cd0b27.noarch is excluded
  - nothing provides maven-archetype-registry needed by eclipse-m2e-core-1.11.0-1.fc31.noarch

Comment 1 Jan Vlug 2019-10-29 16:57:08 UTC

See also bug 1735135.

Comment 2 Mat Booth 2019-12-05 11:01:36 UTC

I believe we've managed to resolve all the necessary issues with FESCo, Releng and Modularity teams.

It should now be possible to upgrade Eclipse in the normal way.

Don't forget if you explicitly disabled any modules, you will first need to reset them before installing Eclipse, e.g.:

$ sudo dnf module reset eclipse ant maven

Sorry for the inconvenience.