Hi,
Am 29.12.2021 um 21:13 schrieb Maciej (Matchek) Bliziński via maintainers
:
> Setting a conflict sounds like a harsh way to do it. Maybe a softer approach
> would suffice? We had a way of obsoleting packages, didn't we?
>
> http://wiki.opencsw.org/obsoleting-packages
>
Setting a conflict sounds like a harsh way to do it. Maybe a softer
approach would suffice? We had a way of obsoleting packages, didn't we?
http://wiki.opencsw.org/obsoleting-packages
https://www.opencsw.org/2012/05/pkgutil-cleanup/
–Maciej
İhsan Doğan via maintainers escreveu no dia
quarta,
Hello,
I’ve updated today unbound to the most recent version and this version comes
also with a new version of libunbound. The new version in the catalog is now
libunbound8, but libunbound2 also in the catalog.
How do I get rid of the old version? I guess the easiest is to set a conflict
to
