November 2020 - eclipse-sig - Fedora mailing-lists

[Bug 1719748] New: jetty-9.4.19.v20190610 is available
by bugzilla＠redhat.com 15 Sep '22

15 Sep '22

https://bugzilla.redhat.com/show_bug.cgi?id=1719748 Bug ID: 1719748 Summary: jetty-9.4.19.v20190610 is available Product: Fedora Version: rawhide Status: NEW Component: jetty Keywords: FutureFeature, Triaged Assignee: mat.booth(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, java-sig-commits(a)lists.fedoraproject.org, jjohnstn(a)redhat.com, krzysztof.daniel(a)gmail.com, mat.booth(a)redhat.com, mizdebsk(a)redhat.com, sochotni(a)redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 9.4.19.v20190610 Current version/release in rawhide: 9.4.18-2.v20190429.fc31 URL: http://www.eclipse.org/jetty Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/1447/ -- You are receiving this mail because: You are on the CC list for the bug.

1 23

[Bug 1902826] New: CVE-2020-27218 jetty: buffer not correctly recycled in Gzip Request inflation
by bugzilla＠redhat.com 23 Mar '22

23 Mar '22

https://bugzilla.redhat.com/show_bug.cgi?id=1902826 Bug ID: 1902826 Summary: CVE-2020-27218 jetty: buffer not correctly recycled in Gzip Request inflation Product: Security Response Hardware: All OS: Linux Status: NEW Component: vulnerability Keywords: Security Severity: medium Priority: medium Assignee: security-response-team(a)redhat.com Reporter: gsuckevi(a)redhat.com CC: abenaiss(a)redhat.com, aboyko(a)redhat.com, aileenc(a)redhat.com, akoufoud(a)redhat.com, alazarot(a)redhat.com, almorale(a)redhat.com, anstephe(a)redhat.com, aos-bugs(a)redhat.com, ataylor(a)redhat.com, bmontgom(a)redhat.com, btofel(a)redhat.com, chazlett(a)redhat.com, drieden(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, eparis(a)redhat.com, etirelli(a)redhat.com, ganandan(a)redhat.com, ggaughan(a)redhat.com, gmalinko(a)redhat.com, gvarsami(a)redhat.com, ibek(a)redhat.com, janstey(a)redhat.com, java-maint(a)redhat.com, java-sig-commits(a)lists.fedoraproject.org, jburrell(a)redhat.com, jcoleman(a)redhat.com, jjohnstn(a)redhat.com, jochrist(a)redhat.com, jokerman(a)redhat.com, jstastny(a)redhat.com, jwon(a)redhat.com, kconner(a)redhat.com, krathod(a)redhat.com, krzysztof.daniel(a)gmail.com, kverlaen(a)redhat.com, ldimaggi(a)redhat.com, mat.booth(a)redhat.com, mizdebsk(a)redhat.com, mnovotny(a)redhat.com, nstielau(a)redhat.com, nwallace(a)redhat.com, pbhattac(a)redhat.com, pdrozd(a)redhat.com, pjindal(a)redhat.com, rrajasek(a)redhat.com, rsynek(a)redhat.com, rwagner(a)redhat.com, sdaley(a)redhat.com, sd-operator-metering(a)redhat.com, sochotni(a)redhat.com, sponnaga(a)redhat.com, sthorger(a)redhat.com, tcunning(a)redhat.com, tkirby(a)redhat.com, vbobade(a)redhat.com Target Milestone: --- Classification: Other In Eclipse Jetty version 9.4.0.RC0 to 9.4.34.v20201102, 10.0.0.alpha0 to 10.0.0.beta2, and 11.0.0.alpha0 to 11.0.0.beta2, if GZIP request body inflation is enabled and requests from different clients are multiplexed onto a single connection, and if an attacker can send a request with a body that is received entirely but not consumed by the application, then a subsequent request on the same connection will see that body prepended to its body. The attacker will not see any data but may inject data into the body of the subsequent request. References: https://bugs.eclipse.org/bugs/show_bug.cgi?id=568892 https://github.com/eclipse/jetty.project/security/advisories/GHSA-86wm-rrjm… -- You are receiving this mail because: You are on the CC list for the bug.

1 37

[Bug 1900374] New: M2E plugin stop works after upgrade
by bugzilla＠redhat.com 30 Nov '21

30 Nov '21

https://bugzilla.redhat.com/show_bug.cgi?id=1900374 Bug ID: 1900374 Summary: M2E plugin stop works after upgrade Product: Fedora Version: 33 Hardware: x86_64 OS: Linux Status: NEW Component: eclipse-m2e-core Severity: urgent Assignee: mat.booth(a)redhat.com Reporter: danielsun3164(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, gerard(a)ryan.lt, mat.booth(a)redhat.com, mizdebsk(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1732101 --> https://bugzilla.redhat.com/attachment.cgi?id=1732101&action=edit .metadata/.log in new workspace Description of problem: I upgraded several eclipse packages today and M2E plugin stopped works. Version-Release number of selected component (if applicable): $ rpm -q eclipse-platform eclipse-m2e-core lucene eclipse-platform-4.17-3.fc33.x86_64 eclipse-m2e-core-1.16.2-1.fc33.noarch lucene-8.6.3-1.fc33.noarch How reproducible: Everytime Steps to Reproduce: 1. Open eclipse in a new workspace 2. Create a new Maven Project Actual results: A dialog as following was displayed: title: Multiple problems have occurred Message: The selected wizard could not be started. Problem Opening Wizard (Details: The selected wizard could not be started. Plug-in org.eclipse.m2e.core.ui was unable to load class org.eclipse.m2e.core.ui.internal.wizards.MavenProjectWizard. An error occurred while automatically activating bundle org.eclipse.m2e.core.ui (5821).) Updaing Maven Dependencies (Details: An internal error occurred during: "Updating Maven Dependencies". org/eclipse/m2e/core/internal/embedder/MavenExecutionContext) Expected results: M2E plugin should works without errors. Additional info: Openning an existing workspace with maven project got the same "Updaing Maven Dependencies" error. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1889417] New: Eclipse Repository loader constraint violation after adding JBoss Developer Tools 4.16
by bugzilla＠redhat.com 30 Nov '21

30 Nov '21

https://bugzilla.redhat.com/show_bug.cgi?id=1889417 Bug ID: 1889417 Summary: Eclipse Repository loader constraint violation after adding JBoss Developer Tools 4.16 Product: Fedora Version: 33 Status: NEW Component: eclipse-m2e-core Assignee: mat.booth(a)redhat.com Reporter: shihping.chan(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, gerard(a)ryan.lt, mat.booth(a)redhat.com, mizdebsk(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: After adding the rest of JBoss Developer Tools 4.16.0 to a relatively clean eclipse get An internal error occurred during: "Repository registry initialization". loader constraint violation: when resolving interface method 'org.apache.maven.index.context.IndexingContext org.apache.maven.index.NexusIndexer.addIndexingContextForced(java.lang.String, java.lang.String, java.io.File, org.apache.lucene.store.Directory, java.lang.String, java.lang.String, java.util.List)' the class loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @ca944c6 of the current class, org/eclipse/m2e/core/internal/index/nexus/NexusIndexManager, and the class loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @34e347a5 for the method's defining class, org/apache/maven/index/NexusIndexer, have different Class objects for the type org/apache/lucene/store/Directory used in the signature (org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @ca944c6, parent loader 'platform'; org.apache.maven.index.NexusIndexer is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @34e347a5, parent loader 'platform') Version-Release number of selected component (if applicable): eclipse-emf-core-2.22.0-2.fc33.noarch eclipse-usage-4.16.0-2.fc33.noarch eclipse-swt-4.16-13.fc33.x86_64 eclipse-m2e-workspace-0.4.0-16.fc33.noarch eclipse-equinox-osgi-4.16-13.fc33.x86_64 eclipse-ecf-core-3.14.8-5.fc33.noarch eclipse-platform-4.16-13.fc33.x86_64 eclipse-jdt-4.16-13.fc33.noarch eclipse-emf-runtime-2.22.0-2.fc33.noarch eclipse-gef-3.11.0-13.fc33.noarch eclipse-webtools-common-3.18.0-5.fc33.noarch eclipse-p2-discovery-4.16-13.fc33.noarch eclipse-webtools-servertools-3.18.0-5.fc33.noarch eclipse-emf-xsd-2.22.0-2.fc33.noarch eclipse-webtools-sourceediting-3.18.0-5.fc33.noarch eclipse-m2e-core-1.16.1-2.fc33.noarch eclipse-mpc-1.8.3-2.fc33.noarch eclipse-pydev-7.7.0-1.fc33.x86_64 How reproducible: Always Steps to Reproduce: 1. Remove ~/.eclipse 2. Note: part of JBoss Developer Tools 4.16.0 comes installed 3. Got to Marketplace, install every feature of 4.16.0. Actual results: On restart the following mesage An internal error occurred during: "Repository registry initialization". loader constraint violation: when resolving interface method 'org.apache.maven.index.context.IndexingContext org.apache.maven.index.NexusIndexer.addIndexingContextForced(java.lang.String, java.lang.String, java.io.File, org.apache.lucene.store.Directory, java.lang.String, java.lang.String, java.util.List)' the class loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @ca944c6 of the current class, org/eclipse/m2e/core/internal/index/nexus/NexusIndexManager, and the class loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @34e347a5 for the method's defining class, org/apache/maven/index/NexusIndexer, have different Class objects for the type org/apache/lucene/store/Directory used in the signature (org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @ca944c6, parent loader 'platform'; org.apache.maven.index.NexusIndexer is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @34e347a5, parent loader 'platform') Expected results: Features are added with no errors Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1891132] New: CVE-2020-27216 jetty: local temporary directory hijacking vulnerability
by bugzilla＠redhat.com 17 Aug '21

17 Aug '21

https://bugzilla.redhat.com/show_bug.cgi?id=1891132 Bug ID: 1891132 Summary: CVE-2020-27216 jetty: local temporary directory hijacking vulnerability Product: Security Response Hardware: All OS: Linux Status: NEW Component: vulnerability Keywords: Security Severity: medium Priority: medium Assignee: security-response-team(a)redhat.com Reporter: gsuckevi(a)redhat.com CC: abenaiss(a)redhat.com, aboyko(a)redhat.com, aileenc(a)redhat.com, akoufoud(a)redhat.com, alazarot(a)redhat.com, almorale(a)redhat.com, anstephe(a)redhat.com, aos-bugs(a)redhat.com, ataylor(a)redhat.com, bmontgom(a)redhat.com, chazlett(a)redhat.com, drieden(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, eparis(a)redhat.com, etirelli(a)redhat.com, ganandan(a)redhat.com, ggaughan(a)redhat.com, gmalinko(a)redhat.com, gvarsami(a)redhat.com, ibek(a)redhat.com, janstey(a)redhat.com, java-maint(a)redhat.com, java-sig-commits(a)lists.fedoraproject.org, jburrell(a)redhat.com, jcoleman(a)redhat.com, jjohnstn(a)redhat.com, jochrist(a)redhat.com, jokerman(a)redhat.com, jstastny(a)redhat.com, jwon(a)redhat.com, kconner(a)redhat.com, krathod(a)redhat.com, krzysztof.daniel(a)gmail.com, kverlaen(a)redhat.com, ldimaggi(a)redhat.com, mat.booth(a)redhat.com, mizdebsk(a)redhat.com, mnovotny(a)redhat.com, nstielau(a)redhat.com, nwallace(a)redhat.com, pbhattac(a)redhat.com, pdrozd(a)redhat.com, pjindal(a)redhat.com, rrajasek(a)redhat.com, rsynek(a)redhat.com, rwagner(a)redhat.com, sdaley(a)redhat.com, sochotni(a)redhat.com, sponnaga(a)redhat.com, sthorger(a)redhat.com, tcunning(a)redhat.com, tkirby(a)redhat.com, vbobade(a)redhat.com Target Milestone: --- Classification: Other In Eclipse Jetty versions 1.0 thru 9.4.32.v20200930, 10.0.0.alpha1 thru 10.0.0.beta2, and 11.0.0.alpha1 thru 11.0.0.beta2O, on Unix like systems, the system's temporary directory is shared between all users on that system. A collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory. If the attacker wins the race then they will have read and write permission to the subdirectory used to unpack web applications, including their WEB-INF/lib jar files and JSP files. If any code is ever executed out of this temporary directory, this can lead to a local privilege escalation vulnerability. References: https://bugs.eclipse.org/bugs/show_bug.cgi?id=567921 https://github.com/eclipse/jetty.project/security/advisories/GHSA-g3wg-6mcf… -- You are receiving this mail because: You are on the CC list for the bug.

1 29

[Bug 1857369] New: CVE-2019-17637 eclipse-webtools: XML external entity vulnerability in DTD Parser/Validator
by bugzilla＠redhat.com 25 May '21

25 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1857369 Bug ID: 1857369 Summary: CVE-2019-17637 eclipse-webtools: XML external entity vulnerability in DTD Parser/Validator Product: Security Response Hardware: All OS: Linux Status: NEW Component: vulnerability Keywords: Security Severity: medium Priority: medium Assignee: security-response-team(a)redhat.com Reporter: psampaio(a)redhat.com CC: eclipse-sig(a)lists.fedoraproject.org, gerard(a)ryan.lt, mat.booth(a)redhat.com Target Milestone: --- Classification: Other In all versions of Eclipse Web Tools Platform through release 3.18 (2020-06), XML and DTD files referring to external entities could be exploited to send the contents of local files to a remote server when edited or validated, even when external entity resolution is disabled in the user preferences. Upstream bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=458571 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1857370] New: CVE-2019-17637 eclipse-webtools: XML external entity vulnerability in DTD Parser/Validator [fedora-all]
by bugzilla＠redhat.com 25 May '21

25 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1857370 Bug ID: 1857370 Summary: CVE-2019-17637 eclipse-webtools: XML external entity vulnerability in DTD Parser/Validator [fedora-all] Product: Fedora Version: 32 Status: NEW Component: eclipse-webtools Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: mat.booth(a)redhat.com Reporter: psampaio(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, gerard(a)ryan.lt, mat.booth(a)redhat.com Target Milestone: --- Classification: Fedora This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of fedora-all. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1891670] New: Where is Eclispe WorkSpace Chose buttion
by bugzilla＠redhat.com 25 May '21

25 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1891670 Bug ID: 1891670 Summary: Where is Eclispe WorkSpace Chose buttion Product: Fedora Version: 32 Hardware: All OS: Linux Status: NEW Component: eclipse Severity: high Assignee: mat.booth(a)redhat.com Reporter: flydove(a)qq.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, dbhole(a)redhat.com, ebaron(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, jjohnstn(a)redhat.com, lef(a)fedoraproject.org, mat.booth(a)redhat.com, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1724459 --> https://bugzilla.redhat.com/attachment.cgi?id=1724459&action=edit Where is Eclispe WorkSpace Chose buttion Where is Eclispe WorkSpace Chose buttion -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1832383] New: Unable to build maven projects from eclipse
by bugzilla＠redhat.com 25 May '21

25 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1832383 Bug ID: 1832383 Summary: Unable to build maven projects from eclipse Product: Fedora Version: 32 Status: NEW Component: eclipse-m2e-core Severity: high Assignee: mat.booth(a)redhat.com Reporter: danielsun3164(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, gerard(a)ryan.lt, mat.booth(a)redhat.com, mizdebsk(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1685783 --> https://bugzilla.redhat.com/attachment.cgi?id=1685783&action=edit Eclipse metadata/.log Description of problem: Unable to build maven projects from eclipse Version-Release number of selected component (if applicable): $ rpm -q eclipse-jdt eclipse-m2e-core maven-archetype-common maven-artifact-transfer eclipse-jdt-4.15-5.module_f32+8555+6b76193d.noarch eclipse-m2e-core-1.15.0-3.module_f32+8482+8510b2e7.noarch maven-archetype-common-3.1.1-1.module_f32+8422+d2b9781b.noarch maven-artifact-transfer-0.11.0-2.fc32.noarch How reproducible: Everytime Steps to Reproduce: 1. Open Eclipse. 2. Try to create a new maven project or build a existing maven project 3. Actual results: An error dialog will be displayed. Expected results: Maven projects should be builded or created successfully. Additional info: According to https://bugzilla.redhat.com/show_bug.cgi?id=1704981 , Update "maven-archetype-common" from "3.1.1" to "3.1.2" could solve this problem, but I cannot find maven-archetype-common-3.1.2 package anywhere. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1891133] New: CVE-2020-27216 jetty: local temporary directory hijacking vulnerability [fedora-all]
by bugzilla＠redhat.com 12 May '21

12 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1891133 Bug ID: 1891133 Summary: CVE-2020-27216 jetty: local temporary directory hijacking vulnerability [fedora-all] Product: Fedora Version: 32 Status: NEW Component: jetty Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: mat.booth(a)redhat.com Reporter: gsuckevi(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, java-sig-commits(a)lists.fedoraproject.org, jjohnstn(a)redhat.com, krzysztof.daniel(a)gmail.com, mat.booth(a)redhat.com, mizdebsk(a)redhat.com, sochotni(a)redhat.com Target Milestone: --- Classification: Fedora This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of fedora-all. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1683547] New: lucene-7.7.1 is available
by bugzilla＠redhat.com 23 Apr '21

23 Apr '21

https://bugzilla.redhat.com/show_bug.cgi?id=1683547 Bug ID: 1683547 Summary: lucene-7.7.1 is available Product: Fedora Version: rawhide Status: NEW Component: lucene Keywords: FutureFeature, Triaged Assignee: akurtako(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, dbhole(a)redhat.com, dingyichen(a)gmail.com, eclipse-sig(a)lists.fedoraproject.org, java-sig-commits(a)lists.fedoraproject.org, jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com, lef(a)fedoraproject.org, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 7.7.1 Current version/release in rawhide: 7.7.0-1.fc30 URL: http://lucene.apache.org/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/7178/ -- You are receiving this mail because: You are on the CC list for the bug.

1 42

[Bug 1887176] New: Ecliple wont start after install.
by bugzilla＠redhat.com 23 Apr '21

23 Apr '21

https://bugzilla.redhat.com/show_bug.cgi?id=1887176 Bug ID: 1887176 Summary: Ecliple wont start after install. Product: Fedora Version: 32 Hardware: x86_64 OS: Linux Status: NEW Component: eclipse Assignee: mat.booth(a)redhat.com Reporter: pwrzonca(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, dbhole(a)redhat.com, ebaron(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, jjohnstn(a)redhat.com, lef(a)fedoraproject.org, mat.booth(a)redhat.com, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1720675 --> https://bugzilla.redhat.com/attachment.cgi?id=1720675&action=edit logfile Description of problem: Ecliple wont start after install. Version-Release number of selected component (if applicable): fedora 32, eclipse 2020-06 How reproducible: Steps to Reproduce: 1. Install eclipse 2. Try to start it 3. Actual results: Error massage that direct me to read log which doesn't say too much for me. Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1895529] New: Eclipse do not start
by bugzilla＠redhat.com 23 Apr '21

23 Apr '21

https://bugzilla.redhat.com/show_bug.cgi?id=1895529 Bug ID: 1895529 Summary: Eclipse do not start Product: Fedora Version: 33 Status: NEW Component: eclipse Assignee: mat.booth(a)redhat.com Reporter: pwrzonca(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, dbhole(a)redhat.com, ebaron(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, jjohnstn(a)redhat.com, lef(a)fedoraproject.org, mat.booth(a)redhat.com, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1727294 --> https://bugzilla.redhat.com/attachment.cgi?id=1727294&action=edit Log file Description of problem: Fresh install of eclipse. It does not start and an error message pops up with location of log file (enclosing). Version-Release number of selected component (if applicable): 1:4.16-13 How reproducible: Steps to Reproduce: 1. sudo dnf install eclipse 2. run eclipse 3. Actual results: Error message. Expected results: Working Eclipse. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1895560] New: not support for java 11
by bugzilla＠redhat.com 23 Apr '21

23 Apr '21

https://bugzilla.redhat.com/show_bug.cgi?id=1895560 Bug ID: 1895560 Summary: not support for java 11 Product: Fedora Version: 32 Hardware: x86_64 OS: Linux Status: NEW Component: eclipse Severity: medium Assignee: mat.booth(a)redhat.com Reporter: flydove(a)qq.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, dbhole(a)redhat.com, ebaron(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, jjohnstn(a)redhat.com, lef(a)fedoraproject.org, mat.booth(a)redhat.com, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1727315 --> https://bugzilla.redhat.com/attachment.cgi?id=1727315&action=edit Eclipse not found java 11 eclipse Bad start java 11 and Good Runing using java 1.8.x -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1902827] New: CVE-2020-27218 jetty: buffer not correctly recycled in Gzip Request inflation [fedora-all]
by bugzilla＠redhat.com 21 Apr '21

21 Apr '21

https://bugzilla.redhat.com/show_bug.cgi?id=1902827 Bug ID: 1902827 Summary: CVE-2020-27218 jetty: buffer not correctly recycled in Gzip Request inflation [fedora-all] Product: Fedora Version: 33 Status: NEW Component: jetty Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: mat.booth(a)redhat.com Reporter: gsuckevi(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, java-sig-commits(a)lists.fedoraproject.org, jjohnstn(a)redhat.com, krzysztof.daniel(a)gmail.com, mat.booth(a)redhat.com, mizdebsk(a)redhat.com, sochotni(a)redhat.com Target Milestone: --- Classification: Fedora This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of fedora-all. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1873489] New: Xorg/Wayland crash on os.kill(0, 15) executed from eclipse python debugger
by bugzilla＠redhat.com 08 Apr '21

08 Apr '21

https://bugzilla.redhat.com/show_bug.cgi?id=1873489 Bug ID: 1873489 Summary: Xorg/Wayland crash on os.kill(0, 15) executed from eclipse python debugger Product: Fedora Version: 32 Status: NEW Component: eclipse-pydev Assignee: mat.booth(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, jjohnstn(a)redhat.com, mat.booth(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: When debugging certain app I got Wayland crashes, then reproduced it on Xorg as well. Simplest reproduction I got to is to create a file that executes "os.kill(0, 15)" and run/debug it from eclipse. Version-Release number of selected component (if applicable): eclipse-equinox-osgi-4.14-5.fc32.x86_64 eclipse-jgit-5.6.0-2.fc32.noarch eclipse-jdt-4.14-5.fc32.noarch eclipse-pydev-7.7.0-1.fc32.x86_64 eclipse-egit-5.6.0-2.fc32.noarch eclipse-swt-4.14-5.fc32.x86_64 eclipse-ecf-core-3.14.6-4.fc32.noarch eclipse-platform-4.14-5.fc32.x86_64 eclipse-emf-core-2.20.0-5.fc32.noarch libwayland-egl-1.18.0-1.fc32.i686 libwayland-server-1.18.0-1.fc32.x86_64 xorg-x11-server-Xwayland-1.20.8-1.fc32.x86_64 qt5-qtwayland-5.14.2-4.fc32.x86_64 gnome-session-wayland-session-3.36.0-2.fc32.x86_64 xorg-x11-server-Xorg-1.20.8-1.fc32.x86_64 How reproducible: Always Steps to Reproduce: 1. create a python file with "import os; os.kill(0, 15)" 2. select "Run As"->"Python Run" Actual results: Eclipse crashes and Wayland/Xorg as well (Xorg restarts, Wayland stays dead) Expected results: Ideally Eclipse should stay unaffected but at least it'd be nice if Wayland/Xorg survived. Additional info: It also works when I start debugging any script and manually execute the "os.kill(0, 15)" from the pydev console. On the other hand everything works well when the process is started elsewhere and pydev is only accessed via "import pydevd; pydevd.settrace("127.0.0.1", True, True)" directly from the script (execution only kills the python process, Eclipse as well as Wayland/Xorg survives) -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1897901] New: [abrt] eclipse-pydev: module(): __init__.py:51:<module>:AttributeError: module 'importlib._bootstrap_external' has no attribute '_w_long'
by bugzilla＠redhat.com 08 Apr '21

08 Apr '21

https://bugzilla.redhat.com/show_bug.cgi?id=1897901 Bug ID: 1897901 Summary: [abrt] eclipse-pydev: module(): __init__.py:51:<module>:AttributeError: module 'importlib._bootstrap_external' has no attribute '_w_long' Product: Fedora Version: 33 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:c44fb866899d088156844cb8c4e9c964cd3a84bc;VAR IANT_ID=kde; Component: eclipse-pydev Assignee: mat.booth(a)redhat.com Reporter: dgunchev(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, jjohnstn(a)redhat.com, mat.booth(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Just started eclipse. Version-Release number of selected component: eclipse-pydev:1-8.0.0-1.fc33 Additional info: reporter: libreport-2.14.0 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-eclipse-a1bd11afe2c74d0e983356851c6ecc0b.scope cmdline: /usr/bin/python3 -u /usr/lib/eclipse/droplets/pydev/plugins/org.python.pydev.core_8.0.0.v20201103-1759/pysrc/pycompletionserver.py 33431 crash_function: module exception_type: AttributeError executable: /usr/lib/eclipse/droplets/pydev/plugins/org.python.pydev.core_8.0.0.v20201103-1759/pysrc/pycompletionserver.py interpreter: python3-3.9.0-1.fc33.x86_64 kernel: 5.8.18-300.fc33.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: #1 [/usr/lib64/python3.7/importlib/__init__.py:51] <module> #2 [/usr/lib64/python3.7/inspect.py:38] <module> #3 [/usr/lib64/python3.7/xmlrpc/server.py:110] <module> #4 [/usr/lib/eclipse/droplets/pydev/plugins/org.python.pydev.core_8.0.0.v20201103-1759/pysrc/_pydev_imps/_pydev_saved_modules.py:22] <module> #5 [/usr/lib/eclipse/droplets/pydev/plugins/org.python.pydev.core_8.0.0.v20201103-1759/pysrc/_pydevd_bundle/pydevd_constants.py:357] <module> #6 [/usr/lib/eclipse/droplets/pydev/plugins/org.python.pydev.core_8.0.0.v20201103-1759/pysrc/pycompletionserver.py:14] <module> -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1901132] New: Request to build eclipse-cdt for EPEL 8
by bugzilla＠redhat.com 08 Apr '21

08 Apr '21

https://bugzilla.redhat.com/show_bug.cgi?id=1901132 Bug ID: 1901132 Summary: Request to build eclipse-cdt for EPEL 8 Product: Fedora EPEL Version: epel8 Status: NEW Component: eclipse Assignee: lef(a)fedoraproject.org Reporter: kretschmer.jens(a)siemens.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, dbhole(a)redhat.com, ebaron(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, jjohnstn(a)redhat.com, lef(a)fedoraproject.org, mat.booth(a)redhat.com, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Please build eclipse-cdt for EPEL 8 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1888339] New: Error unpacking rpm package eclipse-platform-1:4.16-13.fc33.x86_64
by bugzilla＠redhat.com 01 Apr '21

01 Apr '21

https://bugzilla.redhat.com/show_bug.cgi?id=1888339 Bug ID: 1888339 Summary: Error unpacking rpm package eclipse-platform-1:4.16-13.fc33.x86_64 Product: Fedora Version: 33 Status: NEW Component: eclipse Assignee: mat.booth(a)redhat.com Reporter: mycroft8(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, dbhole(a)redhat.com, ebaron(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, jjohnstn(a)redhat.com, lef(a)fedoraproject.org, mat.booth(a)redhat.com, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora One RPM file associated with Eclipse in Fedora 33 beta is not installable. Error unpacking rpm package eclipse-platform-1:4.16-13.fc33.x86_64 And the verification step fails. This is a continuation of the same issue since Fedora 32. It does not help to completely remove and re-install Eclipse. The issue remains. It does not help to specifically enable the "latest" Eclipse. The only workaround I can find is to not use Fedora repo's for Eclipse. To reproduce, just try sudo dnf install eclipse-platform -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1840743] New: Eclipse won't open after installing eclipse-mpc
by bugzilla＠redhat.com 02 Dec '20

02 Dec '20

https://bugzilla.redhat.com/show_bug.cgi?id=1840743 Bug ID: 1840743 Summary: Eclipse won't open after installing eclipse-mpc Product: Fedora Version: 32 Status: NEW Component: eclipse-mpc Assignee: mat.booth(a)redhat.com Reporter: doug.hs(a)protonmail.ch QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, mat.booth(a)redhat.com, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1692717 --> https://bugzilla.redhat.com/attachment.cgi?id=1692717&action=edit Error log Description of problem: After installing the package eclipse-mpc, Eclipse fails right after selecting the workspace and clicking "Launch". See attached logs. Version-Release number of selected component (if applicable): 1.8.1 How reproducible: Always Steps to Reproduce: 1. Install Eclipse from GNOME Software (from Fedora 32 repositories). 2. Install Eclipse PDT (from Eclipse repositories, using "Install New Software" in the "Help" menu). 3. Install Eclipse Marketplace (dnf install eclipse-mpc). 4. Add/Select a workspace and try to launch it. Actual results: Instead of the Eclipse main window, I see a small popup saying an error has occurred and that I should check the logs at "~/eclipse-workspace/.metadata/.log". Eclipse then closes itself. Expected results: Eclipse should load the workspace as usual. Additional info: Creating a new workspace and launching it does not fix the problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1889065] New: cannot upgrade eclipse-mylyn from f32 to f33
by bugzilla＠redhat.com 01 Dec '20

01 Dec '20

https://bugzilla.redhat.com/show_bug.cgi?id=1889065 Bug ID: 1889065 Summary: cannot upgrade eclipse-mylyn from f32 to f33 Product: Fedora Version: 32 Status: NEW Component: eclipse-mylyn Assignee: extras-orphan(a)fedoraproject.org Reporter: heldwin(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: andjrobins(a)gmail.com, eclipse-sig(a)lists.fedoraproject.org, extras-orphan(a)fedoraproject.org, jerboaa(a)gmail.com, jjohnstn(a)redhat.com, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: While trying to upgrade one of my system from f323 to f33, I got these messages. Command used: dnf distro-sync --releasever=33 Version-Release number of selected component (if applicable): eclipse-mylyn-3.25.0-3.fc32.noarch eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch glassfish-jaxb-api-2.2.12-14.fc32.noarch Errors: Problem 1: package eclipse-mylyn-3.25.0-3.fc32.noarch requires osgi(jaxb-api), but none of the providers can be installed - glassfish-jaxb-api-2.2.12-14.fc32.noarch does not belong to a distupgrade repository - problem with installed package eclipse-mylyn-3.25.0-3.fc32.noarch Problem 2: package jaxb-api-2.3.3-2.fc33.noarch obsoletes glassfish-jaxb-api < 2.3.3-2 provided by glassfish-jaxb-api-2.2.12-14.fc32.noarch - package jaxb-runtime-2.3.3-4.fc33.noarch requires mvn(jakarta.xml.bind:jakarta.xml.bind-api), but none of the providers can be installed - package eclipse-mylyn-3.25.0-3.fc32.noarch requires osgi(jaxb-api), but none of the providers can be installed - problem with installed package glassfish-jaxb-core-2.2.11-16.fc32.noarch - package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires osgi(org.eclipse.mylyn.commons.core) = 3.25.0.v20200816.1126, but none of the providers can be installed - package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires osgi(org.eclipse.mylyn.commons.net) = 3.25.0.v20200816.1126, but none of the providers can be installed - package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires osgi(org.eclipse.mylyn.commons.repositories.core) = 1.17.0.v20200816.1126, but none of the providers can be installed - package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires osgi(org.eclipse.mylyn.commons.repositories.http.core) = 1.17.0.v20200816.1126, but none of the providers can be installed - package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires osgi(org.eclipse.mylyn.commons.ui) = 3.25.0.v20200816.1126, but none of the providers can be installed - package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires osgi(org.eclipse.mylyn.commons.workbench) = 3.25.0.v20200816.1126, but none of the providers can be installed - package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires osgi(org.eclipse.mylyn.commons.xmlrpc) = 3.25.0.v20200816.1126, but none of the providers can be installed - package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires osgi(org.eclipse.mylyn.tasks.core) = 3.25.0.v20200816.1126, but none of the providers can be installed - package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch requires osgi(org.eclipse.mylyn.tasks.ui) = 3.25.0.v20200816.1126, but none of the providers can be installed - glassfish-jaxb-core-2.2.11-16.fc32.noarch does not belong to a distupgrade repository - problem with installed package eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch Removing eclipse-mylyn pulls with it: apache-commons-lang-2.6-27.fc32.noarch bea-stax-api-1.2.0-20.fc32.noarch eclipse-mylyn-tasks-bugzilla-3.25.0-3.fc32.noarch glassfish-fastinfoset-1.2.15-2.fc32.noarch glassfish-jaxb-api-2.2.12-14.fc32.noarch glassfish-jaxb-core-2.2.11-16.fc32.noarch glassfish-jaxb-runtime-2.2.11-16.fc32.noarch glassfish-jaxb-txw2-2.2.11-16.fc32.noarch google-gson-2.8.6-3.fc32.noarch istack-commons-runtime-2.21-12.fc32.noarch jakarta-commons-httpclient-1:3.1-33.fc32.noarch relaxngDatatype-2011.1-12.fc32.noarch 1stax-ex-1.7.7-12.fc32.noarch xmlstreambuffer-1.5.4-11.fc32.noarch xsom-20140514-3.fc32.noarc but then we cannot add again eclipse-mylyn as it is not in f33 repo, if I look bug #1831437 (retired package) -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1862776] New: eclipse does not start after (atleast) upgrade to F31
by bugzilla＠redhat.com 24 Nov '20

24 Nov '20

https://bugzilla.redhat.com/show_bug.cgi?id=1862776 Bug ID: 1862776 Summary: eclipse does not start after (atleast) upgrade to F31 Product: Fedora Version: 31 Hardware: x86_64 OS: Linux Status: NEW Component: eclipse Severity: high Assignee: mat.booth(a)redhat.com Reporter: customercare(a)resellerdesktop.de QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, dbhole(a)redhat.com, ebaron(a)fedoraproject.org, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, jjohnstn(a)redhat.com, lef(a)fedoraproject.org, mat.booth(a)redhat.com, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1703200 --> https://bugzilla.redhat.com/attachment.cgi?id=1703200&action=edit startup crash logfile Description of problem: Eclipse does show the splash screen on startup, but does crash with: !ENTRY org.eclipse.osgi 4 0 2020-08-02 13:47:30.736 !MESSAGE Anwendungsfehler !STACK 1 java.lang.RuntimeException: Application "org.eclipse.ui.ide.workbench" could not be found in the registry. The applications available are: org.eclipse.wst.server.preview.preview, org.eclipse.wst.jsdt.core.JavaCodeFormatter, org.eclipse.ant.core.antRunner, org.eclipse.equinox.app.error, org.eclipse.equinox.p2.director, org.eclipse.equinox.p2.garbagecollector.application, org.eclipse.equinox.p2.publisher.InstallPublisher, org.eclipse.equinox.p2.publisher.EclipseGenerator, org.eclipse.equinox.p2.publisher.ProductPublisher, org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher, org.eclipse.equinox.p2.reconciler.application, org.eclipse.equinox.p2.repository.repo2runnable, org.eclipse.equinox.p2.repository.metadataverifier, org.eclipse.equinox.p2.artifact.repository.mirrorApplication, org.eclipse.equinox.p2.metadata.repository.mirrorApplication, org.eclipse.equinox.p2.touchpoint.natives.nativePackageExtractor, org.eclipse.equinox.p2.updatesite.UpdateSitePublisher, org.eclipse.equinox.p2.publisher.UpdateSitePublisher, org.eclipse.equinox.p2.publisher.CategoryPublisher, org.eclipse.help.base.infocenterApplication, org.eclipse.help.base.helpApplication, org.eclipse.help.base.indexTool, org.eclipse.xsd.ecore.importer.XSD2GenModel, org.eclipse.pde.build.Build, org.eclipse.pde.junit.runtime.uitestapplication, org.eclipse.pde.junit.runtime.legacytestapplication, org.eclipse.pde.junit.runtime.coretestapplication, org.eclipse.pde.junit.runtime.coretestapplicationnonmain, org.eclipse.pde.junit.runtime.nonuithreadtestapplication, org.eclipse.jdt.apt.core.aptBuild, org.eclipse.jdt.core.JavaCodeFormatter, org.eclipse.jdt.core.JavaIndexer, org.eclipse.emf.codegen.CodeGen, org.eclipse.emf.codegen.JMerger, org.eclipse.emf.codegen.ecore.Generator, org.eclipse.emf.importer.ecore.Ecore2GenModel, org.eclipse.emf.importer.java.Java2GenModel, org.eclipse.emf.importer.rose.Rose2GenModel. at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:252) at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:33) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:606) at org.eclipse.equinox.launcher.Main.run(Main.java:1477) at org.eclipse.equinox.launcher.Main.main(Main.java:1450) seems to be a conflict with required versions. Logfile attached. Version-Release number of selected component (if applicable): eclipse-ecf-core.noarch 3.14.6-3.fc31 eclipse-egit.noarch 5.6.0-2.fc31 eclipse-emf-core.noarch 1:2.20.0-3.fc31 eclipse-emf-runtime.noarch 2.20.0-3.fc31 eclipse-emf-xsd.noarch 2.20.0-3.fc31 eclipse-equinox-osgi.x86_64 1:4.14-5.fc31 eclipse-gef.noarch 3.11.0-9.fc31 eclipse-jdt.noarch 1:4.14-5.fc31 eclipse-jgit.noarch 5.6.0-1.fc31 eclipse-m2e-core.noarch 1.11.0-1.fc31 eclipse-m2e-workspace.noarch 0.4.0-13.fc31 eclipse-nls-de.noarch 4.10.0-1.fc31 eclipse-p2-discovery.noarch 1:4.14-5.fc31 eclipse-pde.x86_64 1:4.14-5.fc31 eclipse-platform.x86_64 1:4.14-5.fc31 eclipse-swt.x86_64 1:4.14-5.fc31 eclipse-webtools-common.noarch 3.13.0-1.fc31 eclipse-webtools-servertools.noarch 3.13.0-1.fc31 eclipse-webtools-sourceediting.noarch 3.13.0-1.fc31 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1838330] New: Unable to install eclipse
by bugzilla＠redhat.com 24 Nov '20

24 Nov '20

https://bugzilla.redhat.com/show_bug.cgi?id=1838330 Bug ID: 1838330 Summary: Unable to install eclipse Product: Fedora Version: 31 Status: NEW Component: eclipse Assignee: mat.booth(a)redhat.com Reporter: cquike(a)arcor.de QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, dbhole(a)redhat.com, ebaron(a)fedoraproject.org, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, jjohnstn(a)redhat.com, lef(a)fedoraproject.org, mat.booth(a)redhat.com, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Trying to install eclipse in a fresh fedora container with dnf fails: # dnf install eclipse-platform Last metadata expiration check: 0:14:08 ago on Wed May 20 22:15:50 2020. Error: Problem: conflicting requests - package eclipse-platform-1:4.14-5.fc31.x86_64 requires glassfish-el >= 3.0.1, but none of the providers can be installed - package eclipse-platform-1:4.11-3.fc31.x86_64 requires glassfish-el >= 3.0.1, but none of the providers can be installed - package glassfish-el-3.0.1-0.12.b08.module_f31+6519+12cd0b27.noarch is filtered out by modular filtering - package glassfish-el-3.0.1-0.12.b08.module_f31+6793+1c93c38e.noarch is filtered out by modular filtering - package glassfish-el-3.0.1-0.11.b08.fc31.noarch is filtered out by modular filtering I guess that enabling some module the dependency can be satisfied, but if I understand modularity correctly only rpm from modules can depend on other modules, right? How reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1813168] New: Cannot install - broken dependencies
by bugzilla＠redhat.com 24 Nov '20

24 Nov '20

https://bugzilla.redhat.com/show_bug.cgi?id=1813168 Bug ID: 1813168 Summary: Cannot install - broken dependencies Product: Fedora Version: 31 Status: NEW Component: eclipse-egit Assignee: rob.myers(a)gtri.gatech.edu Reporter: fedora(a)famillecollet.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com, mat.booth(a)redhat.com, rgrunber(a)redhat.com, rob.myers(a)gtri.gatech.edu Target Milestone: --- Classification: Fedora # dnf update --best Error: Problem: package eclipse-egit-5.6.0-2.fc31.noarch requires jgit >= 5.6.0, but none of the providers can be installed - cannot install the best update candidate for package eclipse-egit-5.3.0-2.fc31.noarch - package jgit-5.6.0-1.fc31.noarch is filtered out by modular filtering Indeed, the modular repository provides jgit 5.4 (eclipse:2019-06) or jgit 5.5 (eclipse:latest) -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1801198] New: upgrade of eclipse-webtools-sourceediting is impossible due to conflicts
by bugzilla＠redhat.com 24 Nov '20

24 Nov '20

https://bugzilla.redhat.com/show_bug.cgi?id=1801198 Bug ID: 1801198 Summary: upgrade of eclipse-webtools-sourceediting is impossible due to conflicts Product: Fedora Version: 31 Hardware: x86_64 OS: Linux Status: NEW Component: eclipse-webtools Severity: medium Assignee: mat.booth(a)redhat.com Reporter: R.Perdok(a)familieperdok.nl QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, gerard(a)ryan.lt, mat.booth(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Eclipse-webtools-sourceediting cannot be updates due to a conflict Version-Release number of selected component (if applicable): Problem: package eclipse-pdt-6.2.0-3.fc31.noarch requires osgi(org.eclipse.wst.jsdt.core), but none of the providers can be installed - package eclipse-pdt-6.2.0-3.fc31.noarch requires osgi(org.eclipse.wst.jsdt.ui), but none of the providers can be installed - package eclipse-pdt-6.2.0-3.fc31.noarch requires osgi(org.eclipse.wst.jsdt.web.core), but none of the providers can be installed - package eclipse-pdt-6.2.0-3.fc31.noarch requires osgi(org.eclipse.wst.jsdt.web.ui), but none of the providers can be installed - cannot install both eclipse-webtools-sourceediting-3.15.0-3.module_f31+7243+50fb5b11.noarch and eclipse-webtools-sourceediting-3.15.0-1.module_f31+6793+1c93c38e.noarch - cannot install both eclipse-webtools-sourceediting-3.15.0-3.module_f31+7243+50fb5b11.noarch and eclipse-webtools-sourceediting-3.15.0-1.module_f31+6519+12cd0b27.noarch - cannot install the best update candidate for package eclipse-webtools-sourceediting-3.15.0-1.module_f31+6793+1c93c38e.noarch - cannot install the best update candidate for package eclipse-pdt-6.2.0-3.fc31.noarch - package eclipse-webtools-sourceediting-3.13.0-1.fc31.noarch is filtered out by modular filtering ================================================================================================================================================================ Package Architecture Version Repository Size ================================================================================================================================================================ Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): eclipse-webtools-sourceediting noarch 3.15.0-1.module_f31+6519+12cd0b27 fedora-modular 33 M eclipse-webtools-sourceediting noarch 3.15.0-3.module_f31+7243+50fb5b11 updates-modular 12 M Transaction Summary ================================================================================================================================================================ Skip 2 Packages How reproducible: run dnf update Steps to Reproduce: 1.dnf update 2. 3. Actual results: Above error message Expected results: upgrade without error messages Additional info: Suggested options "--best --allowerasing" do not offer a solution. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

eclipse-sig November 2020