4.0 Branch

[joost]

kdeprefix Makes a KDE prefixed install into /usr/kde/$ if enabled or into /usr (FHS compatible) otherwise

http://www.nabble.com/kdeprefix-use-fla ... 72549.html
http://www.pathname.com/fhs/pub/fhs-2.3.html

Its not really a portage compatible issue, but more a inter-linux compatible issue IMHO.

[Fitzcarraldo]

Things reported in bugzilla are addressed in general.
Its not a specific sabayon 4 (Entropy) branch thing.

I'm pretty sure that after we have our first Loop pushed out we will have solved any critical stuff.
You ask for a number of resolved issues. Well that would be kinda impossible for me to answer. All I know is that, since you ask me, I fix whatever dev team asks me to fix in the branch.

Can't do more then that.

//edit
Looking through them allot of things in there are invalid or even outdated.. Needs to be cleaned up.

I agree, but I think some of them could still be relevant (I'm not just thinking of Entropy-related bug reports, either). Can I ask you to pass the request on to Fabio? Thanks.

[eshum]

After reading this thread I decided to give the 4.0 branch a tryout. First I must say I was impressed with what I was able to see and use. My problem with the 4.0 branch was this if I did not reboot everything worked that I tried out. When I rebooted the the desktop overlay would decompose diagonally top left to bottom right leaving a white screen. however as I peered at the screen I moved the scroll wheel and the cube rotated okay so I tried ctrl-alt-left mouse button and move the cube all over the place. So I dropped down to the comand line and poked around enough to find it is a module error problem ( a nvidia driver conflict with driver 173.14.12 &177.whatever). So the cube is there and working without a kde desktop showing. I liked what i saw and will wait for this branch to mature so more and try it again keep up the good work.

ed

[sjieke]

@ eshum: Did you check the opengl settings. A had a similar behaviour, kdm came up right, but after login a had a white screen with a mousepointer. Move the mouse around showed me some black rectangles. When I looked into the opengl setting I saw it was set to xorg instead of nvidia. Setting it back to nvidia and restarting X resolved the issue for me, but I'm still using the 2.6.26 kernel...

@ joost: I saw that the xine backend for phonon still has dependencies on arts (maybe not directly, but installing it pulls in arts again after removing arts and all its dependencies). Is this going to change or will arts always be needed?

[eshum]

I was using 2.6.27 kernel. I did take one look at the 2.6.26 kernel with the same module error. I was just really curious about how 4.0 was looking I was satisfied it will be great when it is done. Probably take another look at loop 1 or 2. I am retired so when I get bored I get adventurous and go looking for whats new. Last week I downloaded MACPUP just to have look see nice little operating system.

ed

[dkasak]

I don't want to dampen the mood here, but I have had faaaarkiiing massive system breakage on the 4.0 branch. What's more, I think there are a number of bugs all working at once here. To start with, I had a 'working' 4.0 system ( after some minor system breakage when updating from 3.5 ). Then I did an 'equo --verbose world'.

Wow. Hundreds of broken packages, including syslog-ng, X, all gnome libraries ... the list goes on. Luckily I'm a seasoned Gentoo user and I'm used to this shit! I ended up running 'revdep-rebuild' ( without letting it actually build and install anything ), looking out for missing libraries ( which mysteriously got removed during the update ), and installing them via equo. That fixed some stuff ... enough to start X anyway. Then I ran revdep-rebuild again and watched for broken libraries, logged into my server ( running Gentoo ), did a 'equery belongs /path/to/library.so', figured out what package it belongs to, and re-installed it, either via equo or emerge. Now this last bit shouldn't have happened ... ie I shouldn't have to go to another Gentoo box to find out what package a broken library belongs to ... but something was seriously out of whack between entropy, portage, and what's actually happening on my system.

Now I'm doing a 'emerge -ev world', because things still aren't exactly perfect. Having said that, I didn't have any issues with the 3.5 branch. But a word of warning for people curious ( and there will be more of these now that the website is advertising the upcoming release in a splashy way ) ... beware. Things break, and break badly. The worst of this breakage is entropy / portage not knowing what's installed. That's critical.

[DHalens]

@ dkasak:
Personally, I use sabayon 4 as my main and only OS and is enough stable considering its bleeding edge so I'm stranged about your issues.
Did you try equo deptest and equo libtest? Was equo and entropy fully updated? You used a clean home folder (specially kde4 may fail if you use previous kde configs)?

[sbdsr]

That's interesting I updated as well and didn't have a lot of breakage...very little actually...and definitely fixable without a lot of effort...different strokes for different folks I guess...

[dkasak]

DHalens: Yes I tried 'equo deptest' and 'equo libtest' before embarking on manually rebuilding stuff. 'equo deptest' fixed some stuff - not a lot at all. 'equo libtest' just dropped straight back to the console as soon as I ran it, but would leave a PID in /var/lib/entropy or something ... which I had to delete before I could use equo / spritz again. And yes, equo and entropy where completely up-to-date before I did anything.

[joost]

We are close to the first iso builds. These first loops will be spread under Core testers to test the upgrade process, hardwarer support, breakage, etc etc.
After this there will be a public testing version. (hopefully within 2 weeks)

@by dkasak on Mon Dec 08, 2008 03:15
No need to report anything about the branch in testing state as it changes all the time.

Further more, reporting stuff without enough info/logs doesn't help at all. A "Gentoo user" should know that.

Wow. Hundreds of broken packages, including syslog-ng, X, all gnome libraries

And you never doubted like: geez maybe i did something wrong?