> Lets have some package installed on a system, which is already removed from
> the repository. This package might work just fine as long as their
> dependencies are satisfied. But after the dependencies change, the package
> needs to be removed.
A package installed on the system has its dependencies satisfied, by
definition. The only way to change its dependencies is to run an rpm
transaction. Such a transaction will fail if it can't satisfy the dependencies
of an already installed package.
> As long as the `libruby.so.3.2()(64bit)` is available, the
> rubygem-byebug-11.1.3-5.fc39.x86_64 package works fine. But is there a way to
> remove it from a system once the `libruby.so.3.2()(64bit)` is not available
> anymore?
Assuming "not available" as in "not available in the repositories", this
question is then irrelevant to rpm as it doesn't deal with repositories and so
can't know that.
If "not available" in the current rpm transaction, then that transaction will
simply fail due to `libruby.so.3.2()(64bit)` not being satisfied.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2938#discussioncomment-8681671
You are receiving this because you are subscribed to this thread.
Message ID:
<rpm-software-management/rpm/repo-discussions/2938/comments/8681...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
