py-2.7 will break vbox

[SlowJet]

bummer.

SJ

[sej7278]

nice brief, care to elaborate?

[tox]

nice brief, care to elaborate?

in essence F14 wont probably work in vbox due to the breakage

[sej7278]

in essence F14 wont probably work in vbox due to the breakage

IN virtualbox - you mean as a guest?

that doesn't bother me much, but if f14 won't work as a host i'm sticking with f13 until oracle fix it!

this doesn't seem to have been discussed on the vbox forums, is it on a vbox maillinglist somewhere? do oracle even know? links.....

what in python 2.7 is going to break vbox, and is it just the additions or api, or is it virtualbox itself that will not work?

i noticed that the java xpcom in virtualbox doesn't compile on f13 (and ubuntu etc) as of this week - it requires the *sun* jdk, openjdk/gcj don't work.

[SlowJet]

VBOX rpm's from sun version use 2.6 and therfore will not run on the Fedora 14 host using 2.7.
It is not unusual for the devl kerenl to stop working on virtual box until the next virtualbox release adjusts to the new finished kerenl.
But with python 2.7 it may be a long dry spell until other distro adopt python 2.7.
(but we could hope that Sun will compile the Fedora 14 rpm with kernel 36 and python 2.7 later this year. If not, ...it may be several months until ti works again.)

(The expanning univere of Linux needs a new 5 year plan. :)

SJ

[tox]

VBOX rpm's from sun version use 2.6 and therfore will not run on the Fedora 14 host using 2.7.
It is not unusual for the devl kerenl to stop working on virtual box until the next virtualbox release adjusts to the new finished kerenl.
But with python 2.7 it may be a long dry spell until other distro adopt python 2.7.
(but we could hope that Sun will compile the Fedora 14 rpm with kernel 36 and python 2.7 later this year. If not, ...it may be several months until ti works again.)

(The expanning univere of Linux needs a new 5 year plan. :)

SJ

i think Ubuntu are gonna go with Python-2.7 in there 10.10 release

[sej7278]

ok thanks for the explanation.

so we either convince ubuntu to go 2.7 (in which case oracle will probably switch too, being the two biggest linux vendors) or we start compling OSE ourselves and lose a bit of functionality.

seems my issue with building OSE with openjdk is a known issue, it basically now REQUIRES the sun jdk (yeah the broken one with the oracle rebranding!)

http://vbox.innotek.de/pipermail/vbox-dev/2010-July/003026.html

looks like oracle being a bit heavy-handed with the rebranding is breaking a lot of their kit, also seems that they've stopped supporting solaris x86_64 sold through oem vendors like ibm.

[leigh123linux]

VBOX rpm's from sun version use 2.6 and therfore will not run on the Fedora 14 host using 2.7.
It is not unusual for the devl kerenl to stop working on virtual box until the next virtualbox release adjusts to the new finished kerenl.
But with python 2.7 it may be a long dry spell until other distro adopt python 2.7.
(but we could hope that Sun will compile the Fedora 14 rpm with kernel 36 and python 2.7 later this year. If not, ...it may be several months until ti works again.)

(The expanning univere of Linux needs a new 5 year plan. :)

SJ


Bull!, python packages built for 2.6 will run on 2.7, python is backward compatible.
You are moaning about the rpm dep which doesn't matter.

http://forums.fedoraforum.org/attachment.php?attachmentid=19904&stc=1&d=1280415915

[hephasteus]

Gonna agree with leigh. Python is serious backward forward upward downward compatibility. We've already done two of these python things when they went from 2.4 to 2.5 and then 2.5 to 2.6 so it's not going to be uneventful based on past experiences. And it's going to suck being a fedora server because it's going to take a mass rebuild though they are likely already getting started on it. Call the power company because they are going to have 100 percent cpu usage for at least 2 months.

[sej7278]

its a good point, its only likely to be rpm's that will not work due to dependency hell.

so we either compile our own from OSE, or use the binary builds from Oracle, or hope they rebuild the RPM's, which i expect they will do, they did for fedora 9-13.

edit: i fixed the compilation problem, its because the compiler can't find jni.h symlinking /usr/lib/jvm/java-1.6.0-openjdk.x86_64 to java-6-openjdk fixes it (alternatives doesn't work).