Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rpm-ostree compose tree fails to add custom package #4177

Open
ab78908 opened this issue Nov 29, 2022 · 2 comments
Open

rpm-ostree compose tree fails to add custom package #4177

ab78908 opened this issue Nov 29, 2022 · 2 comments

Comments

@ab78908
Copy link

ab78908 commented Nov 29, 2022

When I install a package on client side it succeeds:

rpm-ostree install pylon-6.1.1.19861-1.x86_64.rpm

$ rpm-ostree status
State: idle
Deployments:
● testremote:fedora/rawhide/x86_64/silverblue
Version: 38 (2022-11-22T23:02:08Z)
BaseCommit: c0dbc242ae8124af3d8879d2383c9d0350c1283ce151ef864c3d344983036bab
LocalPackages: pylon-6.1.1.19861-1.x86_64

But when I'm trying to add the same package to and image build, the build fails:

sudo rpm-ostree compose tree --repo=repo --cachedir=cache --unified-core fedora-silverblue-extra.yaml
....
Running posttrans scripts... 50 done
Writing rpmdb... done
error: Writing rpmdb: Error running transaction: file / conflicts between attempted installs of pylon-6.1.1.19861-1.x86_64 and filesystem-3.18-2.fc37.x86_64

@ab78908
Copy link
Author

ab78908 commented Nov 30, 2022

I guess it is another flavor of #4165
The RPM package .spec file (generated by alien) had entries like
%dir "/"
%dir "/opt/"
%dir "/etc/"
the first one causing issues with rpm-ostree compose tree command shown above,
while the later two were causing issues with rpm-ostree install command
after these lines were removed from the .spec file rpm-ostree works fine.

@lucab
Copy link
Contributor

lucab commented Nov 30, 2022

Thanks for the report. Yes this is what I was mentioning in the other ticket:

I'm not sure if shipping /etc directly in the package will result in a file conflict with other packages down the road [...]

I'm not aware of a way to fix this, other than tweaking the specfile. I'm surprised this works slightly differing when installing client-side, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants