David, thank you for the detailed explanation and the tip (yes, I'm still learning how the BTS works ).
On 4/24/20 9:53 PM, David Kalnischkies wrote: > Anyway, as there is nothing apt can really do about this I have to > reassign back even if I dislike bug-pingpong. Feel free to ask if you > have come up with a specific solution for your problem and want some > feedback from us regarding apt, but be prepared to explain a lot in your > question as apt developers are "only" (FSVO) experts in apt, not in the > dependency trees of all of Debian (you may consider us the rubber duck > debugging of dependency resolution). 😉 > > > Best regards > > David Kalnischkies I have a question: let's say that I change the recommends, like the following Recommends: runit-systemd | runit-sysv | runit-init What happens in a given system if the "runit-systemd" package is not in the apt index (the package is not in the repository)? What happens if the 'runit-systemd' package exists, but one of its dependency, like, for instance, 'systemd-sysv' does not exists in the repository? Is apt able to jump to the next alternative (runit-sysv), or it will proceed without recommends, or it will give an error? I'm asking because there are downstreams (like Devuan) that blacklist systemd packages in their archive and I would like to understand what will happen there. Regards, Lorenzo
