[Python-modules-team] Bug#806591: marked as done (qscintilla2: FTBFS on sparc64 due to mismatched symbols files)

Your message dated Thu, 30 Jun 2016 05:48:47 + with message-id and subject line Bug#806591: fixed in qscintilla2 2.9.2+dfsg-3 has caused the Debian Bug report #806591, regarding qscintilla2: FTBFS on sparc64 due to mismatched symbols files to be marked as

[Python-modules-team] Processing of qscintilla2_2.9.2+dfsg-3_source.changes

qscintilla2_2.9.2+dfsg-3_source.changes uploaded successfully to localhost along with the files: qscintilla2_2.9.2+dfsg-3.dsc qscintilla2_2.9.2+dfsg-3.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)

[Python-modules-team] qscintilla2_2.9.2+dfsg-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 30 Jun 2016 00:59:24 -0400 Source: qscintilla2 Binary: libqscintilla2-12v5 libqscintilla2-12v5-dbg libqt5scintilla2-12v5 libqt5scintilla2-12v5-dbg libqscintilla2-l10n libqt5scintilla2-l10n

[Python-modules-team] django-uwsgi is marked for autoremoval from testing

django-uwsgi 0.1.3-2 is marked for autoremoval from testing on 2016-07-29 It (build-)depends on packages with these RC bugs: 811606: mongodb: FTBFS with GCC 6: multiple errors ___ Python-modules-team mailing list

[Python-modules-team] guzzle-sphinx-theme is marked for autoremoval from testing

guzzle-sphinx-theme 0.7.10-1 is marked for autoremoval from testing on 2016-07-14 It is affected by these RC bugs: 823508: python-guzzle-sphinx-theme: Useless in Debian ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org

[Python-modules-team] Bug#829053: python-rgain: --jobs doesn't work

Package: python-rgain Version: 1.3.3-1 Severity: normal Hi... Whether one ommits --jobs (which should it cause to use the number of cores according to the docs) or sets it to >1 it doesn't seem to concurrently use more than one CPU. Cheers, Chris. -- System Information: Debian Release:

[Python-modules-team] python-nacl_1.0.1-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 30 Jun 2016 02:00:16 +0200 Source: python-nacl Binary: python-nacl python3-nacl python-nacl-doc Architecture: source Version: 1.0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team

[Python-modules-team] Processing of python-nacl_1.0.1-2_source.changes

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

[Python-modules-team] Processed: tagging 828112, tagging 828110, tagging 828119, tagging 827832, tagging 827834, tagging 818197 ...

Processing commands for cont...@bugs.debian.org: > tags 828112 + sid stretch Bug #828112 {Done: Dirk Eddelbuettel } [src:fregression] fregression: FTBFS: dh_clean: Please specify the compatibility level in debian/compat Added tag(s) sid and stretch. > tags 828110 + sid stretch

[Python-modules-team] Processed: Re: FTBFS: buffio.h: No such file or directory

Processing control commands: > severity -1 normal Bug #828880 [src:elementtidy] elementtidy: FTBFS: elementtidy.c:41:20: fatal error: buffio.h: No such file or directory Severity set to 'normal' from 'serious' -- 828880: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828880 Debian Bug

[Python-modules-team] Processed: Re: FTBFS: buffio.h: No such file or directory

Processing control commands: > severity -1 normal Bug #828880 [src:elementtidy] elementtidy: FTBFS: elementtidy.c:41:20: fatal error: buffio.h: No such file or directory Ignoring request to change severity of Bug 828880 to the same value. -- 828880:

[Python-modules-team] Bug#828880: FTBFS: buffio.h: No such file or directory

control: severity -1 normal I'm lowering the severity since these packages build now that tidy-html5 has a compatible header in Debian. I'm not closing the bug since maybe these packages should be adjusted to the new header location. I don't think it's clear yet exactly what these packages

[Python-modules-team] pythondialog 3.4.0-1 MIGRATED to testing

FYI: The status of the pythondialog source package in Debian's testing distribution has changed. Previous version: 3.3.0-1 Current version: 3.4.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] Bug#828902: utidylib: please update for new tidy-html5

Hi Michal, My understand is that the API is not meant to be changed in libtidy5 relative to the earlier versions of libtidy. Thanks for creating the upstream pull request. Cheers! Daniel ___ Python-modules-team mailing list

[Python-modules-team] Bug#828902: utidylib: please update for new tidy-html5

Hi Dne 29.6.2016 v 15:40 Gianfranco Costamagna napsal(a): > control: tags -1 -patch > >> No, it doesn't, it segfaults, so the API has probably changed somewhere. >> Is there upstream documentation on changes between original libtidy and >> this fork? > > > I'm ccing the maintainer, I have no

[Python-modules-team] python-neovim-gui_0.1.3-1_source.changes ACCEPTED into experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 29 Jun 2016 15:00:42 +0200 Source: python-neovim-gui Binary: python3-neovim-gui Architecture: source Version: 0.1.3-1 Distribution: experimental Urgency: medium Maintainer: Debian Python Modules Team

[Python-modules-team] Bug#828902: utidylib: please update for new tidy-html5

control: tags -1 -patch >No, it doesn't, it segfaults, so the API has probably changed somewhere. >Is there upstream documentation on changes between original libtidy and >this fork? I'm ccing the maintainer, I have no knowledge on this matter. cheers, G.

[Python-modules-team] Processing of python-neovim-gui_0.1.3-1_source.changes

python-neovim-gui_0.1.3-1_source.changes uploaded successfully to localhost along with the files: python-neovim-gui_0.1.3-1.dsc python-neovim-gui_0.1.3.orig.tar.gz python-neovim-gui_0.1.3-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)

[Python-modules-team] Processed: Re: Bug#828902: utidylib: please update for new tidy-html5

Processing control commands: > tags -1 -patch Bug #828902 [src:utidylib] utidylib: please update for new tidy-html5 Ignoring request to alter tags of bug #828902 to the same tags previously set -- 828902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828902 Debian Bug Tracking System Contact

[Python-modules-team] Bug#828902: utidylib: please update for new tidy-html5

Hi Dne 28.6.2016 v 22:25 Gianfranco Costamagna napsal(a): > please update the runtime dependency to the new tidy lib, I hope the binding > will still work No, it doesn't, it segfaults, so the API has probably changed somewhere. Is there upstream documentation on changes between original libtidy

[Python-modules-team] Processed: tagging 828902

Processing commands for cont...@bugs.debian.org: > tags 828902 - patch Bug #828902 [src:utidylib] utidylib: please update for new tidy-html5 Removed tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 828902:

[Python-modules-team] Bug#821888: marked as done (proselint: --demo option is broken)

Your message dated Wed, 29 Jun 2016 13:25:43 + with message-id and subject line Bug#821888: fixed in python3-proselint 0.5.3-3 has caused the Debian Bug report #821888, regarding proselint: --demo option is broken to be marked as done. This means that you

[Python-modules-team] python3-proselint_0.5.3-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 29 Jun 2016 14:10:00 +0200 Source: python3-proselint Binary: python3-proselint Architecture: source Version: 0.5.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team

[Python-modules-team] Processed: raise severity of GCC 6 ftbfs issues in preparation for GCC defaults change

Processing commands for cont...@bugs.debian.org: > severity 816569 serious Bug #816569 [mrs] mrs: FTBFS with GCC 6: was not declared in this scope Bug #822466 [mrs] mrs: FTBFS: error: 'log' was not declared in this scope Ignoring request to change severity of Bug 816569 to the same value.

[Python-modules-team] Processing of python3-proselint_0.5.3-3_source.changes

python3-proselint_0.5.3-3_source.changes uploaded successfully to localhost along with the files: python3-proselint_0.5.3-3.dsc python3-proselint_0.5.3-3.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)

[Python-modules-team] Bug#821888: proselint: --demo option is broken

A little debugging found the culprit, you cannot open read-only files with proselint, even if proselint doesn't need to (nor should) edit the files. I will make a patch for this, and I have reported it upstream to get it fixed [1]. Cheers, [1]: https://github.com/amperser/proselint/issues/502

[Python-modules-team] Processed: tagging 806591

Processing commands for cont...@bugs.debian.org: > tags 806591 + pending Bug #806591 [src:qscintilla2] qscintilla2: FTBFS on sparc64 due to mismatched symbols files Ignoring request to alter tags of bug #806591 to the same tags previously set > thanks Stopping processing here. Please contact me

[Python-modules-team] pep8-naming_0.4.1-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 29 Jun 2016 12:31:00 +0200 Source: pep8-naming Binary: python-pep8-naming python3-pep8-naming Architecture: source all Version: 0.4.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team

[Python-modules-team] nose_1.3.7-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 29 Jun 2016 13:26:34 +0300 Source: nose Binary: python-nose-doc python-nose python3-nose Architecture: source Version: 1.3.7-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team

[Python-modules-team] Processing of nose_1.3.7-2_source.changes

nose_1.3.7-2_source.changes uploaded successfully to localhost along with the files: nose_1.3.7-2.dsc nose_1.3.7-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ Python-modules-team mailing list

[Python-modules-team] Processing of pep8-naming_0.4.1-1_amd64.changes

pep8-naming_0.4.1-1_amd64.changes uploaded successfully to localhost along with the files: pep8-naming_0.4.1-1.dsc pep8-naming_0.4.1.orig.tar.xz pep8-naming_0.4.1-1.debian.tar.xz python-pep8-naming_0.4.1-1_all.deb python3-pep8-naming_0.4.1-1_all.deb Greetings, Your Debian queue

[Python-modules-team] Bug#806591: qscintilla2: FTBFS on sparc64 due to mismatched symbols files

Hi Scott! On 06/29/2016 06:59 AM, Scott Kitterman wrote: > I just looked at fixing this, but I see that the build log for the current > version, qscintilla2_2.9.2+dfsg-2, is not on buildd.d.o. This can happen if the buildd itself has trouble sending email. I have now rescheduled the

[Python-modules-team] Bug#828942: new version available (6.0.2)

Source: cherrypy3 Version: 3.5.0-2 Severity: wishlist The current version described by upstream cherrypy.org as "stable" is v6.0.2, commit ca684b38. Is there a good reason for Debian to only ship 3.5.0 ? There are a lot of changes: $ git clone --bare https://github.com/cherrypy/cherrypy