Dapper upgrade to Edgy: Frozen dist-upgrade and failed second run (in Finnish locales

Thanks for your bugreport.

This bug shows under rare circumstances when dpkg sends unexpected error lines. I will attach a debdiff with a fix and the fix will be uploaded to the archive soon.

I would appreciate if you could test the fixed binary here: http://people.ubuntu.com/~mvo/apt/python-apt/python-apt_0.6.19ubuntu9.1_i386.deb

Oh, and what does "libc6:n asetusten säätö" translate to in english?

thanks,
 Michael

Ok, I'm a bit newbie, so I don't know what am I supposed to do with the package. I installed it and it installed fine, but I don't know what to do next. When I run update-manager it tells me that my system is up to date, although the distribution upgrade clearly didn't complete last time.

asetusten säätö could be translated as adjustment of settings.

Thanks for your fast reply, great!
t. Niko

There are a lot of unfilled dependencies when trying to install that deb file on a dapper. If I force the installation, starting update-manager results in:
Traceback (most recent call last):
  File "/usr/bin/update-manager", line 32, in ?
    from UpdateManager.UpdateManager import UpdateManager
  File "/usr/lib/python2.4/site-packages/UpdateManager/UpdateManager.py", line 36, in ?
    import apt
ImportError: No module named apt

I applied the diff to dapper's python-apt source, built and installed new debs.

Now the update-manager seems to handle the upgrade to 6.10 just fine! Can the patched version be supplied with update-manager's distribution upgrade tool that is always downloaded when starting the upgrade, or should the patched version be pushed into dapper-updates?

I bet this should be fixed, in case it affects all the users of some locale.. and perhaps more. Was the problem just because of the non-ascii letters?

I think the problem is caused by the ":" character in some lines of the Finnish localisation. Parsing text is hard! (So use a serialisation format.)

The fix can be verified by trying a dapper upgrade from dapper->edgy with finish locales.

Confirming both that the update now works with the newest language packs, and that it also works with the proposed fix (with which the update would work regardless of translations used etc.).

http://librarian.launchpad.net/5767420/python-apt_0.6.16.2ubuntu9.debdiff needs to use version ubuntu8.1 because:

python-apt | 0.6.16.2ubuntu9 | edgy | all

(apparently an ASBA that was not cleaned up). But LP has a version record anyway, so we cannot use this version number any more.

What's the feisty status? Is the edgy fix for python-apt necessary as well?

http://librarian.launchpad.net/4937798/python-apt_0.6.19ubuntu9.1.debdiff needs to be uploaded to edgy-proposed, not edgy-updates.

http://librarian.launchpad.net/4937800/dist-upgrader-fix-68553.diff: The patch mangled white space: is the self.read = "" supposed to be in the except: block?

This problem needs to be fixed in both dapper and edgy. I added the according tasks. We could work around the problem in edgy by fixing it in the upgrader for edgy->feisty upgrades, but a regular fix would be much prefered.

This is fixed in the feisty version of the dist-upgrader (it will protect against ValueErrors from python-apt.

This is fixed in the edgy version of the update-manager already

It is enough if we have a fixed python-apt in dapper, the release-upgrader in dapper will work fine then.

http://librarian.launchpad.net/5933961/python-apt_0.6.16.2ubuntu8.1.debdiff approved for dapper-proposed.

http://librarian.launchpad.net/4937798/python-apt_0.6.19ubuntu9.1.debdiff approved for edgy-proposed, if you change s/edgy-updates/edgy-proposed/ in changelog.

 python-apt (0.6.16.2ubuntu8.1) dapper-proposed; urgency=low
 .
   * protect against not-parsable strings send from dpkg (lp: 68553)

accepted into dapper-proposed, please go ahead with QA testing.

 python-apt (0.6.19ubuntu9.1) edgy-proposed; urgency=low
 .
   * protect against not-parsable strings send from dpkg (lp: 68553)

Accepted into edgy-proposed, please go ahead with QA testing.

Should be verified for the dapper point release.

Here are the instructions for verfication:

* install fresh dapper
* use language-selector to install finish loclaes
* logout
* login with finish locales again
* run update-manager -c
* wait for the upgade to hang

Same steps as above, but after the installation of dapper, install python-apt from dapper-proposed and see the update continue.

I have tried to reproduce the crash 2 times using the 6.06.1 Desktop Edition VMware image and it has failed to reproduce the crash both times. I launched 'update-manager -c' in a terminal. I had python-apt version 06.16.2ubuntu8 and update-manager version 0.42.2ubuntu22.

I think the problem was also fixed in translations, so it doesn't show up anymore. I tested with the 2006-10-27 patch back then (my comment at 2006-10-28), and it fixed the problem back then. Ie. before it 6.06 -> 6.10 failed, with it it didn't. The patch from 2006-10-27 and the dapper-proposed patch 0.6.16.2ubuntu8.1 are identical.

Considering as verification-done after Timo's tests and Brian's successful test upgrades.

Copied to dapper-updates.

Copied to edgy-updates.