Sync python-django 1.4-1 (main) from Debian sid (main)

Bug #972104 reported by Thomas Bechtold
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
python-django (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Please sync python-django 1.4-1 (main) from Debian sid (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Merge with Debian. Remaining changes:
    - 09_test_view_decorator_sleep.diff increases the sleep time to
      reduce race condition effects on build machines.
      https://code.djangoproject.com/ticket/16686 (LP: #829487)
  * debian/patches/{psycopg2_creation.diff,compat-psycopg2-plus2.4.2.diff}:
    - New patches, resolve compatibility with psycopg2 > 2.4.1, patches
      based on upstream submissions, rebasing courtesy of Dave Pifke.
    - LP: #905837

- 09_test_view_decorator_sleep.diff: fixed upstream
- debian/patches/{psycopg2_creation.diff,compat-psycopg2-plus2.4.2.diff}: fixed upstream

Changelog entries since current precise version 1.3.1-4ubuntu1:

python-django (1.4-1) unstable; urgency=low

  * New upstream release. Closes: #666003
  * Fix watch file to correctly extract the version number from the URL.
  * Updated Standards-Version to 3.9.3 (no change needed).
  * Drop 01_disable_url_verify_regression_tests.diff since upstream test
    suite has been modified to work even without internet connection.
  * Update 04_hyphen-manpage.diff to apply again.
  * Drop 05_fix_djangodocs_sphinx_ext.diff which has been merged
    upstream.
  * Update 06_use_debian_geoip_database_as_default.diff to apply on
    renamed file.
  * Drop 07_fix_for_sphinx1.1.2.diff merged upstream.
  * Drop 08_fix_test_week_view_allow_future.diff, merged upstream.
  * Add 01_disable_broken_test.diff to disable a test that fails with
    the current python 2.7 version in Debian.

 -- Raphaël Hertzog <email address hidden> Sat, 31 Mar 2012 14:48:00 +0200

Revision history for this message
Daniel Holbach (dholbach) wrote :

Can you please add some information about this update? https://wiki.ubuntu.com/FreezeExceptionProcess

Revision history for this message
Thomas Bechtold (toabctl) wrote :

The changes for 1.4 are listed here: https://docs.djangoproject.com/en/dev/releases/1.4/

build logs, installation output and test attached.

Revision history for this message
Stefano Rivera (stefanor) wrote :

There are a lot of django applications and modules in Ubuntu. Are they ready for 1.4?

Revision history for this message
Thomas Bechtold (toabctl) wrote :

i think the dependencies should be handled with dpkg? or does all the python-django-XXX packages just depend on python-django without any version number? if so, i think that's a bug in all the python-django-XXX packages.

anyway, i don't know if all the packages are compatible with the 1.4 version. are we sure that all packages are compatible with 1.3?

Revision history for this message
Stefano Rivera (stefanor) wrote :

Thomas: Everything in the archive should be installable. If we provide 1.4, we are no longer providing 1.3.

It seems that most django-XXX packages depend on python-django >= X, meaning they are expecting to be forward-compatible. But that doesn't mean that there won't be compatibility issues, and we usually try and find and fix those before starting the transition.

If they aren't already compatible with 1.3, that's a bug. But that's no reason to introduce more such bugs.

Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

I personally work with Django every day. I've never used Debian/Ubuntu packages for Django-related stuff (always virtualenv), but I can say that so far I haven't found an application that "just works" after an upgrade to 1.4. With "application" I'm not referring just to the modules/extensions for Django, but also to the users' own webapps. This is caused by the fact that Django 1.4 introduces a few but important backward-incompatible changes.

It's true that Django 1.4 has a lot of interesting new stuff, but for these reasons I'm against the sync because we are too near the release of Precise.

Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 972104] Re: Sync python-django 1.4-1 (main) from Debian sid (main)

Sounds like sticking with 1.3 may be the best answer.

Revision history for this message
Stefano Rivera (stefanor) wrote :

Yeah, I'm fairly hesitant about upgrading to 1.4, although buxy seemed confident on IRC:

12:51 < tumbleweed> buxy: was the django transition really that easy? I ask
                    because someone proposed transitioning to 1.4 in Ubuntu
https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/972104
13:42 < buxy> tumbleweed: there's no easy way to know whether all reverse deps
              are compatible with 1.4 but very few things are
              backwards-incompatible, so I don't expect many problems

Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 972104] Re: Sync python-django 1.4-1 (main) from Debian sid (main)

Maybe this needs a "heave them all at a PPA and call for testing" approach?

Revision history for this message
Thomas Bechtold (toabctl) wrote :

@scott: a ppa with all the packages would be nice.

Revision history for this message
Iain Lane (laney) wrote :

→ incomplete. Please reset to New once there is something for the release team to approve (i.e. some comprehensive testing results)

Changed in python-django (Ubuntu):
status: New → Incomplete
Revision history for this message
Thomas Bechtold (toabctl) wrote :

i'm currently unable to create a ppa with all the django apps/projects for testing. so if nobody else setup the ppa, i think we go with 1.3 for precise.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Setting the status back to Confirmed since I believe this can be done for Quantal.

Changed in python-django (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Stefano Rivera (stefanor) wrote :

From the delta description in the changelog, looks like it can probably be synced.

Debian is already transitioned, so bug fixes for the apps should be coming through too.

Revision history for this message
Daniel Holbach (dholbach) wrote :

This bug was fixed in the package python-django - 1.4-1
Sponsored for Thomas Bechtold (toabctl)

---------------
python-django (1.4-1) unstable; urgency=low

  * New upstream release. Closes: #666003
  * Fix watch file to correctly extract the version number from the URL.
  * Updated Standards-Version to 3.9.3 (no change needed).
  * Drop 01_disable_url_verify_regression_tests.diff since upstream test
    suite has been modified to work even without internet connection.
  * Update 04_hyphen-manpage.diff to apply again.
  * Drop 05_fix_djangodocs_sphinx_ext.diff which has been merged
    upstream.
  * Update 06_use_debian_geoip_database_as_default.diff to apply on
    renamed file.
  * Drop 07_fix_for_sphinx1.1.2.diff merged upstream.
  * Drop 08_fix_test_week_view_allow_future.diff, merged upstream.
  * Add 01_disable_broken_test.diff to disable a test that fails with
    the current python 2.7 version in Debian.

 -- Raphaël Hertzog <email address hidden> Sat, 31 Mar 2012 14:48:00 +0200

Changed in python-django (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.