[Python-modules-team] Processing of path.py_8.1.1-1_amd64.changes

path.py_8.1.1-1_amd64.changes uploaded successfully to localhost along with the files: path.py_8.1.1-1.dsc path.py_8.1.1.orig.tar.gz path.py_8.1.1-1.debian.tar.xz python-path_8.1.1-1_all.deb python3-path_8.1.1-1_all.deb Greetings, Your Debian queue daemon (running on host

[Python-modules-team] Bug#789670: (no subject)

I think the best we can do is add a Conflicts between the two packages. The contents of the conflicting directories are different. Personally, I think it's a bug that the two upstreams install these into the top-level namespace, but given the nature of the packages, I can see why they did it

[Python-modules-team] Bug#799076: Reproducing

Hi Chris, Do you have any suggestions on how to reproduce this? I'm somewhat surprised that this would fail on a different locale, and am having trouble reproducing it (by setting LC_ALL=fr_CH.UTF-8). How is the locale set exactly? Can you reproduce it? Cheers, Jelmer signature.asc

[Python-modules-team] path.py_8.1.1-1_amd64.changes is NEW

binary:python-path is NEW. binary:python3-path is NEW. source:path.py is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient.

[Python-modules-team] Bug#798010: Info received (Bug#798010 closed by Julian Taylor <jtaylor.deb...@googlemail.com> (Re: Bug#798010: Bug#798010: ipython3: malicious dynamic python3 interpreter lookup

P.S.: You can even get an ImportError running /usr/bin/ipython3, if the dynamic "env" lookup hits a user-space Python3 install whithout IPython: Traceback (most recent call last): File "/usr/bin/ipython3", line 4, in from IPython import start_ipython ImportError: No module named 'IPython'

[Python-modules-team] pysmbc_1.0.15.4-1_amd64.changes is NEW

binary:python3-smbc is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the

[Python-modules-team] Processing of pysmbc_1.0.15.4-1_amd64.changes

pysmbc_1.0.15.4-1_amd64.changes uploaded successfully to localhost along with the files: pysmbc_1.0.15.4-1.dsc pysmbc_1.0.15.4-1.debian.tar.xz python-smbc_1.0.15.4-1_amd64.deb python3-smbc_1.0.15.4-1_amd64.deb Greetings, Your Debian queue daemon (running on host

[Python-modules-team] www.packages.debian.org

Hi, my name's Amber, and I'm emailing you from an Sydney based Online Advertising Agency that specialises in both-SEO-(Google Rankings) and creating Custom Designed and Developed Websites. Our-SEO-and Web Services are legitimate, high quality, and most of all affordable. We also offer a

[Python-modules-team] Processing of python-keyring_5.4-2_source.changes

python-keyring_5.4-2_source.changes uploaded successfully to localhost along with the files: python-keyring_5.4-2.dsc python-keyring_5.4-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) ___

[Python-modules-team] Bug#798010: closed by Julian Taylor <jtaylor.deb...@googlemail.com> (Re: Bug#798010: Bug#798010: ipython3: malicious dynamic python3 interpreter lookup via "/usr/bin/env python3"

> Also the choice of env python in IPython is very deliberate. IPython > is a mostly a developer tool 99% of people I know that are developing scientific Python code are using IPython for interactive prototyping. And most of those people can not be considered Python developers but rather users.

[Python-modules-team] flask-wtf_0.12-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 07 Sep 2015 10:00:50 +0200 Source: flask-wtf Binary: python-flaskext.wtf python3-flaskext.wtf python-flaskext.wtf-doc Architecture: source all Version: 0.12-1 Distribution: unstable Urgency: medium Maintainer:

[Python-modules-team] drf-fsm-transitions_0.2.0-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 28 Apr 2015 17:35:01 +0200 Source: drf-fsm-transitions Binary: python-djangorestframework-fsm-transitions python3-djangorestframework-fsm-transitions Architecture: source all Version: 0.2.0-1 Distribution:

[Python-modules-team] Processed: found 789670 in 0.15.2-1, notfixed 794830 in 0.7-1+b1, notfixed 798635 in 1.0.3+dfsg-1+b1

Processing commands for cont...@bugs.debian.org: > found 789670 0.15.2-1 Bug #789670 [python-future,python-pies2overrides] python-future,python-pies2overrides: error when trying to install together There is no source info for the package 'python-pies2overrides' at version '0.15.2-1' with

[Python-modules-team] Bug#789670: Your mail

On Fri, 18 Sep 2015 15:37:35 -0400 Barry Warsaw wrote: > I think the best we can do is add a Conflicts between the two packages. The > contents of the conflicting directories are different. Personally, I think > it's a bug that the two upstreams install these into the

[Python-modules-team] python-gear is marked for autoremoval from testing

python-gear 0.5.8-2 is marked for autoremoval from testing on 2015-10-04 It (build-)depends on packages with these RC bugs: 796410: python-statsd: FTBFS: ImportError: No module named django.conf ___ Python-modules-team mailing list

[Python-modules-team] Bug#789670: Dropping python-pies2overrides

Since frosted is the only reverse dep of python-pies, and it can use python3-pies instead, how about just dropping python-pies/python-pies2overrides completely? ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org

[Python-modules-team] Jessie/Wheezy backports for python-subprocess32

Hey Daniel, python-subprocess32 will reach testing in the weekend, and we'd like to have it available in stable/oldstable. Do you want to handle the backports yourself or do you prefer me doing them? Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website:

[Python-modules-team] python-keyring_5.4-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 18 Sep 2015 13:14:50 +0300 Source: python-keyring Binary: python-keyring python3-keyring Architecture: source Version: 5.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team

[Python-modules-team] Bug#795108: marked as done (python-keyring: faulty capitalization in long description)

Your message dated Fri, 18 Sep 2015 10:37:27 + with message-id and subject line Bug#795108: fixed in python-keyring 5.4-2 has caused the Debian Bug report #795108, regarding python-keyring: faulty capitalization in long description to be marked as done.

[Python-modules-team] Fwd: Re: Jessie/Wheezy backports for python-subprocess32

Forwarded Message Subject: Re: Jessie/Wheezy backports for python-subprocess32 Date: Fri, 18 Sep 2015 13:13:49 +0200 From: Daniel Stender To: Sandro Tosi , mo...@debian.org On 18.09.2015 12:43, Sandro Tosi wrote: > Hey Daniel, >

[Python-modules-team] path.py_8.1.1-1_amd64.changes REJECTED

as requested by email Thorsten === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. ___ Python-modules-team mailing list

[Python-modules-team] Bug#764959: marked as done (please provide a python 3.x package)

Your message dated Fri, 18 Sep 2015 10:00:15 + with message-id and subject line Bug#782920: fixed in flask-wtf 0.12-1 has caused the Debian Bug report #782920, regarding please provide a python 3.x package to be marked as done. This means that you claim

[Python-modules-team] Bug#764959: marked as done (please provide a python 3.x package)

Your message dated Fri, 18 Sep 2015 10:00:15 + with message-id and subject line Bug#764959: fixed in flask-wtf 0.12-1 has caused the Debian Bug report #764959, regarding please provide a python 3.x package to be marked as done. This means that you claim

[Python-modules-team] Bug#782920: marked as done (Please provide a python3 module)

Your message dated Fri, 18 Sep 2015 10:00:15 + with message-id and subject line Bug#782920: fixed in flask-wtf 0.12-1 has caused the Debian Bug report #782920, regarding Please provide a python3 module to be marked as done. This means that you claim that

[Python-modules-team] Bug#782920: marked as done (Please provide a python3 module)

Your message dated Fri, 18 Sep 2015 10:00:15 + with message-id and subject line Bug#764959: fixed in flask-wtf 0.12-1 has caused the Debian Bug report #764959, regarding Please provide a python3 module to be marked as done. This means that you claim that

[Python-modules-team] pyro 1:3.14-1.2 MIGRATED to testing

FYI: The status of the pyro source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 1:3.14-1.2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you

[Python-modules-team] python-gear 0.5.8-2 MIGRATED to testing

FYI: The status of the python-gear source package in Debian's testing distribution has changed. Previous version: 0.5.5-2 Current version: 0.5.8-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will