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

doctrine-sphinx-theme 0~20130227-1 is marked for autoremoval from testing on 2016-05-14 It is affected by these RC bugs: 821123: doctrine-sphinx-theme: Useless in Debian ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org

[Python-modules-team] Processed: Bug#822224 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 84 pending Bug #84 [src:django-tables] django-tables: Please update build-dependency on django and add a clean rule Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 84:

[Python-modules-team] Bug#822224: Bug#822224: Further changes

Neil Williams writes: > python-django and python-django-tables2 from jessie work but if either > one is pulled in from jessie-backports without the other, restarting > apache2 causes a HTTP500. I am not sure I see how adding the Breaks header helps resolve this? -- Brian

[Python-modules-team] django-reversion_1.10.2-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 22 Apr 2016 22:36:16 +0200 Source: django-reversion Binary: python-django-reversion python3-django-reversion python-django-reversion-doc Architecture: source all Version: 1.10.2-1 Distribution: unstable Urgency:

[Python-modules-team] Processing of django-reversion_1.10.2-1_amd64.changes

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

[Python-modules-team] pyusb 1.0.0~rc1-1 MIGRATED to testing

FYI: The status of the pyusb source package in Debian's testing distribution has changed. Previous version: 1.0.0~b2-2 Current version: 1.0.0~rc1-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#822224: Bug#822224: Further changes

On Fri, 22 Apr 2016 20:28:28 +1000 Brian May wrote: > Neil Williams writes: > > > i.e. django-tables 1.1.6 reveals a "bug" in django 1.7 so django > > needs to be updated to 1.8 before django-tables 1.1.6 can be > > upgraded/installed. > > Sorry, not

[Python-modules-team] Bug#822224: Bug#822224: Further changes

Neil Williams writes: > i.e. django-tables 1.1.6 reveals a "bug" in django 1.7 so django needs > to be updated to 1.8 before django-tables 1.1.6 can be > upgraded/installed. Sorry, not sure I understand the need for the Breaks. What happens if you upgrade django-tables and

[Python-modules-team] Bug#789911: marked as done (python-gear: Obsolete ‘daemon.pidlockfile’ API migrated to ‘python-lockfile’ library)

Your message dated Fri, 22 Apr 2016 11:52:38 +0200 with message-id <20160422095238.gb2...@betterave.cristau.org> and subject line Re: Bug#789911: python-gear: Obsolete ‘daemon.pidlockfile’ API migrated to ‘python-lockfile’ library has caused the Debian Bug report #789911, regarding python-gear:

[Python-modules-team] django-haystack_2.4.1-1~bpo8+1_amd64.changes is NEW

binary:python-django-haystack is NEW. binary:python-django-haystack-doc is NEW. binary:python3-django-haystack is NEW. source:django-haystack 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

[Python-modules-team] Processing of python-fudge_1.1.0-1~bpo8+1_amd64.changes

python-fudge_1.1.0-1~bpo8+1_amd64.changes uploaded successfully to localhost along with the files: python-fudge_1.1.0-1~bpo8+1.dsc python-fudge_1.1.0-1~bpo8+1.debian.tar.xz python-fudge_1.1.0-1~bpo8+1_all.deb python-fudge-doc_1.1.0-1~bpo8+1_all.deb python3-fudge_1.1.0-1~bpo8+1_all.deb

[Python-modules-team] Processing of django-haystack_2.4.1-1~bpo8+1_amd64.changes

django-haystack_2.4.1-1~bpo8+1_amd64.changes uploaded successfully to localhost along with the files: django-haystack_2.4.1-1~bpo8+1.dsc django-haystack_2.4.1-1~bpo8+1.debian.tar.xz python-django-haystack_2.4.1-1~bpo8+1_all.deb python3-django-haystack_2.4.1-1~bpo8+1_all.deb

[Python-modules-team] Bug#822224: Further changes

Actually, there would likely be a need for further changes as the django dependency of the binary packages is specified explicitly in debian/control so also needs an update to 1.8. I'm thinking that the changes need to include: Depends: ${misc:Depends}, ${python:Depends}, python-django (>= 1.8)

[Python-modules-team] Bug#822224: django-tables: Please update build-dependency on django and add a clean rule

Source: django-tables Version: 1.1.6 Severity: minor In order to prepare a backport of django-tables, I had to make these two changes to the current packaging of django-tables: Update build-depends on python-django and python3-django to 1.8 as the unit tests in django-tables 1.1.6 fail with the