From 0ad68e1e57c7ad24193a8aeb53e3ec013c9bb4b2 Mon Sep 17 00:00:00 2001 From: salman Date: Thu, 24 Sep 2026 14:46:48 +0200 Subject: [PATCH] Exclude build-id links from rpm to avoid electron conflicts Two Electron applications built from the identical electron binary set package the same ELF build-id links under /usr/lib/.build-id, so installing trimsp next to musrflow failed the transaction test. Define _build_id_links none in the rpm spec so the package no longer claims those paths, regardless of the el9 build host. --- CHANGELOG.md | 8 ++++++++ packaging/linux/trimsp.spec.ejs | 6 ++++++ 2 files changed, 14 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index a8a097e..d5c77a0 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,13 @@ # Changelog +## Unreleased + +### Fixed + +- The RPM no longer packages ELF build-id links under `/usr/lib/.build-id`, + which previously conflicted when another Electron application built from the + same binary set (e.g. `musrflow`) was installed alongside `trimsp`. + ## 1.4.0 - 2026-08-27 Publication release of TRIMSP-NL Workbench corresponding to the modernization diff --git a/packaging/linux/trimsp.spec.ejs b/packaging/linux/trimsp.spec.ejs index e8d22a9..f41d614 100644 --- a/packaging/linux/trimsp.spec.ejs +++ b/packaging/linux/trimsp.spec.ejs @@ -4,6 +4,12 @@ %global __strip /bin/true %endif +# Electron bundles the identical helper binaries into every app, so the ELF +# build-id links under /usr/lib/.build-id collide when another Electron app +# (e.g. musrflow) is installed. Do not package build-id metadata. +%define _build_id_links none +%undefine _missing_build_ids_terminate_build + Name: <%= name %> Version: <%= version %> Release: <%= revision %>%{?dist}