I've verified all the versions of the queue assuming we are backporting
in SRUs <= 0.10.2-1 of python-{acme,certbot{,-apache,-nginx}} only and
leaving behind python-letsencrypt and python-letsencrypt-apache. So
let's retitle for exactly this.
** Summary changed:
- letsencrypt 0.4.1 contains numer
No changes needed to python-letsencrypt-apache: this will be left as-is
in Xenial, will use python-letsencrypt which is only being changed to
drop the letsencrypt package for the transition (libraries stay all the
same).
** Changed in: python-certbot (Ubuntu Yakkety)
Status: New => In Progr
Setting all tasks for which I see an upload in the queue as "In
Progress" so I can more easily see what's what. Here's my current view
of the queues:
python-acme
queue/xenial/unapproved/cb94bae
queue/yakkety/unapproved/15d7282
python-certbot
queue/xenial/new/e67c69a
queue/yakkety/unapproved/c6e7c
python-letsencrypt and python-letsencrypt-apache don't exist in Yakkety
or Zesty, so let's mark those Invalid as there is no action to take for
these packages neither in Yakkety nor Zesty (only Xenial).
** Changed in: python-letsencrypt-apache (Ubuntu)
Status: Fix Released => Invalid
** Ch
** Also affects: python-certbot-apache (Ubuntu)
Importance: Undecided
Status: New
--
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:
letsencrypt 0.4.1 contains numerous bugs fixe
python-letsencrypt dropping the letsencrypt binary uploaded.
If you'd like me to have access to the git repos you'll need to add
raof-guest to the letsencrypt group (or, alternatively, make the git
repository accessible to collab-maint).
--
You received this bug notification because you are a me
Harlan and the other Debian developers have git trees here:
https://alioth.debian.org/plugins/scmgit/cgi-
bin/gitweb.cgi?a=project_list;pf=letsencrypt
Maybe Chris should also get access to those repos?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Can I suggest that you maintain these packages in a git tree somewhere
(if you aren't doing so already), create branches for the Ubuntu stable
releases you're targeting, and then get reviews straight from there?
I'll be happy to do an SRU review straight from a git branch. Then
review changes could
That's great Chris!
We had some discussions yesterday about whether this has taken long
enough that 0.10.x should be considered for the SRU instead. 0.10.1 has
been in the field for 13 days; people found a couple of bugs in it, but
they only affected new 0.10.x functionality rather than being
regr
Sorry; LCA and then email backlog. I'll upload new packages tomorrow.
--
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:
letsencrypt 0.4.1 contains numerous bugs fixed upstream
To manage
Any news? I feel that changing python-letsencrypt as well exceeds the
bounds of the SRU hat I'm wearing - it should have review from a
different uploader as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
I think it's my job to gently nudge whoever it is that's making the
slightly tweaked packages here, but I'm not sure whether it should be
Chris or Harlan... if all else is equal perhaps it should be Chris,
since we also have a new 0.10.1 release that needs to be packaged for
sid and that would be i
Based on https://irclogs.ubuntu.com/2017/01/12/%23ubuntu-
release.html#t13:47, can you upload a python-letsencrypt for Xenial that
drops the letsencrypt package please? We'll need to accept these all
together.
Please remember to run the update-maintainer field when preparing these
source packages.
I'm confused on a couple of points. Here's my understanding:
AFAICT, there are three source packages in play here: src:python-acme,
src:python-letsencrypt, and src:python-certbot.
src:python-acme appears relatively straightforward. A version bump is
needed for new features used by this proposed u
Packages uploaded to the unapproved queue, awaiting review.
I changed the version numbers (so that the version in Xenial < Yakkety <
Zesty), and added bug links.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
* nod. We haven't changed any of the preexisting API calls or semantics,
so even unpackaged clients should be fine.
--
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:
letsencrypt 0.4.1 con
It's the clients that are *unpackaged* that are the most concerning.
Packaged clients we can update if necessary; random ad-hoc clients not
so much 😀
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16409
The changes in python-acme were comparatively minor. A few bugs were
fixed; one new feature was added to the API (support for DNS-01
challenges); some protocol messages were removed (because they were
believed to have security problems, were never used by Let's Encrypt,
and were removed from the IE
** Also affects: python-certbot-nginx (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-certbot-nginx (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Hm. It was unclear to me that this requires updating python-acme, python
library expected to be used by 3rd parties.
Have any python-acme APIs changed? What are the chances that the update
will break downstream users of python-acme?
--
You received this bug notification because you are a member
** Also affects: python-acme (Ubuntu)
Importance: Undecided
Status: New
** Also affects: python-letsencrypt-apache (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-acme (Ubuntu)
Status: New => Fix Released
** Changed in: python-letsencrypt-apache (Ubunt
** Also affects: python-letsencrypt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: python-letsencrypt (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: python-letsencrypt (Ubuntu)
Status: Confirmed => Fix Released
--
You received th
Those are good arguments, thanks for explaining!
--
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:
letsencrypt 0.4.1 contains numerous bugs fixed upstream
To manage notifications about t
I don't think so. We would want 0.10.0 to have at least several weeks of
field testing before stable distributions include it as an update, and
any regressions in that release would mean we do 0.10.x bugfix releases
that would stretch the timeline further.
--
You received this bug notification be
Will it be reasonable to wait for certbot 0.10.0 (due on Jan 4,
according to https://github.com/certbot/certbot/milestones), and go
ahead then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640978
Ti
.format(*x), sorry :)
--
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:
letsencrypt 0.4.1 contains numerous bugs fixed upstream
To manage notifications about this bug go to:
https://bugs
>>> import random
>>> x = ["RAOF", "rbasak"]
>>> random.shuffle(x)
>>> print "{0} should upload and {1} should review".format(x)
RAOF should upload and rbasak should review
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
I'm happy to do either.
--
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:
letsencrypt 0.4.1 contains numerous bugs fixed upstream
To manage notifications about this bug go to:
https://bu
The format sounds fine, thanks. We need one uploader and SRU team member
to review. I suggest we figure out who is doing what and both people
review before uploading to avoid confusion.
Since you mentioned that RAOF could sponsor, I subscribed him to the
bug. Since both of us are on the SRU team,
Hello everyone.
I'm not sure exactly what form you wanted the SRU in, but... I've
included a tarball of the source changes files and dsc's, signed, along
with the files included in them.
This upload has two changes from the version in sid. First, I tweaked
the versions in python-certbot to reduc
While you do this for v16.04, could you also publish certbot v0.9.x for
v16.10 at the same time? Or need a new ticket for that?
--
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:
letsencry
On Mon, Nov 28, 2016 at 09:22:28PM -, Peter Eckersley wrote:
> I think we've concluded that we'll add a note-upon-installation telling
> the sys admin that that's going to start happening, and point to where
> it can be turned off or tweaked.
I'm afraid that users who automatically update (mos
> Does this mean that users who currently won't get auto-renewed will
> start getting auto-renewed after this proposed update? If so, will that
> also include users who currently have expired (languishing) old
> certificates?
Yes. Each certificate (or more precisely, each lineage of certificates,
Hi Harlan,
Thank you for taking the time to help us out!
On Sun, Nov 20, 2016 at 02:47:14AM -, Harlan Lieberman-Berg wrote:
> The second largest change is the addition of an automatic renewal of any
> certificates, through both a cronjob installed into cron.d and a systemd
> timer.
Does this
@hlieberman My understanding is that the package name change shouldn't
affect any workflows, because "sudo apt-get install letsencrypt" will
still work and the "letsencrypt" command will still work. Anything I
might have missed?
--
You received this bug notification because you are a member of Ub
Hello everyone -- I'm (the primary, but not only) Debian maintainer of
the certbot suite of packages. pde asked me to weigh in here to help
answer some of rbasak's questions in a definitive manner.
Since the 0.4.1 release, there have been a handful of user-facing
changes, but only a few are workf
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python-letsencrypt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640978
* "a compatible but less buggy"
I should also note that most of our users have been running the certbot-
auto script which automatically upgrades them to the latest release of
Certbot as soon as it's public, so the odds of us getting bug reports
about workflow changes is fairly high.
--
You rece
On IRC, rbasak asked:
From an SRU review perspective, what I most want spelled out the exact
list of any behaviour changes you expect Xenial users to receive, and your
confirmation that you don't believe that there are any other changes.
Your word as upstream carries a great deal of weight on
Also fixes: Launchpad bug #1608214
--
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:
letsencrypt 0.4.1 contains numerous bugs fixed upstream
To manage notifications about this bug go to:
40 matches
Mail list logo
