| View previous topic :: View next topic |
| Author |
Message |
jmbsvicetto
Moderator
Joined: 27 Apr 2005
Posts: 4734
Location: Angra do Heroísmo (PT)
|
 Posted: Tue Oct 21, 2008 12:07 pm Post subject: |
 |
|
| platojones wrote: | | billydv wrote: | | I had same problem yesterday with live ebuilds but the keyworded ebuilds do emerge. I would just emerge the keyworded ones for now, I saw no real difference. |
I can confirm that....I just switched from the live ebuilds to the 7.8 ebuilds...no issues and works great! |
All of the intltool/gettext issues revealed by the updated intltool should be fixed now.
_________________
Jorge.
Your twisted, but hopefully friendly daemon.
AMD64 / x86 / Sparc Gentoo
Help answer || emwrap.sh
|
|
| Back to top |
|
 |
overkll
Veteran
Joined: 21 Sep 2004
Posts: 1249
Location: Austin, Texas
|
| Posted: Sat Oct 25, 2008 5:30 pm Post subject: |
|
|
I'm using compiz-fusion-0.7.6 and just ran `emerge --sync` and `emerge -uDNpv` and I get an overlay eclass warning:
| Code: | * Overlay eclass overrides eclass from PORTDIR:
*
* '/usr/portage/local/layman/desktop-effects/eclass/bzr.eclass'
*
* It is best to avoid overridding eclasses from PORTDIR because it will
* trigger invalidation of cached ebuild metadata that is distributed with
* the portage tree. If you must override eclasses from PORTDIR then you
* are advised to run `emerge --regen` after each time that you run `emerge
* --sync`. Set PORTAGE_ECLASS_WARNING_ENABLE="0" in /etc/make.conf if you
* would like to disable this warning. |
This is the first time I've ever seen this warning. Looks like the bzr.eclass file was updated in the portage tree. Should the bzr.eclass file in the desktop-overlay be updated as well?
I ran `layman -S` but the warning/error remains. |
|
| Back to top |
|
|
jmbsvicetto
Moderator
Joined: 27 Apr 2005
Posts: 4734
Location: Angra do Heroísmo (PT)
|
| Posted: Sun Oct 26, 2008 3:10 pm Post subject: |
|
|
| overkll wrote: | I'm using compiz-fusion-0.7.6 and just ran `emerge --sync` and `emerge -uDNpv` and I get an overlay eclass warning:
| Code: | * Overlay eclass overrides eclass from PORTDIR:
*
* '/usr/portage/local/layman/desktop-effects/eclass/bzr.eclass'
*
* It is best to avoid overridding eclasses from PORTDIR because it will
* trigger invalidation of cached ebuild metadata that is distributed with
* the portage tree. If you must override eclasses from PORTDIR then you
* are advised to run `emerge --regen` after each time that you run `emerge
* --sync`. Set PORTAGE_ECLASS_WARNING_ENABLE="0" in /etc/make.conf if you
* would like to disable this warning. |
This is the first time I've ever seen this warning. Looks like the bzr.eclass file was updated in the portage tree. Should the bzr.eclass file in the desktop-overlay be updated as well?
I ran `layman -S` but the warning/error remains. |
The bzr.eclass was added yesterday to the tree. I've removed it from the overlay.
_________________
Jorge.
Your twisted, but hopefully friendly daemon.
AMD64 / x86 / Sparc Gentoo
Help answer || emwrap.sh
|
|
| Back to top |
|
|
albright
Advocate
Joined: 16 Nov 2003
Posts: 2588
Location: Near Toronto
|
| Posted: Sun Oct 26, 2008 4:00 pm Post subject: |
|
|
| Quote: | | The bzr.eclass was added yesterday to the tree. I've removed it from the overlay. |
thanks!
_________________
.... there is nothing - absolutely nothing - half so much worth
doing as simply messing about with Linux ...
(apologies to Kenneth Graeme) |
|
| Back to top |
|
|
overkll
Veteran
Joined: 21 Sep 2004
Posts: 1249
Location: Austin, Texas
|
| Posted: Sun Oct 26, 2008 10:40 pm Post subject: |
|
|
| That fixed it. Thanks jmbsvicetto. |
|
| Back to top |
|
|
ipic
Guru
Joined: 29 Dec 2003
Posts: 377
Location: UK
|
| Posted: Mon Oct 27, 2008 11:02 pm Post subject: |
|
|
I've been using compiz-fusion 0.7.8 since it was introduced into the overlay, and its been good - for me at least.
Today, after updating layman and portage, I get this from eix:
| Code: | [D] x11-wm/compiz-fusion
Available versions: (~)0.6.0 (~)0.7.6[1] [M](~)0.7.8[1] **9999[1] {gnome kde unsupported}
Installed versions: 0.7.8[1](18:11:54 29/09/08)(gnome kde -unsupported)
Homepage: http://compiz-fusion.org
Description: Compiz Fusion (meta) package for optional deps
[1] "desktop-effects" /usr/local/portage/layman/desktop-effects |
showing compiz-fusion (and all its component packages) as being hard masked.
Looking at http://compiz-fusion.org they seem to think that 0.7.8 is the latest version.
I don't want to downgrade, but hard masking is usually done for a good reason - anyone know why?
Regards
Ian |
|
| Back to top |
|
|
jkomar
Apprentice
Joined: 24 Sep 2004
Posts: 192
Location: Calgary, Canada
|
| Posted: Mon Oct 27, 2008 11:12 pm Post subject: |
|
|
| ipic wrote: | I've been using compiz-fusion 0.7.8 since it was introduced into the overlay, and its been good - for me at least.
Today, after updating layman and portage, I get this from eix:
| Code: | [D] x11-wm/compiz-fusion
Available versions: (~)0.6.0 (~)0.7.6[1] [M](~)0.7.8[1] **9999[1] {gnome kde unsupported}
Installed versions: 0.7.8[1](18:11:54 29/09/08)(gnome kde -unsupported)
Homepage: http://compiz-fusion.org
Description: Compiz Fusion (meta) package for optional deps
[1] "desktop-effects" /usr/local/portage/layman/desktop-effects |
showing compiz-fusion (and all its component packages) as being hard masked.
Looking at http://compiz-fusion.org they seem to think that 0.7.8 is the latest version.
I don't want to downgrade, but hard masking is usually done for a good reason - anyone know why?
Regards
Ian |
Excerpt from /usr/portage/profiles/package.mask:
| Code: | # Jorge Manuel B. S. Vicetto <jmbsvicetto@gentoo.org> (26 Oct 2008)
# Masked while adding to the tree and pending a final review.
~dev-python/compizconfig-python-0.7.8
~x11-apps/ccsm-0.7.8
~x11-apps/simple-ccsm-0.7.8
~x11-libs/compiz-bcop-0.7.8
~x11-libs/compizconfig-backend-gconf-0.7.8
~x11-libs/compizconfig-backend-kconfig-0.7.8
~x11-libs/libcompizconfig-0.7.8
~x11-plugins/compiz-fusion-plugins-extra-0.7.8
~x11-plugins/compiz-fusion-plugins-main-0.7.8
~x11-plugins/compiz-fusion-plugins-unsupported-0.7.8
~x11-wm/compiz-0.7.8
~x11-wm/compiz-fusion-0.7.8
~x11-wm/emerald-0.7.8 |
I suppose after a short time for the commit to the portage tree and the review to happen this mask will be removed.
Jason
_________________
www.jbox.ca
www.flashinthepan.ca
stormfront Portage/Paludis overlay |
|
| Back to top |
|
|
jkomar
Apprentice
Joined: 24 Sep 2004
Posts: 192
Location: Calgary, Canada
|
|
| Back to top |
|
|
billydv
l33t
Joined: 22 Dec 2006
Posts: 911
Location: Mount Vernon, NY
|
| Posted: Wed Oct 29, 2008 1:08 am Post subject: |
|
|
Not all of them, there are a few important parts missing, in example compiz itself!!!!!!!
_________________
Billy DeVincentis |
|
| Back to top |
|
|
billydv
l33t
Joined: 22 Dec 2006
Posts: 911
Location: Mount Vernon, NY
|
| Posted: Wed Oct 29, 2008 7:20 pm Post subject: |
|
|
I am not crazy about the fact that some of the ebuilds to run compiz fusion 0.7.8 have been introduced and others not. It doesn't seem to make sense. BTW, the live ebuilds still don't emerge for me, I got an error about 3 or 4 packages into the upgrade, I think it was on one of the plugin emerges where it died.
_________________
Billy DeVincentis |
|
| Back to top |
|
|
billydv
l33t
Joined: 22 Dec 2006
Posts: 911
Location: Mount Vernon, NY
|
| Posted: Wed Oct 29, 2008 7:50 pm Post subject: |
|
|
BTW, I just retries the live ebuilds and they now seem to compile in full.
_________________
Billy DeVincentis |
|
| Back to top |
|
|
jkomar
Apprentice
Joined: 24 Sep 2004
Posts: 192
Location: Calgary, Canada
|
| Posted: Wed Oct 29, 2008 8:40 pm Post subject: |
|
|
| billydv wrote: | | I am not crazy about the fact that some of the ebuilds to run compiz fusion 0.7.8 have been introduced and others not. |
You're definitely not crazy. I didn't look closely enough before I posted.
Jason
_________________
www.jbox.ca
www.flashinthepan.ca
stormfront Portage/Paludis overlay |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Fri Oct 31, 2008 12:22 pm Post subject: |
|
|
I'm trying to install compiz-0.7.8, which is neither in my main tree, nor in the tree provided by the overlay. All the compiz packages are now trying to build 0.7.8, and thus 'emerge -puD' fails for lack of compiz-0.7.8. Thus:
| Code: | # layman -l
* desktop-effects [Git ] (source: git://git.overlays.gentoo....)
* devnull [Mercurial ] (source: http://hg.core.ws/devnull )
* pd-overlay [Subversion] (source: https://pd-overlay.svn.sou...)
|
But! | Code: | # ls /usr/portage/local/layman/
cache_65bd38402ac8431067b54904bd2ed2d1.xml devnull make.conf mozilla overlays.xml pd-overlay
|
and: | Code: | # ls /usr/portage/x11-wm/compiz
ChangeLog compiz-0.5.2.ebuild compiz-0.6.2-r1.ebuild Manifest
compiz-0.5.0.ebuild compiz-0.6.2.ebuild files metadata.xml |
This is after running 'layman -S' and getting a successful exit. Can somebody please explain why compiz refuses to install, why I can't get the ebuilds by syncing to a gentoo mirror, and why layman won't install the overlay?
Thanks,
EE |
|
| Back to top |
|
|
jekyll
n00b
Joined: 07 Mar 2006
Posts: 63
|
| Posted: Sat Nov 01, 2008 12:52 am Post subject: |
|
|
Does compiz-0.7.8 require that xorg-server be version 1.5.1 or above?
I have ati-drivers version 8.542, which won't work with xorg-server 1.5 and above.
-jekyll |
|
| Back to top |
|
|
Devport
Guru
Joined: 15 Dec 2004
Posts: 361
|
| Posted: Sat Nov 01, 2008 5:27 am Post subject: |
|
|
| jekyll wrote: | Does compiz-0.7.8 require that xorg-server be version 1.5.1 or above?
I have ati-drivers version 8.542, which won't work with xorg-server 1.5 and above.
-jekyll |
No it doesnt - at least with nvidia its working fine here with xorg-server-1.3.0.0-r6. |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Sat Nov 01, 2008 12:07 pm Post subject: |
|
|
Hmm ... compiz-0.7.8 appears to be in my latest sync, so my first problem no longer exists. Now, though, emerge can't find compiz-manager:
| Code: | make[2]: Leaving directory `/var/tmp/portage/x11-wm/compiz-0.7.8/work/compiz-0.7.8'
make[1]: Leaving directory `/var/tmp/portage/x11-wm/compiz-0.7.8/work/compiz-0.7.8'
!!! dobin: /usr/portage/x11-wm/compiz/files/compiz-manager does not exist
*
* ERROR: x11-wm/compiz-0.7.8 failed.
* Call stack:
* ebuild.sh, line 49: Called src_install
* environment, line 2749: Called die
* The specific snippet of code:
* dobin "${FILESDIR}/compiz-manager" || die "dobin failed";
* The die message:
* dobin failed
|
So, progress! But, still no compiz.
EE |
|
| Back to top |
|
|
SHINODATT
n00b
Joined: 07 Jan 2006
Posts: 70
Location: Ontario, Canada
|
| Posted: Sat Nov 01, 2008 9:05 pm Post subject: |
|
|
| ExecutorElassus wrote: | Hmm ... compiz-0.7.8 appears to be in my latest sync, so my first problem no longer exists. Now, though, emerge can't find compiz-manager:
| Code: | make[2]: Leaving directory `/var/tmp/portage/x11-wm/compiz-0.7.8/work/compiz-0.7.8'
make[1]: Leaving directory `/var/tmp/portage/x11-wm/compiz-0.7.8/work/compiz-0.7.8'
!!! dobin: /usr/portage/x11-wm/compiz/files/compiz-manager does not exist
*
* ERROR: x11-wm/compiz-0.7.8 failed.
* Call stack:
* ebuild.sh, line 49: Called src_install
* environment, line 2749: Called die
* The specific snippet of code:
* dobin "${FILESDIR}/compiz-manager" || die "dobin failed";
* The die message:
* dobin failed
|
So, progress! But, still no compiz.
EE |
Getting the same error here.
_________________
Board: Maximus Formula, Rampage conversion, BIOS 308
CPU: Q6600 G0 @ 3.47Ghz (385x9), CM Hyper 212 Cooler
RAM: 4x 2GB Kingston 667 @ 771Mhz, 2V
Video: ASUS GeForce 8800GTS 512MB
OS: Gentoo 2.6.29 x86_64 |
|
| Back to top |
|
|
sideways
n00b
Joined: 24 Dec 2004
Posts: 37
Location: Los Gatos, CA
|
| Posted: Sat Nov 01, 2008 9:47 pm Post subject: |
|
|
| SHINODATT wrote: | | ExecutorElassus wrote: |
!!! dobin: /usr/portage/x11-wm/compiz/files/compiz-manager does not exist
So, progress! But, still no compiz.
EE |
Getting the same error here. |
Me too but this error went away for me after running emerge --sync after upgrading to portage 2.2.
Also, EPATCH_SOURCE errors cleared up for me after deleting "rm -rf /usr/portage/x11-**/compiz* and emerald".
I'm guessing this means I missed a step in upgrading to portage 2.2. |
|
| Back to top |
|
|
sideways
n00b
Joined: 24 Dec 2004
Posts: 37
Location: Los Gatos, CA
|
| Posted: Sat Nov 01, 2008 9:52 pm Post subject: |
|
|
| sideways wrote: |
Also, EPATCH_SOURCE errors cleared up for me after deleting "rm -rf /usr/portage/x11-**/compiz* and emerald".
I'm guessing this means I missed a step in upgrading to portage 2.2. |
Ugh, I posted to soon. Now I'm hung up on:
| Code: |
* Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is:
*
* /usr/portage/x11-plugins/compiz-fusion-plugins-extra/files/compiz-fusion-plugins-extra-text-fix.patch
* ( compiz-fusion-plugins-extra-text-fix.patch )
|
|
|
| Back to top |
|
|
sideways
n00b
Joined: 24 Dec 2004
Posts: 37
Location: Los Gatos, CA
|
| Posted: Sun Nov 02, 2008 12:30 am Post subject: |
|
|
| sideways wrote: |
Ugh, I posted to soon. Now I'm hung up on:
| Code: |
* Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is:
*
* /usr/portage/x11-plugins/compiz-fusion-plugins-extra/files/compiz-fusion-plugins-extra-text-fix.patch
* ( compiz-fusion-plugins-extra-text-fix.patch )
|
|
fyi, I synced just now and everything builds and works now with ~x86 package.keywords for compiz stuff |
|
| Back to top |
|
|
SHINODATT
n00b
Joined: 07 Jan 2006
Posts: 70
Location: Ontario, Canada
|
| Posted: Sun Nov 02, 2008 1:04 am Post subject: |
|
|
| sideways wrote: | | sideways wrote: |
Ugh, I posted to soon. Now I'm hung up on:
| Code: |
* Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is:
*
* /usr/portage/x11-plugins/compiz-fusion-plugins-extra/files/compiz-fusion-plugins-extra-text-fix.patch
* ( compiz-fusion-plugins-extra-text-fix.patch )
|
|
fyi, I synced just now and everything builds and works now with ~x86 package.keywords for compiz stuff |
Yup, seems they've fixed it.
_________________
Board: Maximus Formula, Rampage conversion, BIOS 308
CPU: Q6600 G0 @ 3.47Ghz (385x9), CM Hyper 212 Cooler
RAM: 4x 2GB Kingston 667 @ 771Mhz, 2V
Video: ASUS GeForce 8800GTS 512MB
OS: Gentoo 2.6.29 x86_64 |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Mon Nov 03, 2008 8:46 pm Post subject: |
|
|
Hmm... seems to be linking against an invalid KDE/Qt library:
| Code: | Good - your configure finished. Start make now
make -j3
make all-recursive
make[1]: Entering directory `/var/tmp/portage/x11-libs/compizconfig-backend-kconfig-0.7.8/work/compizconfig-backend-kconfig-0.7.8'
Making all in settings-backend
make[2]: Entering directory `/var/tmp/portage/x11-libs/compizconfig-backend-kconfig-0.7.8/work/compizconfig-backend-kconfig-0.7.8/settings-backend'
/bin/sh ../libtool --silent --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. -I./lib -I/usr/qt/3/include -I. -I/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -march=athlon64 -O2 -pipe -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -I/usr/include/compizconfig -I/usr/include/libxml2 -I/usr/include/startup-notification-1.0 -I/usr/include/compiz -c -o kconfig_backend.lo kconfig_backend.cpp
In file included from /usr/include/kdecore_export.h:24,
from /usr/include/kconfigbase.h:27,
from /usr/include/kconfig.h:27,
from kconfig_backend.cpp:24:
/usr/include/kdemacros.h:162:29: error: QtCore/qglobal.h: No such file or directory
In file included from /usr/include/kconfig.h:27,
from kconfig_backend.cpp:24:
{blah blah blah}
In file included from kconfig_backend.cpp:34:
/usr/include/kdirwatch.h:63: error: invalid use of incomplete type 'struct QObject'
/usr/include/kdebug.h:207: error: forward declaration of 'struct QObject'
/usr/include/kdirwatch.h:66: error: expected ';' before 'public'
/usr/include/kdirwatch.h:76: error: 'WatchModes' has not been declared
/usr/include/kdirwatch.h:76: error: 'WatchMode' has not been declared
/usr/include/kdirwatch.h:85: error: expected ';' before 'KDirWatch'
/usr/include/kdirwatch.h:111: error: 'WatchModes' has not been declared
/usr/include/kdirwatch.h:274: error: expected primary-expression before 'void'
/usr/include/kdirwatch.h:274: error: expected ';' before 'void'
/usr/include/kdirwatch.h:111: error: 'WatchDirOnly' was not declared in this scope
/usr/include/kdirwatch.h:294: error: expected constructor, destructor, or type conversion before '(' token
make[2]: *** [kconfig_backend.lo] Error 1
make[2]: Leaving directory `/var/tmp/portage/x11-libs/compizconfig-backend-kconfig-0.7.8/work/compizconfig-backend-kconfig-0.7.8/settings-backend'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/x11-libs/compizconfig-backend-kconfig-0.7.8/work/compizconfig-backend-kconfig-0.7.8'
make: *** [all] Error 2
*
* ERROR: x11-libs/compizconfig-backend-kconfig-0.7.8 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 4120: Called kde_src_compile
* environment, line 2948: Called kde_src_compile 'all'
* environment, line 3073: Called kde_src_compile 'myconf' 'configure' 'make'
* environment, line 3069: Called die
* The specific snippet of code:
* emake || die "died running emake, $FUNCNAME:make"
* The die message:
* died running emake, kde_src_compile:make
*
* 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-libs/compizconfig-backend-kconfig-0.7.8/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-libs/compizconfig-backend-kconfig-0.7.8/temp/environment'.
*
>>> Failed to emerge x11-libs/compizconfig-backend-kconfig-0.7.8, Log file: |
Can someone please remind me (because I'm dumb and forgot) how to fix this partiular failure?
Thanks,
EE |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Tue Nov 11, 2008 11:08 pm Post subject: |
|
|
Uh, bump or whatever. I'm still getting this error. Anybody else? Did I do nomething stupid? All of the 0.7.8 compiz stuff fails to compile.
Thanks,
EE |
|
| Back to top |
|
|
jkomar
Apprentice
Joined: 24 Sep 2004
Posts: 192
Location: Calgary, Canada
|
| Posted: Tue Nov 11, 2008 11:21 pm Post subject: |
|
|
| ExecutorElassus wrote: | Can someone please remind me (because I'm dumb and forgot) how to fix this partiular failure?
Thanks,
EE |
Are you running KDE 4.1.x? I couldn't compile compizconfig-backend-kconfig-0.7.8 under KDE 4.1.2. I guess the integration hasn't been ported to KDE 4.
Jason
_________________
www.jbox.ca
www.flashinthepan.ca
stormfront Portage/Paludis overlay |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Tue Nov 11, 2008 11:30 pm Post subject: |
|
|
You are correct, sir! The bugzilla post is here. I assume this is an integration problem, and it isn't fixed under kdelibs.4.2.3-r1. So, it's not me! It's some poor programmer somewhere who has to fix it! Yay!
I'll give a cookie to the programmer who fixes it*.
Thanks,
EE
*(not really, but I'll send good vibes or something) |
|
| Back to top |
|
|
|
Unsupported Software
