python-dbusmock_0.11.3-1_amd64.changes uploaded successfully to localhost
along with the files:
python-dbusmock_0.11.3-1_all.deb
python3-dbusmock_0.11.3-1_all.deb
python-dbusmock_0.11.3-1.dsc
python-dbusmock_0.11.3.orig.tar.gz
python-dbusmock_0.11.3-1.debian.tar.xz
Greetings,
Yo
This was caused by a missing build dependency on python-requests. The
pypi-install script requires it. After installing the package in a
clean vagrant image:
root@10:~# pypi-install --help
Traceback (most recent call last):
File "/usr/bin/pypi-install", line 5, in
from stdeb.downloader impo
datanommer.commands 0.4.6-1 is marked for autoremoval from testing on 2014-10-18
It (build-)depends on packages with these RC bugs:
760482: txzmq: txzmq tests try to access the network during the build
___
Python-modules-team mailing list
Python-module
datanommer.models 0.6.4-1 is marked for autoremoval from testing on 2014-10-18
It (build-)depends on packages with these RC bugs:
760482: txzmq: txzmq tests try to access the network during the build
___
Python-modules-team mailing list
Python-modules-
moksha.hub 1.4.1-1 is marked for autoremoval from testing on 2014-10-18
It (build-)depends on packages with these RC bugs:
760482: txzmq: txzmq tests try to access the network during the build
___
Python-modules-team mailing list
Python-modules-team@li
datanommer.consumer 0.6.1-1 is marked for autoremoval from testing on 2014-10-18
It (build-)depends on packages with these RC bugs:
760482: txzmq: txzmq tests try to access the network during the build
___
Python-modules-team mailing list
Python-module
txzmq 0.7.2-1 is marked for autoremoval from testing on 2014-10-18
It is affected by these RC bugs:
760482: txzmq: txzmq tests try to access the network during the build
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
h
fedmsg 0.9.3-1 is marked for autoremoval from testing on 2014-10-18
It (build-)depends on packages with these RC bugs:
760482: txzmq: txzmq tests try to access the network during the build
___
Python-modules-team mailing list
Python-modules-team@lists.
pyke 1.1.1-4 is marked for autoremoval from testing on 2014-10-04
It is affected by these RC bugs:
759077: pyke: Please update to use wxpython3.0
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debia
Your message dated Thu, 18 Sep 2014 18:20:56 +
with message-id
and subject line Bug#759077: fixed in pyke 1.1.1-5
has caused the Debian Bug report #759077,
regarding pyke: Please update to use wxpython3.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 18 Sep 2014 18:39:17 +0200
Source: pyke
Binary: python-pyke python-pyke-doc
Architecture: source all
Version: 1.1.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Dani
pyke_1.1.1-5_amd64.changes uploaded successfully to localhost
along with the files:
python-pyke_1.1.1-5_all.deb
python-pyke-doc_1.1.1-5_all.deb
pyke_1.1.1-5.dsc
pyke_1.1.1-5.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
Hello Erwan,
On Monday 15 September 2014 07:56:52 Erwan David wrote:
> Since urllib3 does not do SNI, I cannot activate verification (the
> wrong certificate is retrieved)
urllib3 supports SNI, see here to configure it correctly:
http://urllib3.readthedocs.org/en/latest/contrib.html#module-urllib
tags 759070 + pending
thanks
On Thursday 18 September 2014 16:03:22 you wrote:
> I'm incorporating your patch right now, so a NMU should not be needed. :)
Done. I already asked for a RFS, so this should be fixed soon.
--
Daniele Tricoli 'Eriol'
http://mornie.org
_
FYI: The status of the sphinx source package
in Debian's testing distribution has changed.
Previous version: 1.2.2+dfsg-3
Current version: 1.2.3+dfsg-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you wil
I've noticed that the current python-pypdf package has migrated to
PyPDF2 (thus breaking all of its reverse dependencies in sid):
should the updated/converted rev-dep depend on python-pypdf >= 1.23-1
or python-pypdf2?
How is this going to be managed?
--
Elena ``of Valhalla''
__
Hello Olly,
many thanks for this patch!
On Thursday 18 September 2014 23:05:55 you wrote:
> I'm happy to NMU this change - just let me know if you'd like me to.
I'm incorporating your patch right now, so a NMU should not be needed. :)
Many thanks for working on this!
Kind regards,
--
Daniele
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 15 Aug 2014 16:07:09 +1200
Source: python3-openid
Binary: python3-openid
Architecture: source all
Version: 3.0.2+git20140828-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team
Changed-By
Control: tags 759077 + patch
Control: severity -1 serious
# Justification: blocks the on-going wxpython3.0 transition
I've rebuilt pyke with the attached patch and tested the "learn_pyke"
example, and it seems to work. And in fact, without creating a wx.App
object, it doesn't seem to work with wx
Processing control commands:
> tags 759077 + patch
Bug #759077 [src:pyke] pyke: Please update to use wxpython3.0
Added tag(s) patch.
> severity -1 serious
Bug #759077 [src:pyke] pyke: Please update to use wxpython3.0
Severity set to 'serious' from 'important'
--
759077: http://bugs.debian.org/cg
20 matches
Mail list logo
