UnicodeDecodeError in checkFreeSpace on 13.10=>14.04 upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Steps:
1. Use a locale that has an LC_NUMBER with a no-breaking space (or some other non-ascii character)
2. Have too little space on one mount (for me it was /boot)
3. Can't do release upgrade to 14.04 (well, not getting any error message)
I sent a patch upstream[0], but I don't know if it'll be accepted, and also, this won't really help unless the package is updated on the versions people upgrade from.
[0] <https:/
I suggest instead that you code around it in the trusty upgrade script. The offending line is the apt_pkg.
I don't know where the code for that trusty tarball is held, so I don't have a patch. But I can do that if you tell me where. (should be a simple fix though).
-------
Some relevant log lines (and traceback) from this discussion <http://
2014-04-18 08:44:07,527 DEBUG dir '/var/cache/
2014-04-18 08:44:07,527 DEBUG dir '/usr' needs '1768633344' of '<DistUpgrade.
2014-04-18 08:44:07,528 DEBUG dir '/usr' needs '52428800' of '<DistUpgrade.
2014-04-18 08:44:07,528 DEBUG dir '/boot' needs '47136438' of '<DistUpgrade.
2014-04-18 08:44:07,528 DEBUG dir '/tmp' needs '5242880' of '<DistUpgrade.
2014-04-18 08:44:07,529 DEBUG dir '/' needs '10485760' of '<DistUpgrade.
2014-04-18 08:44:07,529 DEBUG dir '/tmp' needs '0.0' of '<DistUpgrade.
2014-04-18 08:44:07,529 DEBUG dir '/usr' needs '0.0' of '<DistUpgrade.
2014-04-18 08:44:07,530 ERROR Not enough free space: ['/']
2014-04-18 08:44:07,543 ERROR not handled exception:
Traceback (most recent call last):
File "/tmp/update-
sys.
File "/tmp/update-
if app.run():
File "/tmp/update-
return self.fullUpgrade()
File "/tmp/update-
if not self.askDistUpg
File "/tmp/update-
if not self._checkFree
File "/tmp/update-
required.dir))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 1: ordinal not in range(128)
tags: | added: dist-upgrade |
Oh this may be the same bug as bug 1172740.