Hello community, here is the log from the commit of package certbot for openSUSE:Factory checked in at 2018-03-26 13:05:18 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/certbot (Old) and /work/SRC/openSUSE:Factory/.certbot.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "certbot" Mon Mar 26 13:05:18 2018 rev:19 rq:590447 version:0.22.2 Changes: -------- --- /work/SRC/openSUSE:Factory/certbot/certbot.changes 2018-02-01 21:28:38.555166270 +0100 +++ /work/SRC/openSUSE:Factory/.certbot.new/certbot.changes 2018-03-26 13:05:25.440254466 +0200 @@ -1,0 +2,56 @@ +Thu Mar 22 23:14:55 UTC 2018 - [email protected] + +- update to 0.22.2 + * Fixed + - A type error introduced in 0.22.1 that would occur during + challenge cleanup when a Certbot plugin raises an exception + while trying to complete the challenge was fixed. + + Despite us having broken lockstep, we are continuing to release + new versions of all Certbot components during releases for the + time being, however, the only packages with changes other than + their version number were: + + certbot + + More details about these changes can be found on our GitHub + repo: https://github.com/certbot/certbot/milestone/53?closed=1 + +- changes from 0.22.1 + * Changed + - The ACME server used with Certbot's --dry-run and --staging + flags is now Let's Encrypt's ACMEv2 staging server which + allows people to also test ACMEv2 features with these flags. + * Fixed + - The HTTP Content-Type header is now set to the correct value + during certificate revocation with new versions of the ACME + protocol. + - When using Certbot with Let's Encrypt's ACMEv2 server, + it would add a blank line to the top of chain.pem and between + the certificates in fullchain.pem for each lineage. + These blank lines have been removed. + - Resolved a bug that caused Certbot's --allow-subset-of-names + flag not to work. + - Fixed a regression in acme.client.Client that caused the + class to not work when it was initialized without + a ClientNetwork which is done by some of the other projects + using our ACME library. + + Despite us having broken lockstep, we are continuing to release + new versions of all Certbot components during releases for the t + ime being, however, the only packages with changes other than + their version number were: + + acme + certbot + + More details about these changes can be found on our GitHub + repo: https://github.com/certbot/certbot/milestone/51?closed=1 + +------------------------------------------------------------------- +Wed Mar 14 11:24:47 UTC 2018 - [email protected] + +- update to 0.22.0 + See https://github.com/certbot/certbot/blob/master/CHANGELOG.md + +------------------------------------------------------------------- Old: ---- v0.21.1.tar.gz New: ---- v0.22.2.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ certbot.spec ++++++ --- /var/tmp/diff_new_pack.xbe595/_old 2018-03-26 13:05:27.152192928 +0200 +++ /var/tmp/diff_new_pack.xbe595/_new 2018-03-26 13:05:27.156192785 +0200 @@ -19,7 +19,7 @@ # See also http://en.opensuse.org/openSUSE:Specfile_guidelines Name: certbot -Version: 0.21.1 +Version: 0.22.2 Release: 0 Summary: Let's Encrypt client License: Apache-2.0 @@ -47,7 +47,7 @@ BuildRequires: pkgconfig(openssl) BuildRequires: pkgconfig(python) >= 2.7 # install_requires -BuildRequires: python-acme = %{version} +BuildRequires: python-acme > 0.21.1 BuildRequires: python-josepy >= 1.0.1 #BuildRequires: python-argparse BuildRequires: python-configargparse @@ -104,7 +104,7 @@ # requires Requires: ca-certificates Requires: cron -Requires: python-acme = %{version} +Requires: python-acme > 0.21.1 #Requires: python-argparse Requires: python-certbot = %{version} Requires: python-configargparse ++++++ v0.21.1.tar.gz -> v0.22.2.tar.gz ++++++ ++++ 8609 lines of diff (skipped)
