Bug 1967194

Summary: kicad fails to build in Fedora 35+: Broken RPATH will fail rpmbuild
Product: [Fedora] Fedora Reporter: Tomáš Hrnčiar <thrnciar>
Component: kicadAssignee: Steven A. Falco <stevenfalco>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: aimylios, alain.vigne.14, gmarr, kiarakovalevsky, mhroncok, stevenfalco, thibault, thrnciar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-06-03 13:37:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1927309, 1890881    

Description Tomáš Hrnčiar 2021-06-02 15:23:47 UTC
kicad fails to build in Fedora 35+


Related section in packaging guidelines.

+ /usr/lib/rpm/check-rpaths
* WARNING: 'check-rpaths' detected a broken RPATH OR RUNPATH and will cause
*          'rpmbuild' to fail. To ignore these errors, you can set the
*          '$QA_RPATHS' environment variable which is a bitmask allowing the
*          values below. The current value of QA_RPATHS is 0x0000.
*    0x0001 ... standard RPATHs (e.g. /usr/lib); such RPATHs are a minor
*               issue but are introducing redundant searchpaths without
*               providing a benefit. They can also cause errors in multilib
*               environments.
*    0x0002 ... invalid RPATHs; these are RPATHs which are neither absolute
*               nor relative filenames and can therefore be a SECURITY risk
*    0x0004 ... insecure RPATHs; these are relative RPATHs which are a
*               SECURITY risk
*    0x0008 ... the special '$ORIGIN' RPATHs are appearing after other
*               RPATHs; this is just a minor issue but usually unwanted
*    0x0010 ... the RPATH is empty; there is no reason for such RPATHs
*               and they cause unneeded work while loading libraries
*    0x0020 ... an RPATH references '..' of an absolute path; this will break
*               the functionality when the path before '..' is a symlink
* Examples:
* - to ignore standard and empty RPATHs, execute 'rpmbuild' like
*   $ QA_RPATHS=$(( 0x0001|0x0010 )) rpmbuild my-package.src.rpm
* - to check existing files, set $RPM_BUILD_ROOT and execute check-rpaths like
*   $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths
ERROR   0002: file '/usr/lib/python3.10/site-packages/_pcbnew.so' contains an invalid runpath '/builddir/build/BUILD/kicad-5.1.10/x86_64-redhat-linux-gnu/3d-viewer/3d_cache/sg' in [/builddir/build/BUILD/kicad-5.1.10/x86_64-redhat-linux-gnu/3d-viewer/3d_cache/sg:]
ERROR   0010: file '/usr/lib/python3.10/site-packages/_pcbnew.so' contains an empty runpath in [/builddir/build/BUILD/kicad-5.1.10/x86_64-redhat-linux-gnu/3d-viewer/3d_cache/sg:]
error: Bad exit status from /var/tmp/rpm-tmp.lWmi3I (%install)

For the build logs, see:

For all our attempts to build kicad with Python 3.10, see:

Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.10:

Let us know here if you have any questions.

Python 3.10 will be included in Fedora 35. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.10.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.

Comment 1 Steven A. Falco 2021-06-03 13:37:20 UTC
Fixed in version 1:5.1.10-3.

Copr build https://copr.fedorainfracloud.org/coprs/g/python/python3.10/build/2222625/