On 24/03/2020 23:52, Harlan Lieberman-Berg wrote: >> I could fix the issue by upgrading python3-certbot-apache to version >> 1.1.0-1. > Hi Damien, > > Yes, these two versions are not fully compatible. I didn't put in a > version restriction because mixing packages from testing into a stable > installation can result in breakage (such as you've ran into). If you > really want to do so, make sure that you pull not only the package > from testing, but all the things that reverse-depend on it. For > certbot, the easiest way to do that is to specify that you want to > install the leaf package from testing (python3-certbot-apache), rather > than the middle package (certbot, or python3-certbot). That should > reliably upgrade certbot itself, if it's necessary to do so. > > That said, I'll talk with upstream and see if I can add some level of > version protection to keep it from happening in the future.
As a standard user, this is not the behavior that I would expect from the package manager. I can usually safely mix packages from stable, testing and more thanks to a proper apt pinning configuration, and the package manager tells me if I can upgrade a package e.g. from testing without wrecking havoc my system. But I understand your point of view and the solution chosen. Thank you for your feedback! kind regards,
