[Letsencrypt-devel] Bug#825619: Bug#825619: certbot: missing dependency on a recent version of python-setuptools

[Harlan Lieberman-Berg]

block 825619 by 821030
thanks

Lukas Pirl  writes:
> I guess making an adequately recent version of python-setuptools a
> requirement of certbot (probably transitively) would fix this.

Hi Lukas,

Yup, makes sense.  I'm temporarily putting the version restriction in
the next release of python-acme to stop the bleeding, but will remove it
as soon as this bug is fixed in python-cryptography.

Sincerely,
-- 
Harlan Lieberman-Berg
~hlieberman

___
Letsencrypt-devel mailing list
Letsencrypt-devel@lists.alioth.debian.org
https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel

[Letsencrypt-devel] Processed: Re: Bug#825619: certbot: missing dependency on a recent version of python-setuptools

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 825619 by 821030
Bug #825619 [certbot] certbot: missing dependency on a recent version of 
python-setuptools
825619 was not blocked by any bugs.
825619 was not blocking any bugs.
Added blocking bug(s) of 825619: 821030
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
825619: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Letsencrypt-devel mailing list
Letsencrypt-devel@lists.alioth.debian.org
https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel

Re: [Letsencrypt-devel] python-psutil backport

[Sandro Tosi]

Hey Harlan,

On Wed, Jun 1, 2016 at 3:05 AM, Harlan Lieberman-Berg
 wrote:
> Hi Sandro,
>
> Wanted to reach out to you about python-psutil.  Right now, there's an
> extant bug in the version that's in jessie which is causing some
> problems with certbot (aka letsencrypt).
>
> It seems the bug was fixed in 2.2.1, exactly one minor point later than
> what we have in jessie.
>
> Do you think this is something that we might be able to get fixed
> through p-u?

it is unlikely the release team would approve a new upstream release
(no matter how minor that is) or even a patch for software outside of
jessie (as certbot is only in jessie bpo)

> Also, how would you feel about a backport of python-psutil?  I'm happy
> to put that work forth to get 4.1 into jessie-backports.

i think this is a better approach, as most/all the other modules for
certbot are in bpo anyway; if you want you can go ahead and upload
psutil to jessie-backports, or I can do that, but will take me few
days to get to it

Cheers,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Letsencrypt-devel mailing list
Letsencrypt-devel@lists.alioth.debian.org
https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel

[Letsencrypt-devel] Bug#825750: closed by Harlan Lieberman-Berg <hlieber...@debian.org> (Certbot in backports)

[vincent]

Debian Bug Tracking System:
> This is an automatic notification regarding your Bug report
> which was filed against the src:python-acme package:
> 
> #825750: letsencrypt: missing dependency
> 
> It has been closed by Harlan Lieberman-Berg .


Unfortunately that doesn't seems to be fixed yet. At least for
jessie-backports


% sudo apt-get -t jessie-backports install python-letsencrypt
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python-letsencrypt : Depends: python-acme (>= 0.5.0) but it is not
going to be installed
E: Unable to correct problems, you have held broken packages.


python-acme is already installed:

 % sudo  dpkg -s python-acme
Package: python-acme
Status: install ok installed
Priority: extra
Section: python
Installed-Size: 307
Maintainer: Debian Let's Encrypt 
Architecture: all
Version: 0.6.0-1~bpo8+1
Depends: ca-certificates, python-openssl (>= 0.15), python-cryptography
(>= 0.8), python-mock, python-ndg-httpsclient, python-pkg-resources,
python-pyasn1, python-requests, python-rfc3339, python-six, python-tz,
python:any (<< 2.8), python:any (>= 2.7.5-5~)
Breaks: python-certbot (<< 0.6.0), python-letsencrypt (<< 0.6.0)
Description: ACME protocol library for Python 2
 This is a library used by the Let's Encrypt client for the ACME
 (Automated Certificate Management Environment).  The ACME protocol is
 designed as part of the Let's Encrypt project, to make it possible to
 setup an HTTPS server and have it automatically obtain a
 browser-trusted certificate, without any human intervention.  This
 library implements the protocol used for proving the control of a
 domain.  This library is Python 2.
Homepage: https://letsencrypt.org/




however the version installed from jessie-backports is now:
Version: 0.6.0-1~bpo8+1

although the version required in python-letsencrypt is python-acme (>=
0.5.0)

 % sudo apt-cache -t jessie-backports show python-letsencrypt
Package: python-letsencrypt
Version: 0.5.0-1~bpo8+1
Installed-Size: 734
Maintainer: Debian Let's Encrypt 
Architecture: all
Depends: python-acme (>= 0.5.0), python-configargparse,
python-configobj, python-cryptography (>= 0.7), python-dialog,
python-mock, python-openssl, python-parsedatetime, python-pkg-resources,
python-psutil, python-rfc3339, python-six, python-tz,
python-zope.component, python-zope.interface, python:any (<< 2.8),
python:any (>= 2.7.5-5~)
Recommends: letsencrypt


Maybe this syntax (>= 0.5.0) doesn't recognize 0.6.0-1~bpo8+1 as an
upgraded version?


thanks,

___
Letsencrypt-devel mailing list
Letsencrypt-devel@lists.alioth.debian.org
https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel