Bug 858941 – [eclipse] Ebuild failures occuring in global scope

• Product: Gentoo Linux
• Status: CONFIRMED ---

[Description Thomas Bracht Laumann Jespersen 2022-07-18 18:39:43 UTC]

== == == == == == == == == == == == == == == == == == == == == == == ==
The repository owner is not registered on Bugzilla
Owner: ['[e-mail]']
== == == == == == == == == == == == == == == == == == == == == == == ==

Our automated repository checks [1] have detected that the 'eclipse'
repository contains ebuilds that trigger fatal errors during the cache
regeneration. This usually means that the ebuilds call 'die' in global
scope indicating serious issues or have other serious QA violations.

Global-scope failures prevent the ebuild not only from being installed
but also from being properly processed by the Package Manager. Since
metadata can not be obtained for those ebuilds, no cache entries are
created for them and the Package Manager needs to retry running them
every time it stumbles upon them. This involves both a serious slowdown
and repeating error output while performing dependency resolution.

The most common cause of global-scope failures is use of removed or
banned APIs in old ebuilds. In particular, this includes eclasses being
removed or removing support for old EAPIs. Nonetheless there are also
other issues such as performing illegal operations in global scope
(external program calls), malformed bash in ebuilds or malformed
metadata.xml.

The error log for the repository can be found at:

  https://qa-reports.gentoo.org/output/repos/eclipse.html

In particular, please look for highlighted error messages.

Please fix the issue ASAP, possibly via removing unmaintained, old
ebuilds. We reserve the right to remove the repository from our list if
we do not receive any reply within 4 weeks.

[1]:https://wiki.gentoo.org/wiki/Project:Repository_mirror_and_CI

[Comment 1 Thomas Bracht Laumann Jespersen 2022-08-16 13:01:21 UTC]

ping

[Comment 2 Thomas Bracht Laumann Jespersen 2022-09-19 13:12:43 UTC]

ping

[Comment 3 Thomas Bracht Laumann Jespersen 2023-01-03 08:11:07 UTC]

ping

[Comment 4 Michał Górny 2023-03-20 06:42:40 UTC]

@sping, is this thing alive?  If yes, please update the contact address in repositories.xml.  If no, please remove it.

[Comment 5 Georgi 2023-06-22 06:34:31 UTC]

Hello,

I think this repository should be removed as it hasn't been touched for two years and two years are a lot of time in the Eclipse world and in the same time I think packaging Eclipse makes no sense in Gentoo context. If done thoroughly and correctly it's going to be a huge burden. That also explains why it hasn't been touched for so long.

It also brings confusion in users unfamiliar with Eclipse and how it works. Also it has it's own packaging and update system which would most certainly clash with Gentoo's model.

Best Regards,
Georgi

[Comment 6 Georgi 2023-06-22 06:45:19 UTC]

I'm sorry for spamming, I didn't pay attention it wasn't maintained for 6 years now. That commit that was done 2 years ago must have been related to a major vulnerability discovered in log4j. Nothing substantial has actually happened for those 6 years since 2017, when the discussion in the referenced bug #325271 ceased.

Best Regards,
Georgi