[Rpm-maint] [rpm-software-management/rpm] How to obsolete package once their dependencies are not satisfied? (Discussion #2938)

[Vít Ondruch]

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. Is there a way to obsolete package under such condition?

The specific example could be this:

~~~
Problem 3: package rubygem-byebug-11.1.3-5.fc39.x86_64 from @System requires libruby.so.3.2()(64bit), but none of the providers can be installed
  - ruby-libs-3.2.2-181.fc39.x86_64 from @System  does not belong to a distupgrade repository
  - problem with installed package rubygem-byebug-11.1.3-5.fc39.x86_64
~~~

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?

[This](https://src.fedoraproject.org/rpms/fedora-obsolete-packages/pull-request/86#) ticket is the background for my question. 


-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2938
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/repo-discussions/2938 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20240228/8c1ac8d5/attachment-0001.html>