[Bug 353251] Re: rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

2010-02-01 Thread Matthias Klose
won't fix for python2.4 ** Changed in: python2.4 (Ubuntu Jaunty) Status: New = Won't Fix ** Changed in: python2.4 (Ubuntu) Status: New = Won't Fix -- rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade https://bugs.launchpad.net/bugs/353251 You

[Bug 353251] Re: rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

2009-12-05 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/python2.6 -- rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade https://bugs.launchpad.net/bugs/353251 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 353251] Re: rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

2009-11-16 Thread kertib
how do i fix it? -- rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade https://bugs.launchpad.net/bugs/353251 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 353251] Re: rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

2009-08-21 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/karmic/python3.0 -- rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade https://bugs.launchpad.net/bugs/353251 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 353251] Re: rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

2009-04-16 Thread Michael Vogt
Closing the 2.5 task, that should be fine (its marked supported in both hardy and intrepid). ** Changed in: python2.5 (Ubuntu Jaunty) Status: New = Fix Released -- rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

[Bug 353251] Re: rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

2009-04-16 Thread Michael Vogt
I just ran into a interessting variant of this bug. It seems to be important in what order the packages get installed for them to be byte- compiled (done on a current jaunty chroot): [chroot1] # apt-get install python-distutils-extra # apt-get install python2.4 # ls

[Bug 353251] Re: rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

2009-04-16 Thread Michael Vogt
** Also affects: python2.4 (Ubuntu) Importance: Undecided Status: New ** Also affects: python2.5 (Ubuntu) Importance: Undecided Status: New -- rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade https://bugs.launchpad.net/bugs/353251 You

[Bug 353251] Re: rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

2009-04-03 Thread Max Bowsher
The fix is wrong because it doesn't consider the case the the relevant runtime not being contained in *any* category in /usr/share/python/debian_defaults. Before: supported-versions was used as a whitelist After: unsupported-versions is used as a blacklist The current behaviour of python-central

[Bug 353251] Re: rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

2009-04-03 Thread Heitzso
I have a tangled system due to this bug. I tried to upgrade from intrepid from console using aptitude dist-upgrade and the upgrade is severely (?) hung. I would appreciate a fix for those of us with hung/broken systems, i.e. what sequence of commands will get python2.6 working so all of the

[Bug 353251] Re: rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

2009-04-03 Thread Max Bowsher
Un-reopening, fixed by bug 354228. ** Changed in: python3.0 (Ubuntu Jaunty) Status: In Progress = Fix Released -- rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade https://bugs.launchpad.net/bugs/353251 You received this bug notification because you

[Bug 353251] Re: rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

2009-04-02 Thread Launchpad Bug Tracker
This bug was fixed in the package python3.0 - 3.0.1-0ubuntu10 --- python3.0 (3.0.1-0ubuntu10) jaunty; urgency=low [Matthias Klose] * Update to 20090402 from the release30-maint branch. * Address issues when working with PYTHONUSERBASE and non standard prefix (pointed out by

[Bug 353251] Re: rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

2009-04-02 Thread Anders Kaseorg
This fix seems to have caused the regression in bug 354251 (python3.0) and bug 354228 (python2.6). -- rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade https://bugs.launchpad.net/bugs/353251 You received this bug notification because you are a member of

[Bug 353251] Re: rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

2009-04-02 Thread Michael Vogt
** Summary changed: - does not provide 2.6 symlinks for python-fstab (and others?) when python2.6 gets installed + rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade -- rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

[Bug 353251] Re: rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

2009-04-02 Thread Matthias Klose
** Package changed: python-central (Ubuntu Jaunty) = python2.6 (Ubuntu Jaunty) ** Also affects: python3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: python3.0 (Ubuntu Jaunty) Importance: Undecided = High ** Changed in: python3.0 (Ubuntu Jaunty) Status: New =

[Bug 353251] Re: rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid-jaunty upgrade

2009-04-02 Thread Launchpad Bug Tracker
This bug was fixed in the package python2.6 - 2.6.1-1ubuntu8 --- python2.6 (2.6.1-1ubuntu8) jaunty; urgency=low [Matthias Klose] * Update to 20090402, taken from the 2.6 release branch. - Fix issues #2625, #5068, #5387, #5536, #5561, #5619, #5632. * Address issues when