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 07-30-2010, 01:47 PM
Bill Longman
 
Default eix shows keyworded packages on home PC, but not on server

On 07/30/2010 04:57 AM, Mark David Dumlao wrote:
> diff between the eix --dump of my PC and the server
>
> ===
> madumlao@trixie ~ $ diff -Naur PC server
> --- PC 2010-07-30 19:54:38.000000000 +0800
> +++ server 2010-07-30 19:55:05.000000000 +0800
> @@ -126,7 +126,7 @@
>
> # STRING
> # The path to the ebuild.sh executable.
> -EXEC_EBUILD_SH="%{EPREFIX_PORTAGE_EXEC}/usr/lib64/portage/bin/ebuild.sh"
> +EXEC_EBUILD_SH="%{EPREFIX_PORTAGE_EXEC}/usr/lib/portage/bin/ebuild.sh"
>
> # STRING
> # The path to the tempfile generated by "ebuild depend".
> @@ -177,7 +177,7 @@
> # STRING
> # This variable is passed unchanged to ebuild.sh
> # Usually ebuild.sh uses it to calculate the PATH.
> -PORTAGE_ROOTPATH="/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.3.4"
> +PORTAGE_ROOTPATH="/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.3.4:/usr/i686-pc-linux-gnu/x86_64-pc-linux-gnu/gcc-bin/4.4.4"
>
> # STRING
> # This variable is passed unchanged to ebuild.sh
> ===
>
> Seems to be just paths, don't see why that would cause a problem.
>
> Both machines are using portage 2.1.8.3
>
> On Fri, Jul 30, 2010 at 7:46 PM, Mark David Dumlao <madumlao@gmail.com> wrote:
>> Hi guys,
>> Eix is one of those packages where you just set it and forget it, and
>> apparently I've forgotten there was even anything to set.
>>
>> I have a home PC running gentoo. If I do eix foo, and foo happens to
>> be keyworded unmasked in my package.keywords, I get for instance:
>> [i] dev-python/snakeoil
>> Available versions: <yellow>(~)0.3.6.4 (~)0.3.6.5
>> <block-yellow>(~)0.3.7</block-yellow></yellow>
>> Installed versions: 0.3.7(07:34:54 PHT Saturday, 10 July, 2010)
>> Homepage: http://www.pkgcore.org/
>> Description: Miscellaneous python utility code.
>>
>> I try the same on a relatively young gentoo server I'm managing and
>> * dev-python/snakeoil
>> Available versions: <yellow>~0.3.6.4 ~0.3.6.5 ~0.3.7</yellow>
>> Homepage: http://www.pkgcore.org/
>> Description: Miscellaneous python utility code.
>>
>> It's unkeyworded, however, in my package.keywords in both machines:
>> (home machine)
>> madumlao@trixie ~ $ grep snakeoil -r /etc/portage/package.keywords/
>> /etc/portage/package.keywords/autounmask-pkgcore:dev-python/snakeoil ~amd64
>>
>> (server)
>> master@zen ~ $ sudo grep -r snakeoil /etc/portage/package.keywords/
>> /etc/portage/package.keywords/system.keywords:dev-python/snakeoil ~x86
>>
>> Apparently I'm missing some environment variable, but I can't for the
>> life of me imagine how I've set it.
>> <home PC>
>> madumlao@trixie ~/store/HeCares/Photo upload functionality $ cat /etc/eixrc
>> # /etc/eixrc
>> #
>> # In this file system-wide defaults for variables related to eix binaries
>> # are stored, i.e. the variables set in this file override the built-in
>> # defaults. Both can be overridden by ~/.eixrc and by environment variables.
>> #
>> # It is strongly recommended to set here only those variables which you
>> # want to *differ* from the built-in defaults (or for which you have a
>> # particular reason why the default should never change with an eix update).
>> #
>> # *Otherwise you might miss changes in the defaults in newer eix versions*
>> # which may result in confusing behavior of the eix binaries.
>> #
>> # ebuilds of <=eix-0.10.3 (and >=eix-0.7.4) used to set *all* variables in
>> # /etc/eixrc which is not recommended anymore. If you want to get such a file
>> # (i.e. a file where all variables are described and set to the current
>> # values resp. to the built-in default values) you can redirect the output
>> # of the options --dump or --dump-defaults, respectively.
>> #
>> # However once more: To avoid unexpected problems
>> #
>> # *IT IS NOT RECOMMENDED TO SET _ALL_ VARIABLES* in /etc/eixrc
>> #
>> # Only set those for which you have a reason to do so!
>> #
>> # For the available variables and their defaults, see the output of the
>> # options --dump or --dump-defaults.
>> # For more detailed explanations see the manpage of eix.
>>
>> madumlao@trixie ~/store/HeCares/Photo upload functionality $ cat
>> /etc/eix-sync.conf
>> # eix-sync.conf
>> ## defines options to eix-sync, caching system for portage
>>
>>
>> #layman overlays to be synced (* means all)
>> *
>> </home PC>
>>
>> <server>
>> master@zen ~ $ cat /etc/eixrc
>> # /etc/eixrc
>> #
>> # In this file system-wide defaults for variables related to eix binaries
>> # are stored, i.e. the variables set in this file override the built-in
>> # defaults. Both can be overridden by ~/.eixrc and by environment variables.
>> #
>> # It is strongly recommended to set here only those variables which you
>> # want to *differ* from the built-in defaults (or for which you have a
>> # particular reason why the default should never change with an eix update).
>> #
>> # *Otherwise you might miss changes in the defaults in newer eix versions*
>> # which may result in confusing behavior of the eix binaries.
>> #
>> # ebuilds of <=eix-0.10.3 (and >=eix-0.7.4) used to set *all* variables in
>> # /etc/eixrc which is not recommended anymore. If you want to get such a file
>> # (i.e. a file where all variables are described and set to the current
>> # values resp. to the built-in default values) you can redirect the output
>> # of the options --dump or --dump-defaults, respectively.
>> #
>> # However once more: To avoid unexpected problems
>> #
>> # *IT IS NOT RECOMMENDED TO SET _ALL_ VARIABLES* in /etc/eixrc
>> #
>> # Only set those for which you have a reason to do so!
>> #
>> # For the available variables and their defaults, see the output of the
>> # options --dump or --dump-defaults.
>> # For more detailed explanations see the manpage of eix.
>>
>> master@zen ~ $ cat /etc/eix-sync.conf
>> cat: /etc/eix-sync.conf: No such file or directory
>> </server>
>>
>> All comments for the both of them, so it must be a default I'm missing
>> that's different for the 2 machines. Any ideas?
>> --
>> This email is: [ ] actionable [ ] fyi [x] social
>> Response needed: [ ] yes [x] up to you [ ] no
>> Time-sensitive: [ ] immediate [ ] soon [ ] none
>>

What does "eselect profile list" show you on both hosts?
 
Old 07-30-2010, 03:51 PM
Bill Longman
 
Default eix shows keyworded packages on home PC, but not on server

On 07/30/2010 07:46 AM, Mark David Dumlao wrote:
> On Fri, Jul 30, 2010 at 9:47 PM, Bill Longman <bill.longman@gmail.com> wrote:
>> What does "eselect profile list" show you on both hosts?
> home PC
> madumlao@trixie ~ $ eselect profile list
> Available profile symlink targets:
> [1] default/linux/amd64/10.0
> [2] default/linux/amd64/10.0/desktop *
> [3] default/linux/amd64/10.0/desktop/gnome
> [4] default/linux/amd64/10.0/desktop/kde
> [5] default/linux/amd64/10.0/developer
> [6] default/linux/amd64/10.0/no-multilib
> [7] default/linux/amd64/10.0/server
> [8] hardened/linux/amd64/10.0
> [9] hardened/linux/amd64/10.0/no-multilib
> [10] selinux/2007.0/amd64
> [11] selinux/2007.0/amd64/hardened
> [12] selinux/v2refpolicy/amd64
> [13] selinux/v2refpolicy/amd64/desktop
> [14] selinux/v2refpolicy/amd64/developer
> [15] selinux/v2refpolicy/amd64/hardened
> [16] selinux/v2refpolicy/amd64/server
>
> server
> master@zen ~ $ sudo eselect profile list
> Available profile symlink targets:
> [1] default/linux/x86/10.0 *
> [2] default/linux/x86/10.0/desktop
> [3] default/linux/x86/10.0/desktop/gnome
> [4] default/linux/x86/10.0/desktop/kde
> [5] default/linux/x86/10.0/developer
> [6] default/linux/x86/10.0/server
> [7] hardened/linux/x86/10.0
> [8] selinux/2007.0/x86
> [9] selinux/2007.0/x86/hardened
> [10] selinux/v2refpolicy/x86
> [11] selinux/v2refpolicy/x86/desktop
> [12] selinux/v2refpolicy/x86/developer
> [13] selinux/v2refpolicy/x86/hardened
> [14] selinux/v2refpolicy/x86/server
>
> I'm not that familiar with how the profile affects eix though.

The profile affects the default USE settings. This is a very important
Gentoo concept.
 
Old 07-30-2010, 06:05 PM
Bill Longman
 
Default eix shows keyworded packages on home PC, but not on server

On 07/30/2010 09:26 AM, Mark David Dumlao wrote:
> On Fri, Jul 30, 2010 at 11:51 PM, Bill Longman <bill.longman@gmail.com> wrote:
>> The profile affects the default USE settings. This is a very important
>> Gentoo concept.
>
> emerge --info eix on both machines:
>
> PC:
> app-portage/eix-0.20.5 was built with the following:
> USE="bzip2 (multilib) nls sqlite -debug -doc -hardened -optimization
> -strong-optimization -tools"
> LDFLAGS="-Wl,-O1"
>
> server:
> app-portage/eix-0.20.5 was built with the following:
> USE="bzip2 nls sqlite -debug -doc -hardened -optimization
> -strong-optimization -tools"
> LDFLAGS="-Wl,-O1"
>
>
> The only difference between the USE flags of both machines is that my
> local eix was built with multilib. I don't know any documentation
> references that say how that should affect eix output settings, which
> shouldn't be related.
>
> Just to clarify, emerge detects that the packages are keyworded on
> both machines. It's just not being outputted by eix. And there's no
> reason why multilib should cause eix to change the output settings.

I mean to say that the profile sets the *global* USE settings. If you
were to compare "euse -i" between the two machines, you would see that
some flags are "+D" and some are "+C", for instance. The ones that are
set by the profile are "+D". If you peruse the portage/profiles you'll
see that the make.defaults files are setting different USE values. Not
to mention that you are on different architectures between the two, so
some packages will be masked and some not depending upon the
architecture. It's not a matter of how eix was built, it's a matter of
the configuration of the host.

Is that what you were trying to resolve? Or do I not understand your
question? Can you put a package mask in just *any* file below
package.keywords/ and as long as it matches it will be valid?
 
Old 07-31-2010, 03:18 PM
Vaeth
 
Default eix shows keyworded packages on home PC, but not on server

[I know that the headers are wrong; sorry for that]

> I try the same on a relatively young gentoo server I'm managing and
> * dev-python/snakeoil
> Available versions: <yellow>~0.3.6.4 ~0.3.6.5 ~0.3.7</yellow>
[...]
> It's unkeyworded, however

Did you verify with portage that it is unkeyworded?
(There could be many other reasons why it is not).
In other words: Does emerge -a =dev-python/snakeoil-0.3.7
really not complain?

As I understand, you already compared the output of eix --dump.
I suppose you verified that this output was created in the same
environment (i.e. with the same user and the same environment
variables) in which you call eix later on?
If this is the case, already most causes of different eix
configuration are excluded (e.g. LOCAL_PORTAGE_CONFIG should
be "true" on both machines; just to make sure, you can also try
with eix --print LOCAL_PORTAGE_CONFIG).

Please also verify with "type -a eix" that you do not use by accident
some wrapper (shell function, alias, or script) which could set some
eix command line options.

The only difference I could still imagine is that you have set an
environment variable which portage ignores but eix does not.
For instance, does
eix --print ARCH
(and similarly eix --print ACCEPT_KEYWORDS)
show the correct architecture (x86 or amd64) which matches with the
entry in your package.keywords file? Does removing the ~x86/~amd64
in that file change the output?

Other possible causes:
Perhaps some file, most probably package.keywords file cannot be opened
for some reason by eix.
Therefore the simple question: Do you run eix with root permissions
as you probably do with portage?
And just to be sure: Does "strace eix -e snakeoil" show you that
package.keywords was succesfully opened by eix?

If nothing gives a hint, I suggest that you open an eix bug.

Regards
Martin Všth
 

Thread Tools




All times are GMT. The time now is 02:42 AM.

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