Russ Allbery writes:
> Paul Wise writes:
>> I note that letsencrypt 0.4.1-1 (before the rename to certbot) is
>> available in Ubuntu xenial, which is scheduled for 5 years of support,
>> terminating in 2021.
> It's in universe, so it's not really included in that five-year promise.
We're also in
Paul Wise writes:
> On Tue, Nov 22, 2016 at 9:40 AM, Peter Eckersley wrote:
>> currently working with an ACME backwards compatibilty window of 6-12
>> months, but probably not longer than that.
> I note that letsencrypt 0.4.1-1 (before the rename to certbot) is
> available in Ubuntu xenial, whic
Package: wnpp
Severity: wishlist
Owner: "ChangZhuo Chen (陳昌倬)"
* Package name: tpm
Version : v3.0.0
Upstream Author : 2014 Bruno Sutic
* URL : https://github.com/tmux-plugins/tpm
* License : Expat
Programming Lang: bash
Description : tmux plugin manager
On Tue, Nov 22, 2016 at 9:40 AM, Peter Eckersley wrote:
> currently working with an ACME backwards compatibilty window of 6-12 months,
> but probably not longer than that.
I note that letsencrypt 0.4.1-1 (before the rename to certbot) is
available in Ubuntu xenial, which is scheduled for 5 years
> "HL" == Harlan Lieberman-Berg writes:
HL> The fix we put in place took about ten days to hit. It shouldn't have
HL> been broken longer than that; we didn't close the bug immediately,
HL> because we wanted the dependency to fix their versioning.
I do recall a long wait before an upload was
On November 25, 2016 4:05:30 PM EST, James Cloos wrote:
>It may have been; in any case it took *weeks* for the bug I saw to get
>fixed. And it doesn't matter where the bug was, it still made it
>impossible to apt-get install the certbot package. Which still defines
>the certbot in jessie-backpor
> "HL" == Harlan Lieberman-Berg writes:
HL> In fact, letsencrypt was never in jessie either. Both certbot and
HL> letsencrypt have only ever been in stable-bpo, stretch, and sid.
Ok. That must have been before I was forced to switch my openvz systems
from sid to jessie-backports. (The gli
James Cloos writes:
> HL> Certbot has never been in jessie, so I imagine it wouldn't have been
> usable.
>
> Certbot, letsencrypt, python-acme, et cetera; the package name doesn't
> matter for this purpose.
In fact, letsencrypt was never in jessie either. Both certbot and
letsencrypt have only e
> "HL" == Harlan Lieberman-Berg writes:
HL> Certbot has never been in jessie, so I imagine it wouldn't have been
usable.
Certbot, letsencrypt, python-acme, et cetera; the package name doesn't
matter for this purpose.
HL> I'm also haven't gotten any tickets about it being unusable. Can you
H
On Fri, Nov 25, 2016 at 10:52:55PM +0900, Hideki Yamane wrote:
> Almost yes, but I thought it sits before autobuilders as below.
> i.e. [upload]→[lintian autoreject]→[piuparts autoreject]→[autobuilders]
we want people to upload source only packages and piuparts and lintian
work on binary packag
On 11/25/2016 12:45 PM, Christian Seiler wrote:
> On 11/25/2016 10:34 AM, Thijs Kinkhorst wrote:
>> On Thu, November 24, 2016 22:28, Harlan Lieberman-Berg wrote:
>>> On November 24, 2016 11:59:46 AM EST, James Cloos
>>> wrote:
The jessie and jessie-backports releases of certbot have not, in
>
On viernes, 25 de noviembre de 2016 10:38:00 ART Stepan Golosunov wrote:
> 25.11.2016 в 02:07:11 +0100 Jan Niehusmann написал:
> > On Fri, Nov 25, 2016 at 01:56:19AM +0400, Stepan Golosunov wrote:
> > > qsslsocket_openssl_symbols.cpp also tries to load any libssl.* it can
> > > find (in directories
Hi,
On Wed, 23 Nov 2016 22:04:15 +
Johannes Schauer wrote:
> by "repository" you mean the unstable suite?
Yes, I mean it is unstable but it is also better to support testing
migration as Niels said.
> So you essentially want packages to pass piuparts before they are moved from
> incoming
On Fr, Nov 25, 2016 at 10:34:32 +0100, Thijs Kinkhorst wrote:
FWIW certbot from jessie-backports has been working fine for me in
several contexts.
Yes, here as well.
The only problem was the renaming from letsencrypt to certbot.
Many greetings,
Stephan
--
| Stephan Seitz E-M
On 11/22/2016 02:40 AM, Peter Eckersley wrote:
> 1. Leave Certbot out of the Debian Stretch release, and rely on
> backports as the recommended way to run Certbot on Debian. That's what we
> currently do with Jessie:
Note that per backports rules, $RELEASE_N-backports must track
$RELEASE_N_PLUS_1,
On 11/25/2016 10:34 AM, Thijs Kinkhorst wrote:
> On Thu, November 24, 2016 22:28, Harlan Lieberman-Berg wrote:
>> On November 24, 2016 11:59:46 AM EST, James Cloos
>> wrote:
>>> The jessie and jessie-backports releases of certbot have not, in
>>> general, been usable. There have been usable windo
On Thu, November 24, 2016 22:28, Harlan Lieberman-Berg wrote:
> On November 24, 2016 11:59:46 AM EST, James Cloos
> wrote:
>>The jessie and jessie-backports releases of certbot have not, in
>>general, been usable. There have been usable windows, but it has not
>>been continuous.
>
> Certbot has n
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-os-locale
Version : 2.0.0
Upstream Author : Sindre Sorhus
(sindresorhus.com)
* URL : https://github.com/sindresorhus/os-locale#readme
* License
18 matches
Mail list logo
