FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 11-27-2011, 09:34 PM
walt
 
Default Disappearing useflag hell

Somewhere deep in the bowels of portage my 'introspection' useflag is
vanishing -- but on just one of my three machines.

I set the introspection useflag on all three machines (two ~amd64 and
one ~x86) but when I run emerge --info, only two of the machines show
the introspection useflag in the output. Why?

All three machines share the same /usr/portage by NFS, so they all
see the same use.mask and use.force files, etc.

I'm running the default linux desktop gnome profile on all three.

I tried deleting my /etc/portage/* on the problem machine, which made
no difference.

I even tried using an empty make.conf and adding the single line
USE="introspection", but that made no difference either.

When I flip other useflags in make.conf the changes show up in the
output of emerge --info, but not when I flip 'introspection'.

Two days wasted and I'm out of ideas.

Anyone understand the details of emerge --info or what I can do to
diagnose this problem?
 
Old 11-27-2011, 10:43 PM
Dale
 
Default Disappearing useflag hell

walt wrote:

Somewhere deep in the bowels of portage my 'introspection' useflag is
vanishing -- but on just one of my three machines.

I set the introspection useflag on all three machines (two ~amd64 and
one ~x86) but when I run emerge --info, only two of the machines show
the introspection useflag in the output. Why?

All three machines share the same /usr/portage by NFS, so they all
see the same use.mask and use.force files, etc.

I'm running the default linux desktop gnome profile on all three.

I tried deleting my /etc/portage/* on the problem machine, which made
no difference.

I even tried using an empty make.conf and adding the single line
USE="introspection", but that made no difference either.

When I flip other useflags in make.conf the changes show up in the
output of emerge --info, but not when I flip 'introspection'.

Two days wasted and I'm out of ideas.

Anyone understand the details of emerge --info or what I can do to
diagnose this problem?





I searched the -dev mailing list and only found references to the flag
being enabled on a lot of packages. It appears to be a Gnome thing but
don't quote me on it. Is it possible that it is enable by default
whether it is set or not? There was talk of making it on in the profile
instead of make.conf.


I would do a emerge -pv <package that uses the flag> and see if it shows
up there. If it is a small package, compile it then see if it is built
in or not. If it is, then they have it turned on somewhere. This is a
bug report that you can read on too.


https://bugs.gentoo.org/show_bug.cgi?id=324989

That help any?

Dale

:-) :-)

--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
 
Old 11-27-2011, 11:29 PM
Bill Longman
 
Default Disappearing useflag hell

On Nov 27, 2011 3:44 PM, "Dale" <rdalek1967@gmail.com> wrote:

>

> walt wrote:

>>

>> Somewhere deep in the bowels of portage my 'introspection' useflag is

>> vanishing -- but on just one of my three machines.

>>

>> I set the introspection useflag on all three machines (two ~amd64 and

>> one ~x86) but when I run emerge --info, only two of the machines show

>> the introspection useflag in the output. *Why?

>>

>> All three machines share the same /usr/portage by NFS, so they all

>> see the same use.mask and use.force files, etc.

>>

>> I'm running the default linux desktop gnome profile on all three.

>>

>> I tried deleting my /etc/portage/* on the problem machine, which made

>> no difference.

>>

>> I even tried using an empty make.conf and adding the single line

>> USE="introspection", but that made no difference either.

>>

>> When I flip other useflags in make.conf the changes show up in the

>> output of emerge --info, but not when I flip 'introspection'.

>>

>> Two days wasted and I'm out of ideas.

>>

>> Anyone understand the details of emerge --info or what I can do to

>> diagnose this problem?

>>

>>

>>

>

> I searched the -dev mailing list and only found references to the flag being enabled on a lot of packages. *It appears to be a Gnome thing but don't quote me on it. *Is it possible that it is enable by default whether it is set or not? *There was talk of making it on in the profile instead of make.conf.



Yeah, could it be part of your profile? That's up in /etc so it could be different among hosts.


>

> I would do a emerge -pv <package that uses the flag> and see if it shows up there. *If it is a small package, compile it then see if it is built in or not. *If it is, then they have it turned on somewhere. *This is a bug report that you can read on too.


>

> https://bugs.gentoo.org/show_bug.cgi?id=324989

>

> That help any?

>

> Dale

>

> :-) *:-)

>

> --

> I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

>

>
 
Old 11-28-2011, 12:27 AM
Dale
 
Default Disappearing useflag hell

Dale wrote:


I searched the -dev mailing list and only found references to the flag
being enabled on a lot of packages. It appears to be a Gnome thing
but don't quote me on it. Is it possible that it is enable by default
whether it is set or not? There was talk of making it on in the
profile instead of make.conf.


I would do a emerge -pv <package that uses the flag> and see if it
shows up there. If it is a small package, compile it then see if it
is built in or not. If it is, then they have it turned on somewhere.
This is a bug report that you can read on too.


https://bugs.gentoo.org/show_bug.cgi?id=324989

That help any?

Dale

:-) :-)




More looking here. This is what I found with euse -i on my amd64 system:

[- ] introspection
sys-fs/udev: Use dev-libs/gobject-introspection for introspection


but this is what emerge shows:

root@fireball / # emerge -pv udev

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] sys-fs/udev-164-r2 USE="extras -build (-selinux)
-test" 0 kB


Total: 1 package (1 reinstall), Size of downloads: 0 kB
root@fireball / #

So, I suspect it is enabled somewhere on a much lower level and not
optional. Then I emerge udev and used the find tool. I found these
little tidbits:


./configure --prefix=/usr --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --mandir=/usr/share/man
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
--localstatedir=/var/lib --prefix=/usr --sysconfdir=/etc --sbindir=/sbin
--libdir=/usr/lib64 --with-rootlibdir=/lib64 --libexecdir=/lib64/udev
--enable-logging --enable-static --without-selinux --enable-extras
--disable-introspection


gintrospection: no

So, seeing that it is disabled, maybe it is disabled now on a lower
level and is no longer a option? Notice the question mark. This makes
me wonder. It still shows up with euse. It appears disabled but also
doesn't show up as a USE flag option for us mere mortals. ;-)


More looking. I find this:

[- ] introspection
media-libs/gstreamer: Use dev-libs/gobject-introspection for
introspection

Then emerge reports this:

root@fireball / # emerge -pv gstreamer

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] media-libs/gstreamer-0.10.35 USE="introspection nls
-test" 0 kB


Total: 1 package (1 reinstall), Size of downloads: 0 kB
root@fireball / #

So, it is enabled on this one but not udev. The flag does exist and can
be controlled, at least on some packages.


My thoughts. Some packages it is disabled somewhere that overrides your
settings. Might be because it breaks something. The packages where it
is a option, then it sees your settings and applies them. I'm as
confused as you are on emerge --info tho. If it helps any, I don't have
the flag in my make.conf but it appears to be enabled for gstreamer but
disabled for udev. I think the devs are picking and choosing which
packages can have the flag user controlled and not break something.


One last thing that I find interesting. This is weird.

root@fireball / # USE="introspection" emerge -Na world

These are the packages that would be merged, in order:

Calculating dependencies... done!

Total: 0 packages, Size of downloads: 0 kB

Nothing to merge; would you like to auto-clean packages? [Yes/No] n

Quitting.

root@fireball / # USE="-introspection" emerge -Na world

These are the packages that would be merged, in order:

Calculating dependencies... done!

Total: 0 packages, Size of downloads: 0 kB

Nothing to merge; would you like to auto-clean packages? [Yes/No] n

Quitting.

root@fireball / #

It appears that the packages on my system are all controlled by
something over my settings. It does nothing when I enable or disable
it. Yet it is turned on for one package above and turned off for the
other. Scratch your head on that one for a while.


Dale

:-) :-)

--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
 

Thread Tools




All times are GMT. The time now is 06:50 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org