Re: [Python-modules-team] About the security issues affecting python-django in Wheezy

Hello, On Wed, 06 Sep 2017, Ola Lundqvist wrote: > The Debian LTS team recently reviewed the security issue(s) affecting your > package in Wheezy: > https://security-tracker.debian.org/tracker/CVE-2017-12794 The advisory (https://www.djangoproject.com/weblog/2017/sep/05/security-releases/) says

[Python-modules-team] Bug#863267: Bug#863267: Miscalculates MigrationHistory dependencies between multiple django apps - regression from 1.8

Hi, On Tue, 30 May 2017, Senthil Kumaran S wrote: > I tested the new version ie., test2 and got a traceback as shown here - > File "/usr/lib/python2.7/dist-packages/django/db/migrations/state.py", > line 249, in __init__ > raise ValueError("\n".join(error.msg for error in errors)) >

[Python-modules-team] Bug#863267: Bug#863267: Miscalculates MigrationHistory dependencies between multiple django apps - regression from 1.8

On Tue, 30 May 2017, Senthil Kumaran S wrote: > I tested the patch with lava-server, which ended up with a traceback as > seen here - http://paste.debian.net/952276/ Thanks, can you try again with another test version ? $ dget

[Python-modules-team] Bug#863267: Bug#863267: Miscalculates MigrationHistory dependencies between multiple django apps - regression from 1.8

On Mon, 29 May 2017, Raphael Hertzog wrote: > Option 4. Fix Django 1.10 with the attached patches. Updated patches attached, I missed to update some tests to account for the move of the detect_soft_applied() method. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: ht

Re: [Python-modules-team] python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED

On Wed, 24 May 2017, Uwe Kleine-König wrote: > With my model that would be: > > - sid/testing has both, latest version and latest LTS (including >security) > - jessie-backports strictly follows django-lts and so shouldn't be >much of a headache. - $stable has both - $oldstable has

Re: [Python-modules-team] python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED

Hello, On Wed, 24 May 2017, Uwe Kleine-König wrote: > An alternative idea would be to have two separate (source) packages in > sid: django and django-lts. Then django-lts could be put into backports > and so maintained according to the backport policy. I don't really like the idea of a separate

Re: [Python-modules-team] python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED

On Wed, 24 May 2017, Rhonda D'Vine wrote: > > Then we have similar issues as the ones raised by Raphael, where the life > > of the package maintainer is made difficult. > > He actively chose to ignore the guidelines, and actively chose to not > communicate about that. That's very disappointing,

Re: [Python-modules-team] python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED

On Wed, 24 May 2017, Ian Campbell wrote: > Yet 1.10.x is going to be in Stretch, according to [0]? If users want > LTS then why aren't we shipping that in our upcoming stable release > (whether its instead of or in addition to the latest release)? Because of miscommunication between the Django

Re: [Python-modules-team] python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED

On Wed, 24 May 2017, Adrian Bunk wrote: > > This is because backports maintainers are expected to keep the packages > > they upload there as secure. > > "are expected" != "are actually doing" > > > If the rules are not allowing us to do that, then the rules are bad. > > The biggest general

Re: [Python-modules-team] python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED

On Wed, 24 May 2017, Holger Levsen wrote: > On Wed, May 24, 2017 at 12:32:13PM +0200, Raphael Hertzog wrote: > > Right now, I'm maintaining 1.8.x in jessie-backports, we have 1.10.x in > > stretch. If I disappear and nobody else is willing to maintain 1.8.x, you > > can just

Re: [Python-modules-team] python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED

On Wed, 24 May 2017, Adrian Bunk wrote: > This part of the policy continues with: > > If your package had a security update you can upload a new backport > even if its not yet in testing. If you have good reasons to update a > package which is already is in backports with a newer version

Re: [Python-modules-team] python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED

Hi, I'm ignoring the personal attack and threats of ACL removal because that does not bring the discussion further, but I want to highlight that you could have avoided this, I have not said anything bad about your work, I'm just discussing the policy. On Wed, 24 May 2017, Rhonda D'Vine wrote: >

Re: [Python-modules-team] python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED

On Wed, 24 May 2017, Adrian Bunk wrote: > The maintainer of the python-django backport not acting according to > policy is what started this discussion. Let's speak of the policy. It says this: > To guarantee an upgrade path from stable+backports to the next stable, the > package should be in

Re: [Python-modules-team] python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED

On Wed, 24 May 2017, Adrian Bunk wrote: > What is the minimum amount of technical checking that has to be in place > before something like this could be done? For the backports team, none. For the maintainer, he must know this policy and act accordingly. If someone reports that it does not

Re: [Python-modules-team] python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED

On Wed, 24 May 2017, Alexander Wirt wrote: > It is maybe a problem and maybe we should get the policy changed - I > personally don't think too. I don't wan't software that isn't in testing in > backports - but doing it behinds our back is not an option. How do we fix the policy then?

Re: [Python-modules-team] python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED

(please cc me on answers) On Tue, 23 May 2017, Debian FTP Masters wrote: > please take the version from testing, not a version that never was in the > archive I have been maintaining the 1.8.x LTS version of Django in jessie-backports since December 2015. Except the very first, none of the

[Python-modules-team] Bug#849652: Bug#849652: faker: FTBFS on 32-bit: ValueError: timestamp out of range for platform time_t

On Mon, 30 Jan 2017, Brian May wrote: > Help in fixing this RC bug would be appreciated. I have forwarded this > upstream, however need a quick fix for the Debian package (not sure but > suspect it might be too late for stretch). > > Unfortunately, not sure where to start. I don't understand this

[Python-modules-team] Bug#850236: python-django: FTBFS (AssertionError)

On Thu, 05 Jan 2017, Santiago Vila wrote: > It depends. My goal is to build 25000 source packages in a row and have > 0.5 failures on average in total (i.e. closer to 0 than to 1). > > If we have 50 packages which FTBFS randomly, they should fail less > than 1% on average. > > One week every 4

[Python-modules-team] Bug#844139: python-django: FTBFS: Tests failures

Hi, On Sat, 12 Nov 2016, Scott Kitterman wrote: > > This failure happens on a CPU with TSX extensions available, but is not > > reproducible on a machine without them. I can't reproduce this either on my machine. But I have other failures (see below). Lucas, can you see if you reproduce your

Re: [Python-modules-team] Wheezy update of python-django?

Hi, On Fri, 22 Jul 2016, Brian May wrote: > > We got the ack from release team to rebase jessie on latest 1.7.x (see > > #807654) and it makes sense to rebase wheezy on latest 1.4.x (in > > particular since 1.4.x was a LTS version). > > I am out of time for this month, however should be able to

Re: [Python-modules-team] Wheezy update of python-django?

Hi, On Tue, 19 Jul 2016, Chris Lamb wrote: > the Debian LTS team would like to fix the security issues which are > currently open in the Wheezy version of python-django: > https://security-tracker.debian.org/tracker/CVE-2016-6186 > > Would you like to take care of this yourself? I won't claim

[Python-modules-team] Bug#831836: python-django: Add pymysql support

On Tue, 19 Jul 2016, Jeremy Bicha wrote: > Patch attached. But there's no patch attached. :) -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/

[Python-modules-team] Bug#828207: FTBFS: AttributeError: 'module' object has no attribute 'SubfieldBase'

Control: severity -1 important On Sun, 26 Jun 2016, Brian May wrote: > Guessing this might be a Django issue with 1.10~beta1-1: Yes, SubfieldBase was deprecated since 1.8 and it's removed in 1.10. 1.10 is not yet in sid, so reducing severity. Cheers, -- Raphaël Hertzog ◈ Debian Developer

Re: [Python-modules-team] FTBFS trouble upgrading python-django to 1.9.4-1

On Sat, 05 Mar 2016, Luke Faraone wrote: > An excerpt of the end of the log of the build failure is attached. > > Notably, similar ln/mv errors happen in 1.9.2-1[2], but they aren't > fatal. > > Does anybody have an idea what's wrong here? The logic in the find call. The first part of the "or"

Re: [Python-modules-team] FTBFS trouble upgrading python-django to 1.9.4-1

On Sun, 06 Mar 2016, Brian May wrote: > I tried to reproduce, but my build crashed before it even got to this > step. > > Traceback (most recent call last): > File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 75, in > __init__ > sl = self._semlock =

[Python-modules-team] Bug#813571: virtualenv: Broken dependencies

Hello, bringing Barry in the discussion since he's the one who broke it all... On Wed, 03 Feb 2016, Francisco José Rodríguez Bogado wrote: > I'm trying to install virtualenv on Sid. It depends on python3-virtualenv, > that > depends on python-setuptools-whl *and* python-pip-whl. But

[Python-modules-team] Bug#803096: python-bcrypt/2.0.0-1

On Fri, 01 Jan 2016, Daniel Stender wrote: > I've got python-bcrypt 2.0.0 ready. There's a small issue in debian/rules: export DEB_BUILD_OPTIONS=nocheck # testsuite not shipped on Pypi You are not supposed to set this option. This option is for the person which builds the package. If

Re: [Python-modules-team] Question about Django in bpo8

Hi, On Tue, 05 Jan 2016, W. Martin Borgert wrote: > I saw that 1.8.8 has just been uploaded to jessie-backports. > Testing has already 1.9, 1.9.1 to come. > What is the plan in respect to backports? > Will 1.9.x go into bpo8 at some point? > When? Or why not? :~) I don't plan to push 1.9.x in

[Python-modules-team] Bug#803096: python-bcrypt: please update python-bcrypt

Hi, On Wed, 30 Dec 2015, Daniel Stender wrote: > Yes, I would like to help with this. > > Actually also #796853 suggests to switch to pyuca-bcrypt (the other one), > that bug is grave > so action is needed. Why do you name it pyuca-bcrypt? The pypi package name mentionned in that bug report is

[Python-modules-team] Bug#803096: python-bcrypt: please update python-bcrypt

Control: severity -1 important On Mon, 26 Oct 2015, Daniel Stender wrote: > Please update python-bcrypt, we need >= 1.1.0 for Privacyidea. I have a similar need for Django 1.9 whose test suite currently fails due to this... Except that the package currently tracks py-bcrypt:

[Python-modules-team] Bug#802121: pysvn: FTBFS: error: ‘svn

Hi, On Sun, 20 Dec 2015, Josue Ortega wrote: > > It would be nice to fix it and get the package back in testing. > > I have pushed the new upstream release (Python 2 version only) that fixes this > bug to the DPMT git repo[1], I have now DM upload permissions for this > package, > Can you

[Python-modules-team] Bug#802121: pysvn: FTBFS: error: ‘svn

On Wed, 18 Nov 2015, Hideki Yamane wrote: > On Sat, 17 Oct 2015 17:00:45 +0100 "Chris West (Faux)" > wrote: > > Source: pysvn > > Version: 1.7.8-1 > > Severity: serious > > Justification: fails to build from source > > This FTBFS bug is fixed in new upstream

Re: [Python-modules-team] [python-django] 01/01: Use dpkg-maintscript-helper's dir_to_symlink to correctly replace the app_template and project_template symlinks added in 1.9~rc2-2. (Closes: #807683)

Hi, On Sat, 12 Dec 2015, Chris Lamb wrote: > --- /dev/null > +++ b/debian/python-django.postinst > @@ -0,0 +1,11 @@ > +#!/bin/sh > + > +#DEBHELPER# > + > +for X in app_template project_template > +do > + dpkg-maintscript-helper dir_to_symlink \ > +

[Python-modules-team] Bug#807654: jessie-pu: package python-django/1.7.11-1

Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hello, I would like to update python-django in jessie to the latest upstream bug fix release in the 1.7.x branch, aka 1.7.11. It should also be the last upstream release in that

Re: [Python-modules-team] Django 1.9

Hi, On Sat, 05 Dec 2015, Neil Williams wrote: > Yet when I actually install django1.9 from unstable, I get a completely > unanticipated error from the removal of an item that was *not* declared > as deprecated in the django tests but which, nonetheless, crippled > localhost with a HTTP 500. > >

[Python-modules-team] Bug#807097: python-django: Undeclared removal of previously supported features causes crashes

On Sat, 05 Dec 2015, Neil Williams wrote: > http://paste.debian.net/341382/ So this one is fairly obvious, I already replied that it's django.template.base.Origin that you should have used in the first place since where the code actually is... relying on the fact that it was also imported in

Re: [Python-modules-team] Django 1.9

On Fri, 04 Dec 2015, Brian May wrote: > I see that Django 1.9 is now in unstable... Yeah, I noticed the upload on IRC and asked Chris to cancel it but it was too late already. > Raphael Hertzog <hert...@debian.org> writes: > > > For this to be viable, we would just ha

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

Hi, On Thu, 26 Nov 2015, Luke Faraone wrote: > Stretch freezes at 2016-12-05[1]. This is the hard freeze. Switching from Django 1.10 to 1.11 is a like a transition and will probably not be accepted after the transition freeze... > Per the Django roadmap published in June[2], 1.11 LTS will be

Re: [Python-modules-team] Django 1.9

On Thu, 26 Nov 2015, Luke Faraone wrote: > I need to dive a bit deeper into Django's development cycle for 1.11 > LTS. If they freeze around the same time as Debian, perhaps we'd be > able to start shipping 1.11~pre () in unstable as soon as they start > putting out alphas, then just continue to

Re: [Python-modules-team] Django 1.9

On Tue, 24 Nov 2015, Barry Warsaw wrote: > Also, Django 1.9rc1 was released last week and their roadmap says that 1.9 > final should be out possibly by next week (2 weeks after rc1 if no rc2 is > necessary). 1.9 *will* officially support 3.5. > > What's the plan for Django 1.9? I think we

[Python-modules-team] Bug#802677: Bug#802677: Raising severity - blocking RC bug fixes

On Wed, 25 Nov 2015, Neil Williams wrote: > > Should I uploaded the patched version of Django anyway? > > If you are finding problems testing, I would prefer that the > upload was not made to unstable. Could you upload to experimental or to > some other location which I can use for further

[Python-modules-team] Bug#802677: Raising severity - blocking RC bug fixes

Hi, On Tue, 24 Nov 2015, Brian May wrote: > On Mon, Nov 16, 2015 at 02:16:39PM +0100, Raphael Hertzog wrote: > > I forwarded this issue upstream. It looks like the fix should be > > relatively easy and hopefully upsream will pick it up shortly. > > Is this bug really serious

[Python-modules-team] Bug#802677: Raising severity - blocking RC bug fixes

Control: forwarded -1 https://code.djangoproject.com/ticket/25761 On Mon, 16 Nov 2015, Neil Williams wrote: > affects 801930 Note that affects needs a bug and a package. :) > django-testscenarios has an RC bug (801930) related to django1.8 but > now cannot be built because python-testtools

[Python-modules-team] Bug#801928: Django 1.8 has been uploaded to unstable

Control: severity -1 serious Hello, I just uploaded Django 1.8 to unstable and I am thus raising the severity of this bug to serious. Please fix this bug ASAP if you don't want it to be a target of the release manager's auto-removal scripts. Thank you! -- Raphaël Hertzog ◈ Debian Developer

[Python-modules-team] Bug#801931: Bug#801931: python-passlib: Fails to build from source with Django 1.8

On Sat, 17 Oct 2015, Brian May wrote: > hert...@debian.org writes: > > > The failing build log of your package is available here: > > https://people.debian.org/~hertzog/django18-rebuild/python-passlib_1.6.5-1 > > It looks to me like something went wrong in your build system? Why was > it looking

[Python-modules-team] Django 1.8 in unstable in early November

Hello, I just filed 20 bugs on packages that FTBFS with Django 1.8. They have two weeks to be fixed before we upload Django 1.8 to unstable. https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=python-dja...@packages.debian.org;tag=django18 If you maintain a package in the Django ecosystem,

Re: [Python-modules-team] Fwd: Django 1.8 transition

Hi, On Thu, 27 Aug 2015, Luke Faraone wrote: I did a test rebuild of packages that depend on python-django under 1.7 (unstable)[1] and 1.8 (experimental)[2]. I filed bugs against the packages that FTBFS under the current version in unstable if there was not one opened already. Obviously a

Re: [Python-modules-team] squeeze update of python-django?

Hi, On Wed, 19 Aug 2015, b...@decadent.org.uk wrote: the Debian LTS team would like to fix the security issues which are currently open in the Squeeze version of python-django: https://security-tracker.debian.org/tracker/CVE-2015-5963 https://security-tracker.debian.org/tracker/CVE-2015-5964

[Python-modules-team] Bug#780989: squeeze update of dulwich?

Hello Jelmer, the Debian LTS team would like to fix the security issues which are currently open in the Squeeze version of dulwich: https://security-tracker.debian.org/tracker/CVE-2014-9706 https://security-tracker.debian.org/tracker/CVE-2015-0838 (CVE-2014-9390 is also open but it's lower

[Python-modules-team] Bug#780873: About the security issues affecting python-django in Squeeze

Hello dear maintainer(s), the Debian LTS team recently reviewed the security issue(s) affecting your package in Squeeze: https://security-tracker.debian.org/tracker/CVE-2015-2317 We decided that we would not prepare a squeeze security update (usually because the security impact is low and that

[Python-modules-team] Bug#781033: python-django: manage dbshell fails to transmit settings password to postgresql

Hi, On Mon, 23 Mar 2015, Jean-Michel Nirgal Vourgère wrote: When one runs the generated ./manage.py with runserver argument, django find the host, dbname, username, and password and runs ok. But when one runs it with dbshell argument, django only uses host, dbname and username. Then a

[Python-modules-team] Bug#781053: unblock: python-django/1.7.7-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package python-django There's a new upstream security/bugfix release fixing two CVE that I just uploaded to unstable: https://docs.djangoproject.com/en/1.7/releases/1.7.7/

[Python-modules-team] Bug#781033: python-django: manage dbshell fails to transmit settings password to postgresql

Control: forwarded -1 https://code.djangoproject.com/ticket/23658 On Mon, 23 Mar 2015, Jean-Michel Nirgal Vourgère wrote: Another possibility is PGPASSFILE env, that provide an alternate ~/.pgpass file. I believe a temporary file would work. This wouldn't require hacking any existing .pgpass.

Re: [Python-modules-team] Bug#775892: unblock (pre-approval): python-django/1.7.3-1

Hi Mehdi, On Tue, 17 Feb 2015, Mehdi Dogguy wrote: Le 2015-02-04 09:01, Raphael Hertzog a écrit : it's been two weeks that I have opened this pre-approval request and I got almost no feedback from the release team (except Neil saying that he has no answer for me on IRC). Neil or Niels

Re: [Python-modules-team] Bug#775892: unblock (pre-approval): python-django/1.7.3-1

Control: retitle -1 unblock: python-django/1.7.4-1 On Wed, 04 Feb 2015, Raphael Hertzog wrote: File the above bug report with severity serious and upload 1.7.4-1 to sid closing the bug. Now done. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com

Re: [Python-modules-team] Bug#775892: unblock (pre-approval): python-django/1.7.3-1

, 29 Jan 2015, Raphael Hertzog wrote: I want to add that my request is now to upload 1.7.4-1 since upstream released a new bugfix version: https://docs.djangoproject.com/en/1.7/releases/1.7.4/ BTW, that version contains a fix for an unreported FTBFS that we have in Debian and that has been

Re: [Python-modules-team] 1.7.2 in experimental; reasons to not push to unstable?

Hi, On Wed, 04 Feb 2015, Brian May wrote: On 21 January 2015 at 03:29, Raphael Hertzog hert...@debian.org wrote: On Thu, 15 Jan 2015, Luke Faraone wrote: 1.7.3 was issued a few days ago with several security fixes. I've committed an UNRELEASED update in the debian/experimental branch

Re: [Python-modules-team] 1.7.2 in experimental; reasons to not push to unstable?

Hi, On Wed, 21 Jan 2015, Raphael Hertzog wrote: Do you think it would help if I created a Debian bug report pointing to https://code.djangoproject.com/ticket/23581 ? It can't hurt in particular if you believe it's worth a serious severity. I opened the pre-approval request: #775892 I

[Python-modules-team] Bug#775375: python-django: diff for NMU version 1.7.1-1.1

Hello Neil, On Fri, 16 Jan 2015, Neil Williams wrote: I've prepared an NMU for python-django (versioned as 1.7.1-1.1) and I'll do some more testing of it before uploading it, likely to Delayed-2 or possibly 4. Thanks for this, but we prefer to try to push 1.7.3 into unstable/jessie. I'm

[Python-modules-team] Bug#616331: python-django: changed_data in django froms is undocumented

Control: forwarded -1 https://code.djangoproject.com/ticket/24191 Hi Björn, On Thu, 03 Mar 2011, Björn Påhlsson wrote: Would be nice if the Forms API page would mention it. Indeed, I submitted this to the upstream developers in the above ticket and I put you in copy so that you can follow the

Re: [Python-modules-team] 1.7.2 in experimental; reasons to not push to unstable?

Hi, On Thu, 15 Jan 2015, Luke Faraone wrote: 1.7.3 was issued a few days ago with several security fixes. I've committed an UNRELEASED update in the debian/experimental branch; is there a compelling reason not to push it to unstable? I would like to get 1.7.3 into jessie but before pushing it

Re: [Python-modules-team] 1.7.2 in experimental; reasons to not push to unstable?

Hi, On Wed, 21 Jan 2015, Brian May wrote: On 21 January 2015 at 03:29, Raphael Hertzog hert...@debian.org wrote: I would like to get 1.7.3 into jessie but before pushing it that way, we have to convince the release team. Would you like to open a pre-appoval request with a debdiff

[Python-modules-team] Bug#765117: Bug#765117: python-django: FTBFS: Tests failures

On Tue, 14 Oct 2014, Brian May wrote: So to me it looks like loaddata is generating 1 warning, when we were hoping for no warnings. Thanks for the initial analysis. I forwarded a bug to Django: https://code.djangoproject.com/ticket/23651 Now I am a bit puzzled as to (a) why this didn't occur

[Python-modules-team] Bug#755602: Django 1.7 uploaded to unstable

Control: severity -1 serious Hello, as announced previously I just uploaded Django 1.7 to unstable. This bug is thus release critical now. Please do your best to get it fixed soon and ensure that your package doesn't get removed from testing. Cheers, -- Raphaël Hertzog ◈ Debian Developer

[Python-modules-team] Bug#755588: Django 1.7 will be uploaded to unstable soon

[ This mail is sent to all the bugs listed on https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=python-dja...@packages.debian.org;tag=django17 ] Hello, I just uploaded the official Django 1.7 release to experimental. It is our plan to move it to unstable next week (let's say on monday 15th

Re: [Python-modules-team] [django-announce] [ANNOUNCE] Django 1.7 released

Hi, On Thu, 04 Sep 2014, Brian May wrote: On 3 September 2014 19:01, Raphael Hertzog hert...@debian.org wrote: Given the discussions we had on debian-python, are we sure that we want to force it through even though we still have many known problems on https://bugs.debian.org/cgi-bin

Re: [Python-modules-team] [django-announce] [ANNOUNCE] Django 1.7 released

Hi, On Tue, 02 Sep 2014, Luke Faraone wrote: 2014-09-02 15:13 GMT-07:00 James Bennett ubernost...@gmail.com: Django 1.7 is now available: https://www.djangoproject.com/weblog/2014/sep/02/release-17-final/ I'll prepare the upload for unstable tonight. Given the discussions we had on

Re: [Python-modules-team] [python-django] branch master updated (f8054c2 - 18d13a0)

Hi, On Thu, 21 Aug 2014, Luke Faraone wrote: This is an automated email from the git hooks/post-receive script. lfaraone pushed a change to branch master in repository python-django. from f8054c2 releasing package python-django version 1.6.5-5 new 3a30a56 Lets just

[Python-modules-team] Bug#755588: Fails to build with Django 1.7

Control: tag -1 confirmed The package fails to build with Django 1.7: [...] WARNINGS: ?: (1_7.W001) MIDDLEWARE_CLASSES is not set. HINT: Django 1.7 changed the global defaults for the MIDDLEWARE_CLASSES. django.contrib.sessions.middleware.SessionMiddleware, djang

[Python-modules-team] Bug#755595: Fails to build with Django 1.7

Control: tag -1 confirmed The package fails to build with Django 1.7: debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' set -e; \ for python in python2.7; do \ PYTHONPATH=. $python runtests.py; \ done Traceback (most recent call last): File runtests.py,

[Python-modules-team] Bug#755592: Fails to build with Django 1.7

Control: tag -1 + confirmed The package fails to build with Django 1.7: debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' django-admin startproject testproject Using: Python 2.7 if [ -d testproject/testproject ]; then \ cp debian/settings.py

[Python-modules-team] Bug#755665: Fails to build with Django 1.7

Control: tag -1 + confirmed The package fails to build with Django 1.7: debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' set -e; \ for python in python2.7; do \ PYTHON=$python ./runtests.sh; \ done PASS: normal settings PASS: normal settings (--help) FAIL:

[Python-modules-team] Bug#755667: Fails to build with Django 1.7

Control: tag -1 + confirmed The package fails to build with Django 1.7: debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' set -e; \ for python in python2.7; do \ PYTHONPATH=. $python example_consumer/manage.py test --settings=example_consumer.settings

[Python-modules-team] Bug#755647: Fails to build with Django 1.7

Control: tag -1 + confirmed The package fails to build with Django 1.7: debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' django-admin startproject testproject Using: Python 2.7 if [ -d testproject/testproject ]; then \ cp debian/settings.py

[Python-modules-team] Bug#755612: Fails to build with Django 1.7

Control: tag -1 + confirmed The package fails to build with Django 1.7: debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' django-admin startproject testproject Using: Python 2.7 if [ -d testproject/testproject ]; then \ cp debian/settings.py

[Python-modules-team] Bug#755602: Fails to build with Django 1.7

Control: tag -1 + confirmed The package fails to build with Django 1.7: debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' set -e; \ for python in python2.7; do \ PYTHONPATH=. $python runtests.py; \ done Using Python version 2.7.8 from /usr/bin/python2.7

[Python-modules-team] Bug#755603: Fails to build with Django 1.7

Control: tag -1 + confirmed The package fails to build with Django 1.7: debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' set -e; \ for python in python2.7; do \ PYTHONPATH=. $python runtests.py; \ done Traceback (most recent call last): File

[Python-modules-team] Bug#755604: Fails to build with Django 1.7

Control: tag -1 + confirmed The package fails to build with Django 1.7: debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' set -e; \ for python in python2.7; do \ $python sitetree/runtests.py; \ done Traceback (most recent call last): File

[Python-modules-team] Bug#755632: Fails to build with Django 1.7

Control: tag -1 + confirmed The package fails to build with Django 1.7: debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' set -e; \ cd voting/tests; \ for python in python2.7; do \ PYTHONPATH=:../.. $python runtests.py; \ done Traceback (most recent call

[Python-modules-team] Bug#755639: Fails to build with Django 1.7

Control: tag -1 + confirmed The package fails to build with Django 1.7: debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' PYBUILD_SYSTEM=custom \ PYBUILD_TEST_ARGS=cd {build_dir}; {interpreter} {dir}/runtests_sqlite.py dh_auto_test I: pybuild base:170: cd

[Python-modules-team] Bug#755633: Fails to build with Django 1.7

Control: tag -1 + confirmed The package fails to build with Django 1.7: debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' mkdir -p tmp-locales localedef -i en_US -c -f UTF-8 tmp-locales/en_US.UTF-8 set -e; \ for python in python2.7; do \ for name in pil

[Python-modules-team] Bug#755644: Bug#755644: python-django-jsonfield: Please ensure it works with Django 1.7

Hi, On Wed, 23 Jul 2014, Brian May wrote: I think the library itself is fine, but the tests fail: brian@aquitard:~/tree/debian/unstable/python-django-jsonfield/python-django-jsonfield-0.9.12$ python tests.py [...] django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet. You

[Python-modules-team] Bug#755647: Problem migrating from South to Django migrations for Linux distributions

Hi Andrew, thanks for your quick answer. On Thu, 24 Jul 2014, Andrew Godwin wrote: There is no way around this; it's unfortunate that the packaging situation means that Django will get auto-upgraded as part of a distribution upgrade; I'm surprised that Debian hasn't had this with packages

[Python-modules-team] Bug#736878: python-django: Please provide python3-django

Hi, On Fri, 27 Jun 2014, Brian May wrote: On 26 June 2014 11:40, Brian May br...@microcomaustralia.com.au wrote: I committed a working version to subversion. I just uploaded this to DELAYED/10. Please skip the delayed waiting. It will have to go through NEW anyway. Did you manage to

[Python-modules-team] Bug#736878: python-django: Please provide python3-django

Hello Brian, thanks for your work! On Tue, 24 Jun 2014, Brian May wrote: New patch attached. /etc/bash_completion.d/django_bash_completion and /usr/bin/django-admin now supplied with python3-django. python-django recommends python3-django as a result. Hopefully I have set the

[Python-modules-team] Bug#736878: python-django: Please provide python3-django

On Tue, 24 Jun 2014, Brian May wrote: On 24 Jun 2014 16:51, Raphael Hertzog hert...@debian.org wrote: It doesn't look clean to have python-django recommends python3-django just to have django-admin and django_bash_completion. I believe it would better to move them to a python-django-common

[Python-modules-team] Bug#736878: python-django: Please provide python3-django

(CCing Barry who expressed interested in python3-django as well) Hi, On Tue, 17 Jun 2014, Brian May wrote: What needs to happen in order to make this happen? Are there any missing dependencies? Django has very few dependencies, so I don't think this is what is missing. It's just a matter of

Re: [Python-modules-team] python-django 1.6.5-1~bpo70+1

Hi, On Mon, 26 May 2014, Uwe Kleine-König wrote: Also a security announcement would be in order, corresponding to the following CVEs / DSAs: CVE-2013-4315 / DSA-2755-1 CVE-2013-1443 / DSA-2758-1 CVE-2014-0472 + CVE-2014-0473 + CVE-2014-0474 + CVE-2014-1418 + CVE-2014-3730 /

[Python-modules-team] Bug#709622: python-django-registration: Does not work with django 1.5 (please upgrade upstream to hg mainline)

Hello Stephan, On Fri, 24 May 2013, Stephan Suerken wrote: upstream version 0.8 is not compatible with django 1.5, which is now the version in sid, so it's currently unusable. The current upstream mainline works fine (1.4 and 1.5), there is however no release yet. Fwiw, as a POC, I

[Python-modules-team] Bug#697721: python-django-registration: FTBFS with python3-sphinx: AttributeError: 'str' object has no attribute '__dict__'

On Tue, 08 Jan 2013, Jakub Wilk wrote: This happens because the source package includes doctree pickles (in which parsed rST sources are cached) were generated by Python 2.X, and cannot be loaded by Python 3.X. Please ask upstream to exclude the doctrees/ subdirectory from their tarballs.

[Python-modules-team] Bug#686104: python-django-registration: Not compatible with, Django 1.4.

On Fri, 31 Aug 2012, Winfried Tilanus wrote: On 08/31/2012 08:41 AM, Raphael Hertzog wrote: What openly available data are you referring to? The hash calculated in django-registration is send out to people registering a new account, as part of the url to click on when confirming

[Python-modules-team] Bug#551926: Bug#551926: cannot be installed together with pip or pip-python

reassign 551926 ftp.debian.org retitle 551926 RM: pip -- tool for scripted and third-party CPAN distribution installation thanks On Sat, 08 May 2010, gregor herrmann wrote: I'm not sure how useful/needed/... pip is on its own. But looking at the (non-existant) rdepends and the popcon values I

[Python-modules-team] Bug#564377: Bug#562449: celementtree: Depends on python2.4 packages

forcemerge 562449 564377 reassign 562449 ftp.debian.org retitle 562449 RM: celementtree -- RoM; only useful with python 2.5 thanks On Thu, 24 Dec 2009, dktrkr...@debian.org wrote: Squeze will release with Python 2.5 and Python 2.6, while Python 2.4 is scheduled for removal when no packages

[Python-modules-team] Bug#482706: Source format 3.0 (quilt) allowed in testing/unstable

[ Same message sent in bcc to all remaining FTBFS with new source format ] Hello, the new source format 3.0 (quilt) is now allowed in testing/unstable and having all packages buildable with the new format is a release goal (http://wiki.debian.org/ReleaseGoals/NewDebFormats). Thus it would be

Re: [Python-modules-team] getting ready for python-django_1.0

Hi, On Wed, 30 Jul 2008, Eddy Mulyono wrote: Dear Debian experimental python-django maintainers, I would like to contribute to Debian's python-django package In particular, I want to: 1. run unit tests during build (patch already in Ubuntu) 2. make HTML documentation during build

[Python-modules-team] Bug#460413: python-django-registration: Cannot import ugettext_lazy

On Sat, 12 Jan 2008, Vincent Bernat wrote: After installing python-django-registration and setting up on a fresh Django project following instructions in overview.txt.gz, I get this error: Error: Couldn't install apps, because there were errors in one or more models: registration: cannot