notes on getting this release-noted, from IRC:
17:30 < ScottK> The issue was the upgrade of the package happening before
python2.6 had turned into a supported version, so the module didn't get
symlinked for 2.6.
17:31 < ScottK> I suspect (but cannot prove) that an indeterminate number of
people who upgraded before the fix have an indeterminate number of broken
python packages.
17:32 < ScottK> Caveated to people who upgraded before RC.
17:34 < slangasek> should dpkg-reconfigure do the job? (calls the postinst,
saves a download)
17:36 < ScottK> I'm not sure. Most of the symlink magic is done in postinst,
so it should.
17:37 < ScottK> The thing to key off of is "ImportError: No module named Pmw"
so in the release note we can say if the error is "ImportError: No module named
foo" then reconfigure/reinstall python-foo.
17:37 < ScottK> Dunno if that's too complex or not, but it may save us some
bugs and users some frustrations.
17:38 < ScottK> Given that the problem should be limited to people that
upgraded pre-RC they should in theory be able to deal with it.
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in: ubuntu-release-notes
Importance: Undecided => Medium
** Changed in: ubuntu-release-notes
Status: New => Triaged
--
pymol menu bar does not show up after upgrade to jaunty
https://bugs.launchpad.net/bugs/364608
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
