[Python-modules-team] Processing of sphinx_1.3.3-1_source.changes

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

[Python-modules-team] sphinx_1.3.3-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 03 Dec 2015 18:35:09 +0300 Source: sphinx Binary: python-sphinx python3-sphinx sphinx-common sphinx-doc libjs-sphinxdoc Architecture: source Version: 1.3.3-1 Distribution: unstable Urgency: medium Maintainer:

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

python-restless 2.0.1-3 is marked for autoremoval from testing on 2015-12-25 It is affected by these RC bugs: 806335: python-restless: FTBFS: AttributeError: 'NoneType' object has no attribute 'set_close_callback' ___ Python-modules-team mailing list

[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] Bug#806961: Missing python3-all autopkgtest dependency

Package: guessit Version: 0.10.3-1 Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch xenial Hello, guessit's tests [1] started failing since python3.5 got added as a supported python3 version: | adt-run [17:26:41]: test unittests3: [--- | +

[Python-modules-team] cssutils 1.0-4 MIGRATED to testing

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

[Python-modules-team] [bts-link] source package src:django-openid-auth

# # bts-link upstream status pull for source package src:django-openid-auth # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #806352 (http://bugs.debian.org/806352) # Bug title:

Re: [Python-modules-team] Django 1.9

Quoting Raphael Hertzog : What do you think? Of course we should have both django-LTS and django-LATEST in Debian :~) But that would be much more work for both maintainers and security team, so it's probably not a serious option. I wonder which packages *in Debian* depend

[Python-modules-team] Processing of sphinx_1.3.3-1_source.changes

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

[Python-modules-team] sphinx_1.3.3-1_source.changes REJECTED

sphinx_1.3.3-1.dsc: Refers to non-existing file 'sphinx_1.3.3.orig.tar.gz' Perhaps you need to include the file in your upload? === 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.

Re: [Python-modules-team] Django 1.9

Hi, > > I'm tempted to package only LTS releases in Debian unstable As as large "end-developer" of Django projects and Django components, the drawbacks of not having the latest version as possible in the stable release (and thus being uploaded to unstable) would personally far outweigh the

[Python-modules-team] Processing of python-django_1.9-1_amd64.changes

python-django_1.9-1_amd64.changes uploaded successfully to localhost along with the files: python-django_1.9-1.dsc python-django_1.9.orig.tar.gz python-django_1.9-1.debian.tar.xz python-django-common_1.9-1_all.deb python-django-doc_1.9-1_all.deb python-django_1.9-1_all.deb

[Python-modules-team] python-django_1.9-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 03 Dec 2015 16:48:30 +0200 Source: python-django Binary: python-django python3-django python-django-common python-django-doc Architecture: source all Version: 1.9-1 Distribution: unstable Urgency: medium

Re: [Python-modules-team] Django 1.9

Hi, On Thu, 03 Dec 2015, Chris Lamb wrote: > As as large "end-developer" of Django projects and Django components, > the drawbacks of not having the latest version as possible in the stable > release (and thus being uploaded to unstable) would personally far > outweigh the benefits of sticking

Re: [Python-modules-team] Django 1.9

James Bennett writes: > But the gist of it is that, after Django 1.11 (LTS), we'll jump to 2.0, > and the process will be: > > * 2.0 is followed by 2.1, then 2.2, 3.0, 3.1, 3.2, 4.0, etc. > > * Every X.2 release is LTS, targeting 3 years of support. We're > exploring ideas for

Re: [Python-modules-team] Django 1.9

I see that Django 1.9 is now in unstable... Raphael Hertzog writes: > For this to be viable, we would just have to ensure that all Django > applications are free of Django warning before any Debian release. Regardless of what we decide, I would really like to do this one.

[Python-modules-team] - 12 DAYS of DEALS: @ AVON

Avon for Women, Men & the Kids 12 Days of DEALS Celebrate the Holiday with 12 days of Amazing Deals. --- Our gifts to you, starting "TODAY" December 2nd. through December 13th. 

Re: [Python-modules-team] Django 1.9

On Thu, 03 Dec 2015 17:33:39 +0100 "W. Martin Borgert" wrote: > Quoting Raphael Hertzog : > > What do you think? > > Of course we should have both django-LTS and django-LATEST in > Debian :~) But that would be much more work for both maintainers and >