-
Notifications
You must be signed in to change notification settings - Fork 192
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
--skip-inactive switch #1837
Comments
Take provisioning with Ansible, for example. It expects command to be idempotent. |
I agree something like this could be useful, though
E.g. in this case, isn't
That would be |
For some reason with version 2022.2 as found in coreos, I still get |
@akostadinov This is when trying to install a local RPM of NetworkManager, right? Is the intent there that you want that exact RPM to be installed if the base ever dropped NetworkManager? |
Intent was to download a number of RPMs and install them from local storage. I couldn't make that work with a random set of RPMs. So I manually installed only
Btw this solution is not ideal because these packages remain as |
Scripting
rpm-ostree
is a little bit cumbersome when one of the programs in a list is already provided in base, because without--allow-inactive
we get an error and with--allow-inactive
it would get added to “inactive requests”. (In my example, I target both FSB29 and FSB30, so I get different results.) For not getting a larger list of inactive requests clutteringrpm-ostree status
output, I think adding a--skip-inactive
or--ignore-inactive
switch would be a good solution for just ignoring those packages. What do you think? :)The text was updated successfully, but these errors were encountered: