How to: Upgrading compiz-fusion on the 08/08/2007

Compiz, KDE, Gnome, Fluxbox, etc...

Moderator: Moderators

How to: Upgrading compiz-fusion on the 08/08/2007

Postby dave_p_b » Wed Aug 08, 2007 12:43

Hi

I'm writing this update procedure as several ebuilds and dependancies have changed in the past week for compiz-fusion so the current ebuilds are likely to fail.

Note: please only do this if you know what you are doing. This only accounts for updating compiz-fusion upto todays date. If they change further ebuilds or dependancies then this guide will probably not work.


We will start by opening up konqueror as root. It's in kmenu->system->More Applications->File Manager - Super User Mode.

The first ebuild to change is the ccsm-9999.ebuild.


1) In Konqueror, navigate to /usr/portage/local/layman/sabayon/x11-apps/ccsm/
2) Double click on the file ccsm-9999.ebuild.
3) You need to delete the part, near the bottom of the page like this:

src_compile() {
cd ${S}
./autogen.sh || die "autogen failed"

econf || die "econf failed"
emake || die "make failed"
}

src_install() {
make DESTDIR="${D}" install || die "make install failed"
}




The new code (near the bottom of the page) should look like this:

src_compile() {
cd ${S}
./setup.py build --prefix=/usr
}

src_install() {
./setup.py install --root=${D} --prefix=/usr
}


4) After you have saved then open up a root konsole in the /usr/portage/local/layman/sabayon/x11-apps/ccsm/ directory and type "ebuild ccsm-9999.ebuild digest" (without quotes)


The second ebuild that needs changing is compiz-9999.ebuild.

This is a similar process to the last one.

1) In Konqueror, navigate to /usr/portage/local/layman/sabayon/x11-wm/compiz/
2) Double click on the file compiz-9999.ebuild.
3) You need to edit the part, near the middle of the page like this:

pkg_setup() {
if ! use gtk && use gnome ; then
eerror "USE=\"gnome\" requires USE=\"gtk\""
eerror "Please build with USE=\"gnome gtk\""
die "Build with USE=\"gnome gtk\""
fi
}



So that it reads like this:

pkg_setup() {
if ! use gtk && use gnome ; then
eerror "USE=\"gnome\" requires USE=\"gtk\""
eerror "Please build with USE=\"gnome gtk\""
die "Build with USE=\"gnome gtk\""
fi
if ! built_with_use "x11-libs/libX11" "xcb" ; then
eerror "Compiz now requires libX11 to be built with xcb."
eerror "Please build libX11 with USE=\"xcb\""
die "Build libX11 with USE=\"xcb\""
fi
}



4) After you have saved then open up a root konsole in the /usr/portage/local/layman/sabayon/x11-wm/compiz/ directory and type "ebuild compiz-9999.ebuild digest" (without quotes)


Now, we have to deal with some new dependanices.


For compiz-9999 to build correctly, we need to install libx11-xcb into your system. This is done by doing the following:

1) Open up a root konsole.

2) type USE="xcb" emerge =libX11-1.1.1-r1 (Note: This is assuming you haven't upgraded your libx11 package since the release of SL 3.4a. If you have then just change the version number to reflect the change)

3) Change back to the kwin window manager and close down fusion-icon.

4) Uninstall everything related to compiz-fusion by typing the following into a root konsole.

emerge -C x11-libs/bcop x11-apps/ccsm x11-wm/compiz x11-libs/compiz-bcop x11-libs/compizconfig-backend-gconf x11-libs/compizconfig-backend-kconfig dev-python/compizconfig-python x11-wm/compiz-fusion x11-plugins/compiz-fusion-plugins-extra x11-plugins/compiz-fusion-plugins-main x11-plugins/compiz-fusion-plugins-threed x11-plugins/compiz-fusion-plugins-unsupported x11-apps/compiz-settings x11-apps/fusion-icon x11-libs/libcompizconfig

5) Now, just to be on the safe side, in your root Konqueror session go to the folder /usr/portage/distfiles/git-src/ and delete everything from there.

6) Now, installing everything to do with compiz by typing the following into a root konsole.

emerge x11-libs/bcop x11-apps/ccsm x11-wm/compiz x11-libs/compiz-bcop x11-libs/compizconfig-backend-gconf x11-libs/compizconfig-backend-kconfig dev-python/compizconfig-python x11-wm/compiz-fusion x11-plugins/compiz-fusion-plugins-extra x11-plugins/compiz-fusion-plugins-main x11-plugins/compiz-fusion-plugins-threed x11-plugins/compiz-fusion-plugins-unsupported x11-apps/compiz-settings x11-apps/fusion-icon x11-libs/libcompizconfig

7) Next, goto kmenu->System and click on Compiz-fusion icon and change back to the Compiz window manager.


I hope I haven't made any mistakes in here and all goes well for you. If you follow line by line then it should work. I hope :)

All the best

Dave
User avatar
dave_p_b
Old Dear Hen
 
Posts: 607
Joined: Fri Dec 15, 2006 1:39
Location: Exeter, UK

Postby wolfden » Wed Aug 08, 2007 18:10

Which overlay are you using?

one wouldn't have to cd the directories to digest - just issue as root:

Code: Select all
ebuild /usr/portage/local/layman/sabayon/x11-apps/ccsm/ccsm-9999.ebuild digest


Code: Select all
ebuild /usr/portage/local/layman/sabayon/x11-wm/compiz/compiz-9999.ebuild digest


I also did

Code: Select all
echo "x11-libs/libX11 xcb" >> /etc/portage/package.use


to delete the git-src stuff:

Code: Select all
rm -rf /usr/portage/distfiles/git-src/*


little bit more noob friendly
User avatar
wolfden
Sharecropper
 
Posts: 8822
Joined: Sat Jan 14, 2006 0:55
Location: Midwest USA

Postby dave_p_b » Wed Aug 08, 2007 22:00

Hi Wolfden

Just using the normal Sabayon overlay. I'm pinching the ebuild changes from the xeffects overlay though as those ebuilds seem more up to date.

Really the devs should update the Compiz-fusion ebuilds in the Sabayon overlay as they appear to make it almost impossible to upgrade compiz-fusion with the present ebuilds.

Even though xcb has now been introduced into compiz, for 64-bit users (and maybe 32-bit users) it creates java problems. So for us 64-bit users that use blackdown-jdk 1.4, it causes Firefox to crash when one navigates to a page that contains a Java applet.

I've temporarily fixed mine to work but from what I've read, its upto Java to fix it's packages. I'm hoping that Java 7 will be 64-bit friendly as I think this version contains an xcb error fix.

I would write down the temp fix but it is long and includes patching the libxcb source code prior to compiling. I think I'll wait to see if any one runs into problems.

All the best

Dave

p.s. The new xcb may throw errors for some more old programs. From what I can work out the xcb errors are not faults with the actual xcb program itself. Rather the programs that are using xcb have poorly written code that forces xcb to throw these errors.

Here is an example of the error that occurs when Firefox crashes when navigating to a page with a Java applet.

java_vm: xcb_xlib.c:52: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
INTERNAL ERROR on Browser End: Could not read ack from child process
System error?:: Resource temporarily unavailable
firefox-bin exited with non-zero status (255)
User avatar
dave_p_b
Old Dear Hen
 
Posts: 607
Joined: Fri Dec 15, 2006 1:39
Location: Exeter, UK

Postby tpcforever » Wed Aug 08, 2007 23:26

A the end, when emerge, I have this message :
uild with USE="gnome gtk

But I m under KDE

What I ve to do ?
tpcforever
Baby Hen
 
Posts: 10
Joined: Mon Jun 25, 2007 13:12

Postby dave_p_b » Wed Aug 08, 2007 23:32

Hi

Could you post more of the message. I doesn't make much sense.
What type of message is it? Is it an error message?

The compiz ebuilds should be set up to favour KDE if that is all you installed on your system. If you installed KDE and Gnome then compiz will be built with both in mind.


Thanks

Dave
User avatar
dave_p_b
Old Dear Hen
 
Posts: 607
Joined: Fri Dec 15, 2006 1:39
Location: Exeter, UK

Postby Lamo » Thu Aug 09, 2007 4:21

I followed everything to the letter and all seemed well up until I went to emerge compiz. I'm getting this error:

Code: Select all
* Messages for package x11-wm/compiz-9999:

 *
 * ERROR: x11-wm/compiz-9999 failed.
 * Call stack:
 *   ebuild.sh, line 1648:   Called dyn_unpack
 *   ebuild.sh, line 768:   Called qa_call 'src_unpack'
 *   ebuild.sh, line 44:   Called src_unpack
 *   ebuild.sh, line 1328:   Called git_src_unpack
 *   git.eclass, line 280:   Called git_fetch
 *   git.eclass, line 195:   Called die
 *
 * git.eclass: can't fetch from git://anongit.freedesktop.org/git/xorg/app/compiz.
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/x11-wm/compiz-9999/temp/build.log'.


Is the server just down? Thanks. :)
Lamo
Young Hen
 
Posts: 29
Joined: Thu Aug 09, 2007 4:17

Postby Lamo » Thu Aug 09, 2007 22:58

So I guess it has to do with the firewall I'm behind. Anyone know of another way to upgrade cause I have no access to my firewall right now. I tried emerge-webrsync but i get this error:

Code: Select all
Fetching most recent snapshot
Attempting to fetch file dated: 20070808
portage-20070808.tar.bz2: FAILED
md5sum: WARNING: 1 of 1 computed checksum did NOT match


Any clues? Thanks.
Lamo
Young Hen
 
Posts: 29
Joined: Thu Aug 09, 2007 4:17

Postby BRi7X » Thu Aug 16, 2007 11:09

Okay, so I followed the whole set of instructions in the first post... I've gotten to the point where it's time to reinstall all the compiz crap...
However... I get this staring me in the face:
Laptop7X ccsm # emerge x11-libs/bcop x11-apps/ccsm x11-wm/compiz x11-libs/compiz-bcop x11-libs/compizconfig-backend-gconf x11-libs/compizconfig-backend-kconfig dev-python/compizconfig-python x11-wm/compiz-fusion x11-plugins/compiz-fusion-plugins-extra x11-plugins/compiz-fusion-plugins-main x11-plugins/compiz-fusion-plugins-threed x11-plugins/compiz-fusion-plugins-unsupported x11-apps/compiz-settings x11-apps/fusion-icon x11-libs/libcompizconfig
Calculating dependencies |
!!! All ebuilds that could satisfy "x11-libs/bcop" have been masked.
!!! One of the following masked packages is required to complete your request:
- x11-libs/bcop-9999 (masked by: missing keyword)

It tells me to consult the man page... but since I was following directions from here, I figured I'd post it here...
Any suggestions? Thank you!
BRi7X
Baby Hen
 
Posts: 12
Joined: Thu Aug 16, 2007 9:57
Location: Aldan, PA, USA

Postby dave_p_b » Thu Aug 16, 2007 11:15

Hi

You must be using an old version of SabayonLinux as version 3.4 doesn't have this issue. Anyway, the entries I list below should be in your /etc/portage/package.keywords file (which you have to edit as root).

dev-python/compizconfig-python **
x11-apps/ccsm **
x11-apps/fusion-icon **
x11-libs/bcop **
x11-libs/compiz-bcop **
x11-libs/compizconfig-backend-gconf **
x11-libs/compizconfig-backend-kconfig **
x11-libs/libcompizconfig **
x11-plugins/compiz-fusion-plugins-atlantis **
x11-plugins/compiz-fusion-plugins-extra **
x11-plugins/compiz-fusion-plugins-main **
x11-plugins/compiz-fusion-plugins-threed **
x11-plugins/compiz-fusion-plugins-unsupported **
x11-plugins/compiz-users-pafy-screensaver **
x11-themes/emerald-themes **
x11-wm/compiz **
x11-wm/compiz-fusion **
x11-wm/emerald **


All the best

Dave
User avatar
dave_p_b
Old Dear Hen
 
Posts: 607
Joined: Fri Dec 15, 2006 1:39
Location: Exeter, UK

Postby BRi7X » Thu Aug 16, 2007 11:36

Hello...

This is what it's spitting out at me now, similar to that of Lamo's post.:

*
* ERROR: x11-wm/compiz-9999 failed.
* Call stack:
* ebuild.sh, line 1654: Called dyn_compile
* ebuild.sh, line 990: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* compiz-9999.ebuild, line 73: Called die
*
* make failed
* If you need support, post the topmost build error, and the call stack if rele vant.
* A complete build log is located at '/var/tmp/portage/x11-wm/compiz-9999/temp/ build.log'.
*



There's a whole slew of errors previous to that, I wasn't sure if I should have pasted them since it's quite lengthy, but that's the error at the end. It's pretty similar to Lamo's.

Any more suggestions?
Thanks!
BRi7X
Baby Hen
 
Posts: 12
Joined: Thu Aug 16, 2007 9:57
Location: Aldan, PA, USA

Next

Return to 3D Desktops and Window Managers

Who is online

Users browsing this forum: No registered users and 0 guests