[Python-modules-team] python-rsa_4.0-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 04 Oct 2018 14:19:18 +0900 Source: python-rsa Binary: python-rsa python3-rsa Architecture: source all Version: 4.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By:

[Python-modules-team] Processing of python-rsa_4.0-1_amd64.changes

python-rsa_4.0-1_amd64.changes uploaded successfully to localhost along with the files: python-rsa_4.0-1.dsc python-rsa_4.0.orig.tar.gz python-rsa_4.0-1.debian.tar.xz python-rsa_4.0-1_all.deb python-rsa_4.0-1_amd64.buildinfo python3-rsa_4.0-1_all.deb Greetings, Your Debian

[Python-modules-team] pychromecast 2.3.0-1 MIGRATED to testing

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

[Python-modules-team] peewee 3.7.0+dfsg-1 MIGRATED to testing

FYI: The status of the peewee source package in Debian's testing distribution has changed. Previous version: 2.10.2+dfsg-2 Current version: 3.7.0+dfsg-1 -- 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-mongoengine is marked for autoremoval from testing

python-mongoengine 0.10.6-1 is marked for autoremoval from testing on 2018-10-29 It is affected by these RC bugs: 906402: python-mongoengine: FTBFS in buster/sid (ModuleNotFoundError: No module named 'document') ___ Python-modules-team mailing list

[Python-modules-team] mwic 0.7.6-1 MIGRATED to testing

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

[Python-modules-team] python-vertica 0.8.0-1 MIGRATED to testing

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

[Python-modules-team] jaraco.itertools REMOVED from testing

FYI: The status of the jaraco.itertools source package in Debian's testing distribution has changed. Previous version: 2.0.1-3 Current version: (not in testing) Hint: Bug #907873: python3-jaraco.itertools,python-jaraco.itertools:

[Python-modules-team] cloudpickle 0.5.6-1 MIGRATED to testing

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

[Python-modules-team] python-changelog 0.4.1-2 MIGRATED to testing

FYI: The status of the python-changelog source package in Debian's testing distribution has changed. Previous version: 0.4.1-1 Current version: 0.4.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] Bug#909971: marked as done (remove unneeded dependency on backports.ssl-match-hostname)

Your message dated Thu, 04 Oct 2018 01:34:53 + with message-id and subject line Bug#909971: fixed in libcloud 2.3.0-3 has caused the Debian Bug report #909971, regarding remove unneeded dependency on backports.ssl-match-hostname to be marked as done. This means that you claim that the

[Python-modules-team] libcloud_2.3.0-3_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 03 Oct 2018 21:14:23 -0400 Source: libcloud Binary: python-libcloud python3-libcloud Architecture: source all Version: 2.3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team

[Python-modules-team] Processing of libcloud_2.3.0-3_amd64.changes

libcloud_2.3.0-3_amd64.changes uploaded successfully to localhost along with the files: libcloud_2.3.0-3.dsc libcloud_2.3.0-3.debian.tar.xz libcloud_2.3.0-3_amd64.buildinfo python-libcloud_2.3.0-3_all.deb python3-libcloud_2.3.0-3_all.deb Greetings, Your Debian queue daemon

[Python-modules-team] Processed: Bug #909971 in libcloud marked as pending

Processing control commands: > tag -1 pending Bug #909971 [libcloud] remove unneeded dependency on backports.ssl-match-hostname Added tag(s) pending. -- 909971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

[Python-modules-team] Bug#910240: python3-django: GeoDjango incorrectly initialize spatialite (Error: /usr/lib/x86_64-linux-gnu/mod_spatialite.so: undefined symbol: sqlite3_spatialite_init)

On Wed, 03 Oct 2018 20:42:42 +0200 Petter Reinholdtsen wrote: > According to sebastic on #debian-gis, the way to load spatialite changed > in version 4.2, and now the correct way to load the library is to use > "SELECT load_extension('mod_spatialite');", while the GeoDjango database > backend try

[Python-modules-team] Bug#910240: python3-django: GeoDjango incorrectly initialize spatialite (Error: /usr/lib/x86_64-linux-gnu/mod_spatialite.so: undefined symbol: sqlite3_spatialite_init)

Package: python3-django Version: 1:1.10.7-2 Today I decided to test GeoDjango, and set up a simple project using spatialite. But loading the spatialite database backend would fail like this: Traceback (most recent call last): File

[Python-modules-team] Processed: add ftbfs tag

Processing commands for cont...@bugs.debian.org: > tags 806100 + ftbfs Bug #806100 [src:pyviennacl] pyviennacl: FTBFS when built with dpkg-buildpackage -A (No such file or directory) Added tag(s) ftbfs. > tags 806127 + ftbfs Bug #806127 [src:zope2.13] zope2.13: FTBFS when built with

[Python-modules-team] Processed (with 2 errors): user debian...@lists.debian.org, usertagging 910008, reassign 910008 to libghc-mtl-dev ...

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 910008 piuparts There were no usertags set. Usertags are now: piuparts. > reassign 910008 libghc-mtl-dev 2.2.2-2 Bug #910008

[Python-modules-team] Bug#869896: backports.ssl-match-hostname should be removed for buster

Hi, On 10/02/2018 09:22 PM, Felipe Sateler wrote: Hi Matthias, Ivo, On Sun, 30 Sep 2018 22:59:26 +0200 Ivo De Decker > wrote: > clone 869896 -1 > retitle -1 remove unneeded dependency on backports.ssl-match-hostname > block 869896 by -1 > clone -1 -2 -3 -4 -5 >

[Python-modules-team] Processing of django-auto-one-to-one_3.1.1-1_amd64.changes

django-auto-one-to-one_3.1.1-1_amd64.changes uploaded successfully to localhost along with the files: django-auto-one-to-one_3.1.1-1.dsc django-auto-one-to-one_3.1.1.orig.tar.gz django-auto-one-to-one_3.1.1-1.debian.tar.xz django-auto-one-to-one_3.1.1-1_amd64.buildinfo

[Python-modules-team] Processed: Reassign to src:python-virtualenv, downgrading severity

Processing commands for cont...@bugs.debian.org: > reassign 884352 src:python-virtualenv Bug #884352 [virtualenvwrapper] virtualenvwrapper: Python interpreter inside virtualenv breaks after system python upgrade Bug reassigned from package 'virtualenvwrapper' to 'src:python-virtualenv'. No