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, 11:46 AM
Mark David Dumlao
 
Default eix shows keyworded packages on home PC, but not on server

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
 
Old 07-30-2010, 11:57 AM
Mark David Dumlao
 
Default eix shows keyworded packages on home PC, but not on server

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
>



--
This email is:* * [ ] actionable** [ ] fyi* * * * [ ] social
Response needed:* [ ] yes* * * * * [ ] up to you* [ ] no
Time-sensitive:** [ ] immediate* * [ ] soon* * ** [ ] none
 
Old 07-30-2010, 02:46 PM
Mark David Dumlao
 
Default eix shows keyworded packages on home PC, but not on server

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.
 
Old 07-30-2010, 04:26 PM
Mark David Dumlao
 
Default eix shows keyworded packages on home PC, but not on server

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.
--
This email is:* * [ ] actionable** [ ] fyi* * * * [ ] social
Response needed:* [ ] yes* * * * * [ ] up to you* [ ] no
Time-sensitive:** [ ] immediate* * [ ] soon* * ** [ ] none
 
Old 07-31-2010, 09:21 AM
Mark David Dumlao
 
Default eix shows keyworded packages on home PC, but not on server

On Sat, Jul 31, 2010 at 2:05 AM, Bill Longman <bill.longman@gmail.com> wrote:
> 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?

I'm sorry, I think I wasn't very good at describing the problem.

Let's say there is a package foo. Foo is keyworded, so if I try
building it on either machine, portage complains saying it's masked.

Now I unkeyword foo on both machines by adding it to
/etc/portage/package.keywords/foo.keywords. When I run emerge on both
machines portage will no longer complain and will build the keyworded
package as intended. All's well.

However, on one machine, eix reports that I have unkeyworded the
package foo by printing parens around the keyword marker ~. On the
other machine, eix does not report it. That is, the package is being
effectively unmasked for emerge, but eix is not reporting the
unmasking to me. So that's why I think it's either an eix
configuration issue, or when you mentioned profile, checked the eix
use flags. So my question was "what could I be missing in eix?" but if
I'm wrong and it's not an eix thing then I'll happily take any
suggestions.
 
Old 08-01-2010, 10:30 AM
Mark David Dumlao
 
Default eix shows keyworded packages on home PC, but not on server

On Sat, Jul 31, 2010 at 11:18 PM, Vaeth
<vaeth@mathematik.uni-wuerzburg.de> wrote:
> [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
> 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?
Thanks for the user tip.

I forgot that I "hardened" the server by default umasking all accounts
to 007 (something I don't do on the desktop), so eix couldn't read the
/etc/portage/ files as a regular user, because I wrote them as root.
So if I eix as root or using sudo (which I don't do), I get the
parens, but if I don't, eix can't read the keyword files, so no
parens. Interesting.

So this one's solved now.
--
This email is:* * [ ] actionable** [x] fyi* * * * [ ] social
Response needed:* [ ] yes* * * * * [ ] up to you* [ ] no
Time-sensitive:** [ ] immediate* * [ ] soon* * ** [ ] none
 

Thread Tools




All times are GMT. The time now is 01:09 AM.

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