dnf packages not removed on my final image
I'm running into an issue where some of my package listed in the
remove section of the dnf module are still in my final image.
I suspect that it's because these packages (fuzzel, alacritty and waybar in my case) are installed as a dependency of another package listed in the install section.
I wonder if there is a way to run the remove section after the install section as a workaround for this issue.
Another way would be to track down where these packages come from. I couldn't with just the bluebuild action logs, but I strongly suspect it is shipped with the niri package, I would appreciate it if someone can guide me to track down these packages (I don't really know much about rpm packaging ...)
I attached portion of my logs showing the packages that should be removed and when they are installed afterward.
Thank you in advance for your help and all the effort you put in this project.Solution:Jump to solution
For reference https://github.com/blue-build/modules/pull/462
GitHub
feat(dnf): exclude feature by benoitlx · Pull Request #462 · blue...
Implement what's being discussed in #460
15 Replies
are you sure you're on the latest update?
one way of doing it is to run
rpm-ostree update, if it says "No upgrade available." then probably you'll need to reboot
if there's an update then let it do it's thing and rebootMaybe this would be a good opportunity to add a way to exclude packages when installing.
Hmmm, there doesn't appear to be an arg for that with dnf
dnf -x
I saw it several times while looking at some containerfiles from ublueOh shit you're right
I was looking for
--exclude or something
looks like there isn't a long arg for it, just -xOk so yeah I think that would be something to include in the spec and the module
Nope I'm an idiot who can't read,
--exclude does exist
Ok, I'll make an issue to add this featureGitHub
feat: Add
exclude under install property · Issue #460 · blue-...A user was asking for a way to exclude certain packages from being installed. Since remove happens before install, we should make use of the --exclude/-x arg to exclude a list of packages when runn...
happens 🤷♀️
I was not when I read your message but I still have my unwanted packages in my image
It would be great, but would it not be kind of redundant to have a
remove and exclude section ? Also, is there a particular reason for not running the remove after install ?You could also try
install-weak-deps: falsewill try !
Remove happens first and will remove any packages that exist. The exclude would prevent the packages from even being installed
Is there a way to confirm my unwanted packages were installed because of
niri being installed ? The only reference I found in the niri copr is in niri.spec :
But since I don't know much about this file, I'm not sure what it implies.
I will try to create a PR implementing the exclude feature, a draft should be available in the end of the day
Indeed those packages are part of niri's weak dependenciesSolution
For reference https://github.com/blue-build/modules/pull/462
GitHub
feat(dnf): exclude feature by benoitlx · Pull Request #462 · blue...
Implement what's being discussed in #460
GitHub
feat: Add
exclude under install property · Issue #460 · blue-...A user was asking for a way to exclude certain packages from being installed. Since remove happens before install, we should make use of the --exclude/-x arg to exclude a list of packages when runn...