https://bugzilla.redhat.com/show_bug.cgi?id=1720682
Bug ID: 1720682 Summary: Binary build-id conflicts with RCP application Product: Fedora Version: 30 Status: NEW Component: eclipse Assignee: mat.booth@redhat.com Reporter: jkang@redhat.com QA Contact: extras-qa@fedoraproject.org CC: akurtako@redhat.com, andjrobins@gmail.com, dbhole@redhat.com, ebaron@fedoraproject.org, eclipse-sig@lists.fedoraproject.org, jerboaa@gmail.com, jjohnstn@redhat.com, lef@fedoraproject.org, mat.booth@redhat.com, rgrunber@redhat.com Blocks: 1718921 Target Milestone: --- Classification: Fedora
When trying to install either of the updates to jmc:latest or jmc:7 [1], the installation fails with e.g.
file /usr/lib/.build-id/43/6307dc22dd874edd6c0bf49cd1d43b3b1980b2 conflicts between attempted installs of jmc-7.1.0-2.20190524hg4c9efa5eb5b8.module_f30+4549+4157fe94.x86_64 and eclipse-platform-1:4.11-4.fc30.x86_64
This build-id links to /usr/lib/jmc/jmc* for package: jmc This build-id links to /usr/lib/eclipse/eclipse* for package: eclipse-platform
This issue is new and prevents installation of jmc.
The thread [1] suggests that -g should be used but it looks like it was removed in [2]. This might explain why it didn't occur in previous releases. Should this fix be applied to the jmc package or to the eclipse package?
[1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/... [2] https://src.fedoraproject.org/rpms/eclipse/c/fd9180606a37bd4a6f0c378e3eb19b4...
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1718921 [Bug 1718921] Unable to install jmc updates because build-id conflicts with eclipse-platform
https://bugzilla.redhat.com/show_bug.cgi?id=1720682
--- Comment #1 from Mat Booth mat.booth@redhat.com --- Hmm, the reason I made this change was because we had this problem with the CDT standalone debugger: https://issues.jboss.org/browse/RHECLIPSE-114
https://bugzilla.redhat.com/show_bug.cgi?id=1720682
Severin Gehwolf sgehwolf@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sgehwolf@redhat.com
--- Comment #2 from Severin Gehwolf sgehwolf@redhat.com --- (In reply to Mat Booth from comment #1)
Hmm, the reason I made this change was because we had this problem with the CDT standalone debugger: https://issues.jboss.org/browse/RHECLIPSE-114
FWIW, the debuginfo issue has been worked around in jmc via: https://src.fedoraproject.org/rpms/jmc/blob/jmc/f/jmc.spec#_21
https://bugzilla.redhat.com/show_bug.cgi?id=1720682
--- Comment #3 from Jie Kang jkang@redhat.com --- Er for clarity, I missed a [1] in my original comment that should be:
[1] https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-339bc366c3 https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-e894e9ce53
https://bugzilla.redhat.com/show_bug.cgi?id=1720682
--- Comment #4 from Jie Kang jkang@redhat.com --- Curiously, the binaries for JMC and Eclipse are not the same. However I have spoken to Mark J. Wielaard and it is possible (but unlikely) that since some (JMC) are built without debuginfo, there might be too little data left to make unique build-ids.
It's also my understanding that building with '-g' will embed package name/dir/sources into the binary on which the build-id is based. This makes the workaround described in [1] strange to me as using '-g' should produce more differences for the build-id generator to work with. I will try to configure the JMC build to use '-g' but I also don't think the Fedora eclipse package needs to carry the changes made in [2].
[1] https://issues.jboss.org/browse/RHECLIPSE-114 [2] https://src.fedoraproject.org/rpms/eclipse/c/fd9180606a37bd4a6f0c378e3eb19b4...
https://bugzilla.redhat.com/show_bug.cgi?id=1720682
--- Comment #5 from Mat Booth mat.booth@redhat.com --- (In reply to Jie Kang from comment #4)
Curiously, the binaries for JMC and Eclipse are not the same. However I have spoken to Mark J. Wielaard and it is possible (but unlikely) that since some (JMC) are built without debuginfo, there might be too little data left to make unique build-ids.
It's also my understanding that building with '-g' will embed package name/dir/sources into the binary on which the build-id is based. This makes the workaround described in [1] strange to me as using '-g' should produce more differences for the build-id generator to work with. I will try to configure the JMC build to use '-g' but I also don't think the Fedora eclipse package needs to carry the changes made in [2].
I can make the following an SCL-specific patch, if that helps:
[1] https://issues.jboss.org/browse/RHECLIPSE-114 [2] https://src.fedoraproject.org/rpms/eclipse/c/ fd9180606a37bd4a6f0c378e3eb19b4a2acccc7a?branch=master
https://bugzilla.redhat.com/show_bug.cgi?id=1720682
--- Comment #6 from Jie Kang jkang@redhat.com --- (In reply to Mat Booth from comment #5)
(In reply to Jie Kang from comment #4)
Curiously, the binaries for JMC and Eclipse are not the same. However I have spoken to Mark J. Wielaard and it is possible (but unlikely) that since some (JMC) are built without debuginfo, there might be too little data left to make unique build-ids.
It's also my understanding that building with '-g' will embed package name/dir/sources into the binary on which the build-id is based. This makes the workaround described in [1] strange to me as using '-g' should produce more differences for the build-id generator to work with. I will try to configure the JMC build to use '-g' but I also don't think the Fedora eclipse package needs to carry the changes made in [2].
I can make the following an SCL-specific patch, if that helps:
Yes I would appreciate that, thanks!
I'm not even sure if it's possible for me to configure how the JMC launcher binary is compiled. The project has a .product file that describes it and some configuration like additional arguments for the .ini, but I haven't found any documentation on how the launcher is actually created. Do you know?
[1] https://issues.jboss.org/browse/RHECLIPSE-114 [2] https://src.fedoraproject.org/rpms/eclipse/c/ fd9180606a37bd4a6f0c378e3eb19b4a2acccc7a?branch=master
https://bugzilla.redhat.com/show_bug.cgi?id=1720682
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |MODIFIED
--- Comment #7 from Fedora Update System updates@fedoraproject.org --- FEDORA-MODULAR-2019-00f5ed2262 has been submitted as an update to Fedora 30 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-00f5ed2262
https://bugzilla.redhat.com/show_bug.cgi?id=1720682
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |ON_QA
--- Comment #8 from Fedora Update System updates@fedoraproject.org --- eclipse-2019_06-3020190801230108.f19b8f68 has been pushed to the Fedora 30 Modular testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-00f5ed2262
https://bugzilla.redhat.com/show_bug.cgi?id=1720682
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |MODIFIED
--- Comment #9 from Fedora Update System updates@fedoraproject.org --- FEDORA-MODULAR-2019-fb1ce318f5 has been submitted as an update to Fedora 30 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-fb1ce318f5
https://bugzilla.redhat.com/show_bug.cgi?id=1720682
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |ON_QA
--- Comment #10 from Fedora Update System updates@fedoraproject.org --- eclipse-2019_06-3020190805134222.f19b8f68 has been pushed to the Fedora 30 Modular testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-fb1ce318f5
https://bugzilla.redhat.com/show_bug.cgi?id=1720682
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |MODIFIED
--- Comment #11 from Fedora Update System updates@fedoraproject.org --- FEDORA-MODULAR-2019-fb1ce318f5 has been submitted as an update to Fedora 30 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-fb1ce318f5
https://bugzilla.redhat.com/show_bug.cgi?id=1720682
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |ON_QA
--- Comment #12 from Fedora Update System updates@fedoraproject.org --- eclipse-2019_06-3020190807134759.6ebe2c0f has been pushed to the Fedora 30 Modular testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-fb1ce318f5
https://bugzilla.redhat.com/show_bug.cgi?id=1720682
--- Comment #13 from Jie Kang jkang@redhat.com --- I've completed a build of JMC and it looks like there are no conflicts; thanks for updating this.
$ rpm -qpl jmc-7.1.0-2.20190524hg4c9efa5eb5b8.module_f30+5573+67d8d3e6.x86_64.rpm | grep build-id /usr/lib/.build-id /usr/lib/.build-id/e9 /usr/lib/.build-id/e9/cf13ad0c51bc1a3987e713cae9c9a54060263f
$ rpm -qpl eclipse-platform-4.12-6.module_f30+5264+0fe54b96.x86_64.rpm | grep build-id /usr/lib/.build-id /usr/lib/.build-id/33 /usr/lib/.build-id/33/81f1e174e69a404b75e5a20a799612e04c6eaf /usr/lib/.build-id/48 /usr/lib/.build-id/48/ef88685b3e19575b7e8db0a4da874a2cf9cc27 /usr/lib/.build-id/80 /usr/lib/.build-id/80/a4a0e6d8f57bc184f015cd5ec88048af2806cb /usr/lib/.build-id/ba /usr/lib/.build-id/ba/bdfc154fc7ea1a00cb3eea63c9dd27d2d31ede /usr/lib/.build-id/c9 /usr/lib/.build-id/c9/6bbe5036fda5c9875ffeb2eb6d16f426de5d65
https://bugzilla.redhat.com/show_bug.cgi?id=1720682
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Fixed In Version| |eclipse-2019_06-30201908071 | |34759.6ebe2c0f Resolution|--- |ERRATA Last Closed| |2019-08-15 18:10:48
--- Comment #14 from Fedora Update System updates@fedoraproject.org --- eclipse-2019_06-3020190807134759.6ebe2c0f has been pushed to the Fedora 30 Modular stable repository. If problems still persist, please make note of it in this bug report.
eclipse-sig@lists.stg.fedoraproject.org
-
bugzilla＠redhat.com