Did some major cleanup of this bug. Debdiffs attached for review.
In general, the primary change for the backport was to modify the
package to build against Python 2 instead of Python 3; one code change
was needed in certbot to disable API documentation as the necessary
sphinx module is not
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640978
Title:
[SRU] Backport letsencrypt 0.14.2
To manage notifications about this bug go to:
Unless we want this package to suddenly break for approximately 10,000
users in February, I think we probably want to do an SRU to Certbot
version 0.21.1 or higher. I wrote more about the problem in the relevant
issue at https://bugs.launchpad.net/ubuntu/+source/python-
letsencrypt/+bug/1745126.
FYI pushed some backporting from bionic to xenial without touching
existing Python dependencies:
https://launchpad.net/~kraut.hosting/+archive/ubuntu/certbot/+packages
Would recommend to rebase this SRU effort on the packages we have in
bionic now anyway.
So far my push does only cover Certbot
This is still a valid issue for everyone want to do a proper QA chain in
software delivery. Both the recent Snap package from Robie as the
certbot PPA by our Debian heroes have the problem on different install
times you have different versions installed. On a big bunch of boxes
this gives us the
I agree it would be a shame, but we need someone to sort out the build
failures and make sure the packages are in proper shape. Robie, since
you were the original backporter, would you be able to drive this
forward? The point release is nearing and I'd prefer not to have stale
packages in
As a developer of letsencrypt/certbot, it'll be pretty disappointing to
us if we can't some kind of update here. In addition to the many bugs
listed in the original description that would be fixed by this SRU, the
python-letsencrypt-apache package has been unable to obtain new
certificates since
Please someone look into the build failures in the nearest days. If
there will be no movement on these packages I will be removing them from
xenial-proposed and marking the bug as Won't Fix (as per SRU policy).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Oh, I see the Xenial update was blocked by build failures.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640978
Title:
[SRU] Backport letsencrypt 0.14.2
To manage notifications about this bug go
Should this update just be let into Xenial now?
Someone needs to start yet another backport of certbot for LP: #1745227.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640978
Title:
[SRU] Backport
While I didn't look any more into the build failure for the letsencrypt
package (let me know if you'd like me to), I added a check to
https://wiki.ubuntu.com/StableReleaseUpdates/Certbot/TestScript testing
that a symlink is properly created in the user's PATH. The test passes
on the letsencrypt
Thanks for approving the binary.
Tests passed for the proposed Xenial packages using
https://wiki.ubuntu.com/StableReleaseUpdates/Certbot/TestScript.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unfortunately the test script at
https://wiki.ubuntu.com/StableReleaseUpdates/Certbot/TestScript cannot
be used to test the Xenial packages yet because the python-certbot-nginx
binary still needs to be accepted. See
https://launchpad.net/ubuntu/xenial/+queue.
Is someone able to approve this
** No longer affects: python-letsencrypt (Ubuntu Yakkety)
** No longer affects: python-letsencrypt (Ubuntu)
** No longer affects: python-letsencrypt-apache (Ubuntu)
** No longer affects: python-letsencrypt-apache (Ubuntu Yakkety)
--
You received this bug notification because you are a member
Hello Peter, or anyone else affected,
Accepted python-letsencrypt into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/python-
letsencrypt/0.4.1-1ubuntu0.16.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing
Hello Peter, or anyone else affected,
Accepted python-certbot-apache into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/python-certbot-apache/0.14.2-0ubuntu0.16.04.1 in a few hours, and then
in the -proposed repository.
Please help us by
Hi Peter,
Robie is on leave the next few days, but here's what I know:
1) As far as I can tell all the packages we expect to see in Zesty are
in zesty-proposed now. They bake for at least a week there. Someone
needs to go through the testing of the packages from proposed and update
the metadata
What are next steps here? Is the Zesty SRU ready to go? Does Robie (or
someone else) need to make a python-certbot package for Xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640978
Title:
I just successfully ran the test script I provided earlier on the
proposed Ubuntu Zesty packages. I had to make a couple modifications to
properly install the packages from the proposed archive. An updated
version of the script is attached.
** Attachment added: "ubuntu-test.sh"
I don't see an upload of the python-certbot package in the -proposed
queue for Xenial, am I missing something?
+python-letsencrypt (0.4.1-1ubuntu0.16.04.1) xenial; urgency=medium
+
+ * Drop letsencrypt binary package; this is now produced by the
+python-certbot package (LP: #1640978)
--
20 matches
Mail list logo
