This bug was fixed in the package lxc - 0.9.0~rc1-0ubuntu2
---
lxc (0.9.0~rc1-0ubuntu2) raring; urgency=low
* Fix python3-lxc on armhf (LP: #1159817).
-- Stephane GraberTue, 26 Mar 2013 11:21:46 -0400
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159817
Title:
python module lxc failed to import on ARM with: UnicodeDecodeError:
Reproducing was easy, understanding the problem wasn't ;)
Anyway, I figured it out and sent a patch upstream for inclusion in the final
0.9.
Once it's accepted upstream (hopefully in a few minutes), I'll push it to
Ubuntu.
--
You received this bug notification because you are a member of Ubunt
BTW if you don't have a board to reproduce this issue, it is also reproducible
in an armhf container created with:
$ sudo lxc-create -n raring-arm -t ubuntu -- -r raring -a armhf
then install python3-lxc into this container
--
You received this bug notification because you are a member of Ubunt
** Changed in: lxc (Ubuntu)
Status: New => Triaged
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159817
Title:
python module lxc
I'm currently going on the assumption that we simply got a corrupted
binary out of the armhf buildd. I'm doing a local rebuild to confirm and
if that's the case, will simply push a no-change rebuild.
This assumption is based on the fact that the same python module works
on other architectures and
My first guess was some utf-8 problems with the python module "lxc", but
it actually looks like it's the binary module that's the problem:
root@delmak:~# python3 -c "import _lxc"
Traceback (most recent call last):
File "", line 1, in
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb5 in p
