Your message dated Sat, 08 Feb 2020 14:23:35 +0000 with message-id <a894a0233c2d264936953d7a69507573c4a5742a.ca...@adam-barratt.org.uk> and subject line Closing bugs included in 9.12 has caused the Debian Bug report #941126, regarding stretch-pu: package dehydrated/0.6.2-2+deb9u1 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 941126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: release.debian.org User: release.debian....@packages.debian.org Usertags: pu Tags: stretch Hi SRM, It was brought to my attention that stretch's version of dehydrated has a few issues. They could be resolved by adding a bunch of patches on top of the current versions, but I'd like to propose to instead backport the buster version as it is into stretch. From my side, the buster version is much more tested by me, as well as somewhat "looked after" by the upstream developer (who, for example, contacted me a few months ago to be sure it had a few patches). Updating the stretch version would also bring in a few features that might be interesting for some users: * ACMEv2 support (related, ISTR hearing LE wanted to retire ACMEv1 at some point, so bringing in support for v2 into stretch earlier would be a good idea) * a bunch of new hook types * support for OCSP From what I can see, the breakages would pretty much account to the following: * you need a new --accept-terms flag while creating a new account (might break autoamted deployments who need to create a new account?) * only since v0.6.0 the upstream developer made clear that users should not hardcode a list of hook, and it's known many users did it, so hook scripts may break due to unknown hook types * this also changes the default endpoint to ACMEv2. It should be totally transparent for most users, and those who really need ACMEv1 (why?) would need to explicitly specify it. IMHO, it would be best to just take the buster version as-is, without starting a whack-a-mole in backporting fixes, even if it would be somewhat trivial (the lack of ACMEv2 means many can be skipped), but they would have so many conflicts that missing bits and causing (also subtle… it's bash after all) bugs makes me prefer not to try it. If this route is accepted, I'd keep both stretch and buster updated at the same time, if case further changes are required in the future. What's your opinion? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Package: release.debian.org Version: 9.12 Hi, Each of the uploads referred to by these bugs was included in today's oldstable point release. Regards, Adam
--- End Message ---
