[Bug 1800991] New: cannot upgrade eclipse because of eclipse-usage
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1800991
Bug ID: 1800991
Summary: cannot upgrade eclipse because of eclipse-usage
Product: Fedora
Version: 31
Status: NEW
Component: eclipse-usage
Assignee: extras-orphan(a)fedoraproject.org
Reporter: listes.00(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eclipse-sig(a)lists.fedoraproject.org,
extras-orphan(a)fedoraproject.org, mat.booth(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Cannot update eclipse, because eclipse-usage cannot find a dependency.
Not sure if it is because of the obsoletes eclipse-epp-logging <= 2.0.8-4
Version-Release number of selected component (if applicable):
eclipse-usage-4.11.0-1.fc31.noarch
eclipse-epp-logging-2.0.7-8.fc31.noarch
Informations:
Problème 1: package eclipse-usage-4.11.0-1.fc31.noarch requires
osgi(org.eclipse.epp.logging.aeri.core), but none of the providers can be
installed
- package eclipse-usage-4.11.0-1.fc31.noarch requires
osgi(org.eclipse.epp.logging.aeri.ide), but none of the providers can be
installed
- package eclipse-platform-1:4.14-5.fc31.x86_64 obsoletes eclipse-epp-logging
<= 2.0.8-4 provided by eclipse-epp-logging-2.0.7-8.fc31.noarch
- cannot install the best update candidate for package
eclipse-usage-4.11.0-1.fc31.noarch
- cannot install the best update candidate for package
eclipse-abrt-0.0.3-9.fc31.noarch
Problème 2: problem with installed package eclipse-usage-4.11.0-1.fc31.noarch
- package eclipse-usage-4.11.0-1.fc31.noarch requires
osgi(org.eclipse.epp.logging.aeri.core), but none of the providers can be
installed
- package eclipse-usage-4.11.0-1.fc31.noarch requires
osgi(org.eclipse.epp.logging.aeri.ide), but none of the providers can be
installed
- package eclipse-platform-1:4.14-5.fc31.x86_64 obsoletes eclipse-epp-logging
<= 2.0.8-4 provided by eclipse-epp-logging-2.0.7-8.fc31.noarch
- cannot install the best update candidate for package
eclipse-epp-logging-2.0.7-8.fc31.noarch
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 8 months
[Bug 1800970] New: dnf update of eclipse-usage-4.11.0-1.fc31.noarch fails
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1800970
Bug ID: 1800970
Summary: dnf update of eclipse-usage-4.11.0-1.fc31.noarch fails
Product: Fedora
Version: 31
Hardware: x86_64
OS: Linux
Status: NEW
Component: eclipse-usage
Severity: medium
Assignee: extras-orphan(a)fedoraproject.org
Reporter: colin.barker07(a)btinternet.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eclipse-sig(a)lists.fedoraproject.org,
extras-orphan(a)fedoraproject.org, mat.booth(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1661970
--> https://bugzilla.redhat.com/attachment.cgi?id=1661970&action=edit
output of rpm -qa
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.run 'dnf update'
2.
3.
Actual results:
Problem 1: package eclipse-usage-4.11.0-1.fc31.noarch requires
osgi(org.eclipse.epp.logging.aeri.core), but none of the providers can be
installed
- package eclipse-usage-4.11.0-1.fc31.noarch requires
osgi(org.eclipse.epp.logging.aeri.ide), but none of the providers can be
installed
- package eclipse-platform-1:4.14-5.fc31.x86_64 obsoletes eclipse-epp-logging
<= 2.0.8-4 provided by eclipse-epp-logging-2.0.7-8.fc31.noarch
- cannot install the best update candidate for package
eclipse-usage-4.11.0-1.fc31.noarch
- cannot install the best update candidate for package
eclipse-abrt-0.0.3-9.fc31.noarch
- package eclipse-epp-logging-2.0.8-1.module_f31+6165+9b01e00c.noarch is
filtered out by modular filtering
- package eclipse-epp-logging-2.0.8-2.module_f31+6519+12cd0b27.noarch is
filtered out by modular filtering
Problem 2: problem with installed package eclipse-usage-4.11.0-1.fc31.noarch
- package eclipse-usage-4.11.0-1.fc31.noarch requires
osgi(org.eclipse.epp.logging.aeri.core), but none of the providers can be
installed
- package eclipse-usage-4.11.0-1.fc31.noarch requires
osgi(org.eclipse.epp.logging.aeri.ide), but none of the providers can be
installed
- package eclipse-platform-1:4.14-5.fc31.x86_64 obsoletes eclipse-epp-logging
<= 2.0.8-4 provided by eclipse-epp-logging-2.0.7-8.fc31.noarch
- cannot install the best update candidate for package
eclipse-epp-logging-2.0.7-8.fc31.noarch
- package eclipse-epp-logging-2.0.8-1.module_f31+6165+9b01e00c.noarch is
filtered out by modular filtering
- package eclipse-epp-logging-2.0.8-2.module_f31+6519+12cd0b27.noarch is
filtered out by modular filtering
Expected results:
dnf update to complete with no dependency errors
Additional info:
output of rpm -qa attached as package.log
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 8 months
[Bug 1704981] New: Eclipse cannot import maven projects
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1704981
Bug ID: 1704981
Summary: Eclipse cannot import maven projects
Product: Fedora
Version: 30
Hardware: x86_64
OS: Linux
Status: NEW
Component: eclipse-m2e-core
Severity: high
Assignee: mat.booth(a)redhat.com
Reporter: proski(a)gnu.org
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 updating to Fedora 30, Eclipse fails to import maven based projects
Version-Release number of selected component (if applicable):
eclipse-jdt-4.11-4.fc30.noarch
eclipse-m2e-core-1.11.0-1.fc30.noarch
How reproducible:
Always
Steps to Reproduce:
1. Run Eclipse
2. File->Import->Maven->Checkout Maven Projects from SCM
3. Enter https://github.com/jenkinsci/stash-pullrequest-builder-plugin.git and
click "Finish
Actual results:
A message appears:
An internal error occurred during: "Importing Maven projects".
org.apache.lucene.document.Field.<init>(Ljava/lang/String;Ljava/lang/String;Lorg/apache/lucene/index/IndexableFieldType;)V
Expected results:
The project is imported successfully
Additional info:
Also tested with https://github.com/jenkinsci/stashnotifier-plugin.git
Message from ~/workspace/.metadata/.log:
!ENTRY org.eclipse.core.jobs 4 2 2019-04-30 16:42:11.456
!MESSAGE An internal error occurred during: "Importing Maven projects".
!STACK 0
java.lang.NoSuchMethodError:
org.apache.lucene.document.Field.<init>(Ljava/lang/String;Ljava/lang/String;Lorg/apache/lucene/index/IndexableFieldType;)V
at org.apache.maven.index.IndexerField.toField(IndexerField.java:96)
at
org.apache.maven.index.creator.MinimalArtifactInfoIndexCreator.updateDocument(MinimalArtifactInfoIndexCreator.java:267)
at
org.apache.maven.index.ArtifactContext.createDocument(ArtifactContext.java:195)
at
org.apache.maven.index.DefaultIndexerEngine.update(DefaultIndexerEngine.java:72)
at
org.apache.maven.index.DefaultIndexer.addArtifactsToIndex(DefaultIndexer.java:109)
at
org.apache.maven.index.DefaultNexusIndexer.addArtifactToIndex(DefaultNexusIndexer.java:337)
at
org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.addDocument(NexusIndexManager.java:588)
at
org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.mavenProjectChanged(NexusIndexManager.java:767)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:777)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:921)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:298)
at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:259)
at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:175)
at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
at
org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1336)
at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:143)
at
org.eclipse.m2e.core.ui.internal.wizards.ImportMavenProjectsJob$1.doCreateMavenProjects(ImportMavenProjectsJob.java:68)
at
org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:73)
at
org.eclipse.m2e.core.ui.internal.wizards.ImportMavenProjectsJob.runInWorkspace(ImportMavenProjectsJob.java:77)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:42)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 8 months
[Bug 1799304] New: eclipse-mylyn: FTBFS in Fedora rawhide/f32
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1799304
Bug ID: 1799304
Summary: eclipse-mylyn: FTBFS in Fedora rawhide/f32
Product: Fedora
Version: rawhide
Status: NEW
Component: eclipse-mylyn
Assignee: mat.booth(a)redhat.com
Reporter: releng(a)fedoraproject.org
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, jjohnstn(a)redhat.com,
mat.booth(a)redhat.com, rgrunber(a)redhat.com
Blocks: 1750908 (F32FTBFS)
Target Milestone: ---
Classification: Fedora
eclipse-mylyn failed to build from source in Fedora rawhide/f32
https://koji.fedoraproject.org/koji/taskinfo?taskID=41316836
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild
Please fix eclipse-mylyn 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-mylyn will be orphaned. Before branching of Fedora 33,
eclipse-mylyn 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
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1750908
[Bug 1750908] Fedora 32 FTBFS Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 8 months