| View previous topic :: View next topic |
| Author |
Message |
konna
n00b
Joined: 29 Jun 2005
Posts: 24
Location: Jõgeva, Estonia
|
 Posted: Sun Mar 12, 2006 5:41 pm Post subject: [SOLVED]vte emerge prob while installing gnome |
 |
|
I`m tring to install gnome-light but I`m getting error when vte is emerging.
| Code: |
!!! ERROR: x11-libs/vte-0.11.16-r1 failed.
!!! Function dyn_install, Line 1057, Exitcode 0
!!! Insecure binaries detected |
| Code: |
make install-exec-hook
make[3]: Entering directory `/var/tmp/portage/vte-0.11.16-r1/work/vte-0.11.16/gnome-pty-helper'
chown root.utmp /var/tmp/portage/vte-0.11.16-r1/image//usr/libexec/gnome-pty-helper || true
chown: `root.utmp' syntax is obsolete; use `:' since this will be removed in the future
chmod g+s /var/tmp/portage/vte-0.11.16-r1/image//usr/libexec/gnome-pty-helper || true
make[3]: Leaving directory `/var/tmp/portage/vte-0.11.16-r1/work/vte-0.11.16/gnome-pty-helper'
make[2]: Nothing to be done for `install-data-am'.
make[2]: warning: Clock skew detected. Your build may be incomplete.
make[2]: Leaving directory `/var/tmp/portage/vte-0.11.16-r1/work/vte-0.11.16/gnome-pty-helper'
make[1]: warning: Clock skew detected. Your build may be incomplete.
make[1]: Leaving directory `/var/tmp/portage/vte-0.11.16-r1/work/vte-0.11.16/gnome-pty-helper'
make[1]: Entering directory `/var/tmp/portage/vte-0.11.16-r1/work/vte-0.11.16'
make[2]: Entering directory `/var/tmp/portage/vte-0.11.16-r1/work/vte-0.11.16'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/var/tmp/portage/vte-0.11.16-r1/image//usr/lib/pkgconfig" || mkdir -p -- "/var/tmp/portage /vte-0.11.16-r1/image//usr/lib/pkgconfig"
/bin/install -c -m 644 'vte.pc' '/var/tmp/portage/vte-0.11.16-r1/image//usr/lib/pkgconfig/vte.pc'
make[2]: Leaving directory `/var/tmp/portage/vte-0.11.16-r1/work/vte-0.11.16'
make[1]: Leaving directory `/var/tmp/portage/vte-0.11.16-r1/work/vte-0.11.16'
man:
prepallstrip:
strip: strip --strip-unneeded
usr/bin/vte
usr/lib/vte/iso8859mode
usr/lib/vte/slowcat
usr/lib/vte/nativeecho
usr/lib/vte/vterdb
usr/lib/vte/utf8echo
usr/lib/vte/utf8mode
usr/lib/vte/interpret
usr/lib/libvte.so.4.4.0
usr/lib/python2.4/site-packages/gtk-2.0/vtemodule.so
usr/libexec/gnome-pty-helper
making executable: /usr/lib/libvte.so.4.4.0
QA Notice: the following files contain insecure RUNPATH's
|
Need some help there, tnx. 
PS! Sorry for my crap english..
Last edited by konna on Sun Mar 12, 2006 9:58 pm; edited 1 time in total |
|
| Back to top |
|
 |
sternklang
Veteran
Joined: 10 Sep 2005
Posts: 1641
Location: Somewhere in time and space
|
| Posted: Sun Mar 12, 2006 6:52 pm Post subject: |
|
|
See this bug for details on this problem. The bottom line is this is fixed in portage-2.1_pre6, which is an ~arch (unstable) package. Assuming you are on x86, you would have to: | Code: | echo "sys-apps/portage ~x86" >> /etc/portage/package.keywords
emerge portage |
Then assuming you are upgrading from a stable portage, you need to do:to rebuild the portage cache as the structure has changed since the older versions.
That apparently fixes various insecure RUNPATH problems, including with vte. The only potential problem with this is that there are some bugs in the new portage. The only ones I've run into so far have to do with advanced features (confcache specifically) and x11 fonts, so if you are not adding font packages to your system you should be okay. |
|
| Back to top |
|
|
konna
n00b
Joined: 29 Jun 2005
Posts: 24
Location: Jõgeva, Estonia
|
| Posted: Sun Mar 12, 2006 7:17 pm Post subject: |
|
|
Oo big thanks , I`ll try it out and let you know if it works or not.
//edit: worked perfectly, problem solved. Tnx m8 . |
|
| Back to top |
|
|
cayenne
l33t
Joined: 17 Oct 2002
Posts: 945
Location: New Orleans
|
| Posted: Thu Mar 16, 2006 1:02 am Post subject: What's the difference? |
|
|
What is the difference between doing this:
| Code: | echo "sys-apps/portage ~x86" >> /etc/portage/package.keywords
emerge portage |
And doing the ACCEPT_KEYWORDS="~x86" emerge portage the way I've always done it?
This is new to me....are the advantages to doing it this way?
TIA,
cayenne
_________________
Light travels faster than sound. This is why some people appear bright until you hear them speak......... |
|
| Back to top |
|
|
sternklang
Veteran
Joined: 10 Sep 2005
Posts: 1641
Location: Somewhere in time and space
|
| Posted: Thu Mar 16, 2006 1:19 am Post subject: Re: What's the difference? |
|
|
| cayenne wrote: | What is the difference between doing this:
| Code: | echo "sys-apps/portage ~x86" >> /etc/portage/package.keywords
emerge portage |
And doing the ACCEPT_KEYWORDS="~x86" emerge portage the way I've always done it? |
Putting in in package.keywords makes it persistant. If you did an "emerge -uD world" after a sync, your package would be downgraded to the stable version -- and if you didn't pay close attention to the output you wouldn't know it until you failed to get some feature that the ~x86 version of the package provides. You don't have to worry about that with using package.keywords. The same applies to using /etc/portage/package.use vs. USE="useflag" emerge package.
It also helps to keep track of exactly which packages you are using the ~x86 version of on your otherwise x86 system.
Why depend on remembering to use ACCEPT_KEYWORDS when you can get the computer to do the work for you?  |
|
| Back to top |
|
|
|
Desktop Environments
