Unwanted directories added to RPM #1503
Comments
|
I uninstalled the Python package and installed an older version of the same Python package and installation was successful. However, the mysterious files and directories still exist in my RPM. |
|
@hellosputnik I've just also encountered this issue (without installation problems, though) on Fedora 28 box. After some googling around, it comes out, that it has nothing to do with fpm, virtualenv etc. This's an rpmbild's feature (see: https://fedoraproject.org/wiki/Releases/FeatureBuildId and https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo. |
|
Thanks @daoxxx! I really appreciate your response! |
|
@hellosputnik You're welcome. Guess you shold close the issue. |
stable changed to buster and buster included a newer rpm package and now the rpmbuild is including files like /usr/lib/.build-id/9d/3614c9a48200641b24890671bea43ef43c760b in our packages. So we'll base this image on stretch and then update all the things using the container to include --rpm-rpmbuild-define "_build_id_links none" when building RPMs to prevent those files from being included. Then we can update. jordansissel/fpm#1503
stable changed to buster and buster included a newer rpm package and now the rpmbuild is including files like /usr/lib/.build-id/9d/3614c9a48200641b24890671bea43ef43c760b in our packages. So we'll base this image on stretch and then update all the things using the container to include --rpm-rpmbuild-define "_build_id_links none" when building RPMs to prevent those files from being included. Then we can update. jordansissel/fpm#1503
This commit addresses a certain issue with `rpmbuild` in which certain packages will conflict with each other because they have identical `.build-id` links in the package. I can speculate from some comments I've seen that this might be do to electron versions the packages rely on, but I can't know for sure. Most relevant issues I've seen: jordansissel/fpm#1503 jgraph/drawio-desktop#259
_build_id_links is turned off because binary rpms would conflict with other similarly packaged packages (e.g. Slack desktop app). See jordansissel/fpm#1503
_build_id_links is turned off because binary rpms would conflict with other similarly packaged packages (e.g. Slack desktop app). See jordansissel/fpm#1503
When creating an RPM from a virtualenv (whether I use -s dir or -s virtualenv), unwanted directories and files are included in the RPM.
I do not specify
/usr/lib/.build-idanywhere and--editdoes not show the directories in the spec, butrpm -qlp output.rpmshows the directories.I have tried excluding and disabling dependencies, but nothing prevents those directories from showing up and failing my installations :( Has anyone else run into this issue?
When I try to install the generated RPM, yum complains about conflicts on
/usr/lib/.build-id/$filefrom the Python package that contains the virtualenv I used. If I uninstall the Python package, then I can install the FPM package (which is broken because it's missing those necessary Python packages that I uninstalled).The text was updated successfully, but these errors were encountered: