On Sat, May 27, 2017 at 04:00:58PM +0200, David Kalnischkies wrote: > Control: reassign -1 libssl-dev 1.1.0e-2 > Control: retitle -1 libssl-dev: declare conflict with libssl1.0-dev to help > apt find solutions [...] > Not being installable is the problem of the package which isn't > installable – even if that is due to bugs in a package manager!
So why does this bug get assigned to libssl-dev then and not to libecryptfs-dev, with maybe a wishlist bug against libssl-dev (and apt)? In general, I disagree that we should declare a conflict at both sides of the conflict and that the package manager should be able to deal with a conflict on just one side. It's not a conflict that involves version numbers. However, if everybody agrees that this is the best solution for the next release, I will need permission from the release team to make such a change. Kurt