** Description changed: Binary package hint: canto Canto was obviously last built, when python-dev still pointed to python2.5-dev. The package should probably be installing its modules - under /usr/share/canto, since they are hardly used by something besides - Canto. But it installs them under /usr/python2.5/site-packages/canto as - public modules. Dunno, maybe a packaging error on part of Debian - maintainer. + under /usr/share/canto, since they are hardly used by something else + besides Canto. But it installs them under /usr/python2.5/site- + packages/canto as public modules. Dunno, maybe a packaging error on part + of Debian maintainer. But the net result of this is that /usr/bin/canto and /usr/bin/canto- fetch give ImportError on launch and don't start since python on Jaunty defaults to python2.6 For now, I'm forced to start canto like this: python2.5 /usr/bin/canto Simply rebuilding the package from source without any changes would hopefully fix that. Making a freeze exception and uploading a new version of canto from sid like described in LP bug #336082 would automatically fix this bug too.
** Description changed: Binary package hint: canto Canto was obviously last built, when python-dev still pointed to - python2.5-dev. The package should probably be installing its modules - under /usr/share/canto, since they are hardly used by something else - besides Canto. But it installs them under /usr/python2.5/site- - packages/canto as public modules. Dunno, maybe a packaging error on part - of Debian maintainer. + python2.5-dev. The package should probably install its modules under + /usr/share/canto, since they are hardly used by something else besides + Canto. But it installs them under /usr/python2.5/site-packages/canto as + public modules. Dunno, maybe a packaging error on part of Debian + maintainer. But the net result of this is that /usr/bin/canto and /usr/bin/canto- fetch give ImportError on launch and don't start since python on Jaunty defaults to python2.6 For now, I'm forced to start canto like this: python2.5 /usr/bin/canto Simply rebuilding the package from source without any changes would hopefully fix that. Making a freeze exception and uploading a new version of canto from sid like described in LP bug #336082 would automatically fix this bug too. ** Description changed: Binary package hint: canto Canto was obviously last built, when python-dev still pointed to - python2.5-dev. The package should probably install its modules under - /usr/share/canto, since they are hardly used by something else besides - Canto. But it installs them under /usr/python2.5/site-packages/canto as - public modules. Dunno, maybe a packaging error on part of Debian - maintainer. + python2.5-dev. The package installs its modules under /usr/python2.5 + /site-packages/canto - But the net result of this is that /usr/bin/canto and /usr/bin/canto- - fetch give ImportError on launch and don't start since python on Jaunty - defaults to python2.6 + But python on Jaunty defaults now to python2.6 + The net result of this is that /usr/bin/canto and /usr/bin/canto-fetch give ImportError on launch and don't start. For now, I'm forced to start canto like this: python2.5 /usr/bin/canto Simply rebuilding the package from source without any changes would hopefully fix that. Making a freeze exception and uploading a new version of canto from sid like described in LP bug #336082 would automatically fix this bug too. ** Description changed: Binary package hint: canto Canto was obviously last built, when python-dev still pointed to python2.5-dev. The package installs its modules under /usr/python2.5 - /site-packages/canto + /site-packages/canto, but python on Jaunty defaults now to python2.6. - But python on Jaunty defaults now to python2.6 + The net result of this is that /usr/bin/canto and /usr/bin/canto-fetch + give ImportError on launch and don't start. - The net result of this is that /usr/bin/canto and /usr/bin/canto-fetch give ImportError on launch and don't start. For now, I'm forced to start canto like this: python2.5 /usr/bin/canto Simply rebuilding the package from source without any changes would hopefully fix that. Making a freeze exception and uploading a new version of canto from sid like described in LP bug #336082 would automatically fix this bug too. ** Tags added: bitesize ** Description changed: Binary package hint: canto Canto was obviously last built, when python-dev still pointed to python2.5-dev. The package installs its modules under /usr/python2.5 /site-packages/canto, but python on Jaunty defaults now to python2.6. The net result of this is that /usr/bin/canto and /usr/bin/canto-fetch give ImportError on launch and don't start. For now, I'm forced to start canto like this: python2.5 /usr/bin/canto Simply rebuilding the package from source without any changes would hopefully fix that. Making a freeze exception and uploading a new version of canto from sid - like described in LP bug #336082 would automatically fix this bug too. + like requested in LP bug #336082 would automatically fix this bug too. -- Please rebuild canto https://bugs.launchpad.net/bugs/342504 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
