Bug 5195 – emerge gnome fails on XFS, not on ext3 (1.3b)

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Lex 2002-07-18 07:54:47 UTC]

I did an install on ext3 of 1.3b and emerged Gnome flawlessly.

Later I decided to change my partition setup, and partition type (now XFS)
I installed 1.3b twice on XFS.

-first time emerge gnome broke on gnome-session and gedit.
(didn't finish the emerge).

-second time ermerge gnome broke on ORBit2 (just emerged ORBit2 solely and then 
continued to emerge gnome), and later on gnome-session. gnome-session emerge 
failed because of gconf. Then I emerged gconf; now gnome-session succeeded.
The rest of emerge gnome went without troubles.

(portage was 2.0.13 (2.13?)

Strange because on ext3 things went without hickups.


Another point; When I had still a partition with 1.2 (XFS), I emerged gcc3, and 
emerged system, several hickups then too. Manually finished this emerge.


system specs:
maxtor 20g hdd (740dx)
athlon tbird 1000
512 mb sdram
msi kt7a mb

[Comment 1 Spider (RETIRED) 2002-07-18 08:55:00 UTC]

strange... 
do you use XFS acl support? there was a report about the acl causing a warning
to be output on cp, mv and rm, thus breaking the install scripts... could this
be it??

Other reasons, I'm stumped here, and I dont think I'll be able to debug this
since I have no hardware to run XFS on.

[Comment 2 Andreas Kotowicz 2002-07-18 15:11:59 UTC]

this is actually this bug http://bugs.gentoo.org/show_bug.cgi?id=5098. something
seems to thave changed in gconf-ebuild so it doesn't install
gconf-sanity-check-2 which makes gnome-session fail. just unmerge gconf and
emerge gconf again. then continue your emerge gnome. will work

[Comment 3 Spider (RETIRED) 2002-07-18 15:27:28 UTC]

okay, I'm in the process of testing a new gconf release that will fix this issue.