eclipse-jgit failed to build from source in Fedora rawhide/f31 https://koji.fedoraproject.org/koji/taskinfo?taskID=36633070 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild Please fix eclipse-jgit at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, eclipse-jgit will be orphaned. Before branching of Fedora 32, eclipse-jgit will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://fedoraproject.org/wiki/Fails_to_build_from_source
Created attachment 1595893 [details] build.log
Created attachment 1595894 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 1595895 [details] state.log
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
This is breaking upgrades to F31: > Problem 1: problem with installed package eclipse-jgit-5.4.0-4.fc30.noarch > - eclipse-jgit-5.4.0-4.fc30.noarch does not belong to a distupgrade > repository > - nothing provides jgit = 5.3.0-5.fc31 needed by > eclipse-jgit-5.3.0-5.fc31.noarch
Can you explain how a FTBFS bug breaks upgrades?
jgit was updated to 5.4.0 and eclipse-jgit is not installable now.
Then this is a different issue and should be reported as a separate bug.
It's pretty clear that both will be fixed at the same time. Entia non sunt multiplicanda praeter necessitatem.
To me it's the opposite - it's pretty clear that the two issues are not very much related and that fixing FTBFS will not fix FTI (fails to install) bug - FTBFS is caused by dependency issues in ursine buildroots while FTI seems to be caused by modular packages shadowing ursine packages. Therefore, in order to be able to reproduce the FTI issue we need a separate bug open with all relevant details - which packages were installed at the time of upgrade attempt, which YUM repositories were enabled, which modules were enabled and so on.
I can reproduce the same error easily on a F31 installation, and a clean F32 server install: $ sudo dnf install eclipse-jgit Last metadata expiration check: 2:26:12 ago on Thu Sep 12 09:17:37 2019. Error: Problem: conflicting requests - nothing provides jgit = 5.3.0-5.fc31 needed by eclipse-jgit-5.3.0-5.fc31.noarch (try to add '--skip-broken' to skip uninstallable packages) There might be some complex underlying issues, but I think this is for the maintainers to figure out. From the POV of users (or packages who are not familiar with this particular package), a report like this should be enough. It's an obvious bug (breaks upgrade path) and reproduction is trivial.
FEDORA-MODULAR-2019-33a1b20f0a has been submitted as an update to Fedora 31 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-33a1b20f0a
(In reply to Zbigniew Jędrzejewski-Szmek from comment #12) > I can reproduce the same error easily on a F31 installation, and a clean F32 > server install: > $ sudo dnf install eclipse-jgit > Last metadata expiration check: 2:26:12 ago on Thu Sep 12 09:17:37 2019. > Error: > Problem: conflicting requests > - nothing provides jgit = 5.3.0-5.fc31 needed by > eclipse-jgit-5.3.0-5.fc31.noarch > (try to add '--skip-broken' to skip uninstallable packages) > > There might be some complex underlying issues, but I think this is for the > maintainers to figure out. > From the POV of users (or packages who are not familiar with this particular > package), a report like > this should be enough. It's an obvious bug (breaks upgrade path) and > reproduction is trivial. There are severe problems with MBS that has prevented me from publishing the Eclipse module sooner. Apologies for the inconvenience.
eclipse-2019_06-3120190902131726.efdece7d has been pushed to the Fedora 31 Modular stable repository. If problems still persist, please make note of it in this bug report.