It runs most tests in the test suite, minus some tests that require networking, and the FileSaveRaceConditionTest.
According to James Bennet, that last item is not a Django bug. Getting it "fixed" will require me to probe into pbuilder/chroot/soyuz/buildbot-land, which I don't think I'll be able to finish before Intrepid's launch.
Other than that, though, I've been using my 1.0-1ubuntu1~ppa3, and it works fine for me.
> Please remember to do it as a merge from the current Ubuntu version to that the Ubuntu change history is preserved.
I might need some help with merging the Ubuntu changelog with the Debian changelog. Which entries from Debian changelog should I include? Which entries should I not include?
@Scott:
> Are you close to a final debdiff for this?
If I understand correctly, I should debdiff python- django_ 0.96.2- 1ubuntu2 against my python- django_ 1.0-1ubuntu1~ ppa3.
Am I correct? (The deb.diff is 15.2 MB. Should I upload it anyway?)
I didn't get much further than https:/ /bugs.launchpad .net/ubuntu/ +source/ python- django/ +bug/264191/ comments/ 24
It runs most tests in the test suite, minus some tests that require networking, and the FileSaveRaceCon ditionTest.
According to James Bennet, that last item is not a Django bug. Getting it "fixed" will require me to probe into pbuilder/ chroot/ soyuz/buildbot- land, which I don't think I'll be able to finish before Intrepid's launch.
Other than that, though, I've been using my 1.0-1ubuntu1~ppa3, and it works fine for me.
> Please remember to do it as a merge from the current Ubuntu version to that the Ubuntu change history is preserved.
I might need some help with merging the Ubuntu changelog with the Debian changelog. Which entries from Debian changelog should I include? Which entries should I not include?