eclipse-sig August 2020

eclipse-sig@lists.stg.fedoraproject.org

1 participants
56 discussions

[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 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 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 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 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 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 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

eclipse-sig August 2020