Bug#954189: Backport to buster?
Please backport the 0.2.1 package from bullseye to buster. The 0.0.62 package currently in buster no longer works for new installs, and will stop working for renewals of current domain certificates in July 2020. The 0.2.1 tag of acmetool is two years old and should build with the golang 1.11 package in Buster. The systemd unit file int he 0.0.62 package has also been broken by the /var/run -> /run tempfiles changes. Anyone who wants to continue using acmetool has to manually install the package from unstable, so the distro might as well do it for us. Thanks for packaging acmetool! -r
Bug#954189: Backport to buster?
On Monday 27 April 2020 11:15:30 Paul van Tilburg wrote: > Hi! > > This bug report was originally about buster and in my opinion a > backport is necessary (stretch also had one). I reckon mostly servers > use Let's Encrypt, and they mostly run Debian buster/stable. > Given that upstream doesn't seem to change to that much, is that a > possibility? > > I didn't reopen this bug report and will leave that to the maintainer's > discretion, however, I did want to mention this. Yes, I reported this bug to Debian Buster, but in Buster release this bug is not still fixed. So I think it should stay open. -- Pali Rohár pali.ro...@gmail.com
Bug#954189: Backport to buster?
Hi! This bug report was originally about buster and in my opinion a backport is necessary (stretch also had one). I reckon mostly servers use Let's Encrypt, and they mostly run Debian buster/stable. Given that upstream doesn't seem to change to that much, is that a possibility? I didn't reopen this bug report and will leave that to the maintainer's discretion, however, I did want to mention this. Kind regards, Paul -- Web: http://paul.luon.net/ | E-mail: p...@luon.net Matrix: @paul:luon.net | GnuPG: 0xC6DE073EDA9EEC4D
