Re: [gentoo-user] [OT] Thanks to the devs

2012-05-23 Thread Walter Dnes 
On Wed, May 23, 2012 at 03:10:25PM -0400, Michael Mol wrote

> I'd just like to say thank you for the work you guys do.
> 
> Thank you for the work you guys do.
> 
> There. I said it. *Goes back to work*

  Me too.  They answered my questions as I stumbled along replacing udev
with mdev.  And they even accepted a feature request from me to include
busybox[mdev] as an option in virtual/dev-manager...

$ grep Walter /usr/portage/virtual/dev-manager/ChangeLog 
  Add busybox[mdev] as a provider #395319 by Walter Dnes.

Thank you again.

-- 
Walter Dnes

Re: [gentoo-user] Re: [entirely ON topic] Thanks to the devs

2012-05-23 Thread kwkhui 
On Thu, 24 May 2012 02:03:07 +0200
Alan McKinnon  wrote:

> On Wed, 23 May 2012 16:42:15 -0700
> walt  wrote:
> 
> > On 05/23/2012 12:10 PM, Michael Mol wrote:
> > > I've noticed a lot of overt participation on this list by gentoo
> > > devs[1], especially in scenarios where they're explaining
> > > rationales and reasoning behind changes that affect users.
> > > 
> > > I'd just like to say thank you for the work you guys do.
> > > 
> > > Thank you for the work you guys do.
> > 
> > I posted the same, but a long time ago, so I'll add a mee too.

Another me too.

> > (Thanking the suse devs here would of course be very
> > inappropriate ;)
> 
> But then you'd be excluding gregkh and *that* would be very
> inappropriate ;-) 

Is gregkh still a SUSE dev?  I thought he now works for Linux
Foundation (since February).

Kerwin.


signature.asc
Description: PGP signature

Re: [gentoo-user] Re: Screen blank on Nvidia GT 610M graphic card

2012-05-23 Thread Seong-ho Cho 
first of all sorry for my poor english :-$

you may check your hardware PCI ID by "lspci -ns 01:00.0".
make sure that like below manual (Link. you can find easily nvidia
download site)
whether your hardware is supported or not.

http://us.download.nvidia.com/XFree86/Linux-x86_64/295.53/README/supportedchips.html

if there is no same pci id, your hardware is not supported yet.

I've met some same problem due to purchase "gtx 560 SE".
so I changed to "gtx 560 Ti" and same problem is resolved.

2012/5/24 du yang :
> Thanks the update, but still get the same problem.
>
> 在 2012-5-24 上午9:45，"Nikos Chantziaras" 写道：
>
>> On 24/05/12 03:51, du yang wrote:
>>>
>>>    Section "Device"
>>>        Identifier "NVidia GeForce GTX 560 Ti"
>>
>>
>> Oops, I forgot to change the ID there.  Try setting it to "NVidia GT
>> 610M", like the Screen section.
>>
>>
>

Re: [gentoo-user] [OT] Thanks to the devs

2012-05-23 Thread Chris Stankevitz 
On Wed, May 23, 2012 at 12:10 PM, Michael Mol  wrote:
> I'd just like to say thank you for the work you guys do.

I'm not sure who the devs are (perhaps Hans), but thank you to all for
your patient help with my Ruby questions.  It's not often that you get
people politely answering questions from the laypeople.

Chris

Re: [gentoo-user] Re: Screen blank on Nvidia GT 610M graphic card

2012-05-23 Thread du yang 
Thanks the update, but still get the same problem.
 在 2012-5-24 上午9:45，"Nikos Chantziaras" 写道：

> On 24/05/12 03:51, du yang wrote:
>
>>Section "Device"
>>Identifier "NVidia GeForce GTX 560 Ti"
>>
>
> Oops, I forgot to change the ID there.  Try setting it to "NVidia GT
> 610M", like the Screen section.
>
>
>

[gentoo-user] Re: Screen blank on Nvidia GT 610M graphic card

2012-05-23 Thread Nikos Chantziaras 

On 24/05/12 03:51, du yang wrote:

Section "Device"
Identifier "NVidia GeForce GTX 560 Ti"


Oops, I forgot to change the ID there.  Try setting it to "NVidia GT 
610M", like the Screen section.

Re: [gentoo-user] Re: Screen blank on Nvidia GT 610M graphic card

2012-05-23 Thread Salvatore Borgia 
this  is the old way
to do the trick, instead this  is an
interesting recent project but I haven't tried it yet.

2012/5/24 du yang 

>
>
> On Thu, May 24, 2012 at 12:38 AM, Salvatore Borgia wrote:
>
>> Hi, have the video card the optimus technology? In this case the "error"
>> that you get is correct, because the video card is not directly connected
>> to the monitor, so you have to configure the intel video card too.
>>
>>
>
> Yes, the card has optimus technology, could you give a detail action what
> I should do?
>
> I tried to compile driver the intel video card (i915), but that let my
> screen blank during boot phase(after udev started). my screen gone back
> after turned off the driver (i915).
>
>
>
> --
> Dreaming my dream!
>

Re: [gentoo-user] Re: Screen blank on Nvidia GT 610M graphic card

2012-05-23 Thread du yang 
On Thu, May 24, 2012 at 12:38 AM, Salvatore Borgia wrote:

> Hi, have the video card the optimus technology? In this case the "error"
> that you get is correct, because the video card is not directly connected
> to the monitor, so you have to configure the intel video card too.
>
>

Yes, the card has optimus technology, could you give a detail action what I
should do?

I tried to compile driver the intel video card (i915), but that let my
screen blank during boot phase(after udev started). my screen gone back
after turned off the driver (i915).



-- 
Dreaming my dream!

Re: [gentoo-user] udevd boot messages

2012-05-23 Thread Pandu Poluan 
On May 24, 2012 5:19 AM, "Alan McKinnon"  wrote:
>
> On Wed, 23 May 2012 22:54:23 +0100
> Markos Chandras  wrote:
>

[znip]

> > Did either of you ever open a bug about this or even discuss it in the
> > gentoo-dev mailing list? What you say sounds like a valid concern to
> > me but unless you express your needs to maintainers, nothing is ever
> > going to happen. However, in this particular case, yes a news item
> > would be the ideal solution.
>
>
> I haven't opened a bug myself, mostly because I've never been bitten
> by this. My Gentoo servers run stable so I've always known from this
> list and other places when something requiring a reboot is coming down
> the line.
>

+1

I love this list :-)

In my previous place, I have one 'experimental' server which gets updated
before all others. It's the 'designated fall guy'.

Which reminds me of Project Management 101: What's the first thing you must
do before embarking on a project? Answer: Designate a fall guy and prepare
implicating evidences. ;-)

> I agree, a news item is the perfect solution. Having portage do it will
> be highly cumbersome, it will require some kind of new magic flag in
> ebuilds that portage must parse. All that work for something that
> doesn't happen often? Nah, it'll never fly.
>

Also a heartfelt +1 for this.

That said, I'm going to repost this 'news' to the Gentoo-server list,
unless someone beats me to it.

Rgds,

Re: [gentoo-user] Re: Screen blank on Nvidia GT 610M graphic card

2012-05-23 Thread du yang 
On Thu, May 24, 2012 at 2:37 AM, Nikos Chantziaras  wrote:

> On 23/05/12 18:59, du yang wrote:
>
>> Hi,
>>
>> I recently bought a new notebook ASUS U31SG which has a nvidia GT 610M
>> graphic card,
>>
>> I always get blank screen (X is running) no matter how i tune the
>> xorg.conf,
>>
>
> Delete your xorg.conf file.  Then, create "/etc/X11/xorg.conf.d/nvidia.**conf"
> with these contents:
>
>
> Section "Device"
>Identifier "NVidia GeForce GTX 560 Ti"
>Driver  "nvidia"
>
> EndSection
>
> Section "Screen"
>Identifier "Screen0"
>Device "NVidia GT 610M"
>DefaultDepth24
>Option "metamodes" "1920x1080 +0+0"
>SubSection "Display"
>Depth  24
>EndSubSection
> EndSection
>
>
> (Replace "1920x1080" with the resolution you want.)
>
> Also make sure to start "nvidia-settings --load-config-only" when starting
> X.  Unfortunately, Gentoo does not do this automatically (like Ubuntu and
> other distros), so you need to do it manually by putting this in
> "/etc/X11/xinit/xinitrc.d/95-**nvidia-settings"
>
>
> #!/bin/sh
> [ -x /opt/bin/nvidia-settings ] &&
>/opt/bin/nvidia-settings --load-config-only > /dev/null 2>&1
>
>
> and make it executable:
>
> $ chmod +x /etc/X11/xinit/xinitrc.d/95-**nvidia-settings
>
>
>

Thanks your help.

but I got error "screen not found" when I try to use it. is there
configuration missing?

[115146.137] (II) LoadModule: "nvidia"
[115146.137] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[115146.138] (II) Module nvidia: vendor="NVIDIA Corporation"
[115146.138] compiled for 4.0.2, module version = 1.0.0
[115146.138] Module class: X.Org Video Driver
[115146.138] (II) NVIDIA dlloader X Driver  295.53  Fri May 11 23:29:56 PDT
2012
[115146.138] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[115146.138] (--) using VT number 7

[115146.140] (EE) No devices detected.
[115146.140]
Fatal server error:
[115146.140] no screens found
[115146.140]



-- 
Dreaming my dream!

Re: [gentoo-user] Re: [entirely ON topic] Thanks to the devs

2012-05-23 Thread Alan McKinnon 
On Wed, 23 May 2012 16:42:15 -0700
walt  wrote:

> On 05/23/2012 12:10 PM, Michael Mol wrote:
> > I've noticed a lot of overt participation on this list by gentoo
> > devs[1], especially in scenarios where they're explaining rationales
> > and reasoning behind changes that affect users.
> > 
> > I'd just like to say thank you for the work you guys do.
> > 
> > Thank you for the work you guys do.
> 
> I posted the same, but a long time ago, so I'll add a mee too.
> 
> (Thanking the suse devs here would of course be very inappropriate ;)

But then you'd be excluding gregkh and *that* would be very
inappropriate ;-) 



-- 
Alan McKinnnon
alan.mckin...@gmail.com

Re: [gentoo-user] [OT] CPU temperature monitoring?

2012-05-23 Thread Alex Schuster 
walt writes:

> Now it's hotter than Hades here and I'm very much aware of
> the fan noise, but I can't tell if the fan is beginning
> to fail (the noise sounds a bit harsh to me) or something
> is merely controlling the speed appropriately.
> 
> The machines BIOS has no settings whatever concerning the
> fan or temperature warnings, etc. so I have no idea how
> to find out the CPU temp.

Strange.

> The k10temp kernel module loads automatically at boot with
> no errors, so I just hope something (somewhere) is taking
> care of this stuff automatically.  But I'm only hoping,
> not knowing.
> 
> Any ideas how to find out for sure?

emerge sys-apps/lm_sensors, run 'sensors-detect', and hopefully the
'sensors' command will show you the fan speeds and temperatures then. And
maybe the output makes sense. Here it does that only partially, this is
what it looks like:

k10temp-pci-00c3
Adapter: PCI adapter
temp1: +9.9°C  (high = +70.0°C)
   (crit = +70.0°C, hyst = +67.0°C)

fam15h_power-pci-00c4
Adapter: PCI adapter
power1:   86.04 W  (crit =  95.04 W)

nct6775-isa-0290
Adapter: ISA adapter
Vcore:+0.93 V  (min =  +0.00 V, max =  +1.74 V)
in1:  +1.66 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
AVCC: +3.30 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
+3.3V:+3.30 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:  +0.06 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:  +1.86 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:  +0.06 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
3VSB: +3.42 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
Vbat: +3.50 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:1155 RPM  (min =0 RPM, div = 8)  ALARM
fan2:1054 RPM  (min =0 RPM, div = 128)  ALARM
fan3: 540 RPM  (min =0 RPM, div = 64)  ALARM
fan4:   0 RPM  (div = 128)
SYSTIN:   +37.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor =
thermistor
CPUTIN:   +37.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor =
thermistor
AUXTIN:  +127.5°C  (high = +80.0°C, hyst = +75.0°C)  ALARM  sensor =
thermistor
cpu0_vid:+0.000 V
intrusion0:  ALARM

Wonko

Re: [gentoo-user] [OT] CPU temperature monitoring?

2012-05-23 Thread Volker Armin Hemmann 
Am Mittwoch, 23. Mai 2012, 16:37:01 schrieb walt:
> I bought this desktop 4-core machine during the coolest part
> of the year and until very recently I could barely hear the
> CPU fan except for about one second during power-up when
> the fan spins way up and then quickly slows down.
> 
> Now it's hotter than Hades here and I'm very much aware of
> the fan noise, but I can't tell if the fan is beginning
> to fail (the noise sounds a bit harsh to me) or something
> is merely controlling the speed appropriately.
> 
> The machines BIOS has no settings whatever concerning the
> fan or temperature warnings, etc. so I have no idea how
> to find out the CPU temp.
> 
> The k10temp kernel module loads automatically at boot with
> no errors, so I just hope something (somewhere) is taking
> care of this stuff automatically.  But I'm only hoping,
> not knowing.
> 
> Any ideas how to find out for sure?

sensors

-- 
#163933

[gentoo-user] Re: [entirely ON topic] Thanks to the devs

2012-05-23 Thread walt 
On 05/23/2012 12:10 PM, Michael Mol wrote:
> I've noticed a lot of overt participation on this list by gentoo
> devs[1], especially in scenarios where they're explaining rationales
> and reasoning behind changes that affect users.
> 
> I'd just like to say thank you for the work you guys do.
> 
> Thank you for the work you guys do.

I posted the same, but a long time ago, so I'll add a mee too.

(Thanking the suse devs here would of course be very inappropriate ;)

[gentoo-user] [OT] CPU temperature monitoring?

2012-05-23 Thread walt 
I bought this desktop 4-core machine during the coolest part
of the year and until very recently I could barely hear the
CPU fan except for about one second during power-up when
the fan spins way up and then quickly slows down.

Now it's hotter than Hades here and I'm very much aware of
the fan noise, but I can't tell if the fan is beginning
to fail (the noise sounds a bit harsh to me) or something
is merely controlling the speed appropriately.

The machines BIOS has no settings whatever concerning the
fan or temperature warnings, etc. so I have no idea how
to find out the CPU temp.

The k10temp kernel module loads automatically at boot with
no errors, so I just hope something (somewhere) is taking
care of this stuff automatically.  But I'm only hoping,
not knowing.

Any ideas how to find out for sure?

Re: [gentoo-user] OT: mount so that other users can write to mounted dir?

2012-05-23 Thread Walter Dnes 
On Wed, May 23, 2012 at 02:42:46AM +0200, Alan McKinnon wrote

> What filesystem is on that stick?
> 
> For vfat and ntfs what you are truing should work.  For Unix file
> systems (ext*, reiser, etc), it will not work. You cannot override
> owners and permissions with the mount command on those.

  Thanks.  That approach won't work in the general case.  I'll probably
have to change the command in my "mdev rules" to something like...

sudo -u waltdnes pmount blah blah blah

...where "waltdnes" is my regular user account.  That'll also allow me
to unmount it with the pumount command from my regular account.

  In the case of my backups to an external USB drive, I have to be root
anyways, so I'll just...

* plug in the external drive
* unmount it after the automount
* remount it manually as root

...and proceed from there.

-- 
Walter Dnes

Re: [gentoo-user] udevd boot messages

2012-05-23 Thread Alan McKinnon 
On Wed, 23 May 2012 22:54:23 +0100
Markos Chandras  wrote:

> On 05/23/2012 10:47 PM, Alan McKinnon wrote:
> > On Wed, 23 May 2012 22:25:37 +0100
> > Markos Chandras  wrote:
> > 
> >> On 05/23/2012 05:24 PM, Tanstaafl wrote:
> >>> On 2012-05-21 5:00 PM, Markos Chandras 
> >>> wrote:
>  On 05/21/2012 03:27 PM, Michael Hampicke wrote:
> >> I updated udev from 171-r5 to 171-r6 and now i get several
> >> udevd boot message as : udevd[1389]: can not find
> >> '/lib/udev/rules.d/90-network.rules': No such file or directory
> >> udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules':
> >> No such file or directory .. and so on.
> >>
> >> /lib is a symlink pointing to /lib64. /lib64/udev/rules.d is ok
> >> with all the rules that udevd does not find at boot.
> >
> > No I would guess it was because of the upgrade of
> > sys-apps/baselayout to 2.1-r1. Things got crazy here with that
> > upgrade. I had to re-merge every package with files under /lib/
> > In your case re-merging udev should to the trick.
> >>>
>  The package clearly informed you that you need to reboot for
>  things to work properly
> 
>  "You should reboot the system now to get /run mounted with
>  tmpfs!"
> 
>  Have a look on pkg_postinst() function in that ebuild. You chose
>  to ignore it and this is why you had these problems after the
>  update.
> >>>
> >>> 
> >>> I asked about this a while back but never got a decent answer...
> >>>
> >>> *Especially* for servers, there really, REALLY needs to be a way
> >>> to see this kind of warning BEFORE updating... ie, the warning
> >>> should be printed to the screen during an 'emerge -pvuDN world' or
> >>> something, so I know that a reboot will be required for this
> >>> update. 
> >>>
> >> This kind of messages are also printed at the end of -uDNav world
> >> so if you scroll your screen up you can see all the warning/log
> >> messages from every package that you have updated. Also, these
> >> kind of messages are logged in /var/log/portage/
> > 
> > You are missing the point.
> > 
> > Tanstaafl wants to know if a reboot *will* be required *before* he
> > does the update. What you are describing tells him that after the
> > update completes when it is already too late.
> > 
> > I face the same issue at work. We have a change policy requiring 14
> > days advance notice of any change affecting service. If I do a
> > routine world update then have to log an emergency change for an
> > unexpected reboot, the change manager will have my nuts for
> > breakfast.
> > 
> > If it happens more than once, I'd be having a really unusual
> > conversation with the CTO which probably ends with him standing
> > behind me watching while I migrate every single box that isn't
> > RHEL6 (all 200 of them) over to RHEL6 where I *do* have exact
> > knowledge in advance of the impact of a change.
> > 
> > 
> > 
> Did either of you ever open a bug about this or even discuss it in the
> gentoo-dev mailing list? What you say sounds like a valid concern to
> me but unless you express your needs to maintainers, nothing is ever
> going to happen. However, in this particular case, yes a news item
> would be the ideal solution.


I haven't opened a bug myself, mostly because I've never been bitten
by this. My Gentoo servers run stable so I've always known from this
list and other places when something requiring a reboot is coming down
the line.

I agree, a news item is the perfect solution. Having portage do it will
be highly cumbersome, it will require some kind of new magic flag in
ebuilds that portage must parse. All that work for something that
doesn't happen often? Nah, it'll never fly.


 
-- 
Alan McKinnnon
alan.mckin...@gmail.com

Re: [gentoo-user] udevd boot messages

2012-05-23 Thread Markos Chandras 
On 05/23/2012 10:47 PM, Alan McKinnon wrote:
> On Wed, 23 May 2012 22:25:37 +0100
> Markos Chandras  wrote:
> 
>> On 05/23/2012 05:24 PM, Tanstaafl wrote:
>>> On 2012-05-21 5:00 PM, Markos Chandras  wrote:
 On 05/21/2012 03:27 PM, Michael Hampicke wrote:
>> I updated udev from 171-r5 to 171-r6 and now i get several udevd
>>   boot message as : udevd[1389]: can not find
>> '/lib/udev/rules.d/90-network.rules': No such file or directory
>> udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules': No
>> such file or directory .. and so on.
>>
>> /lib is a symlink pointing to /lib64. /lib64/udev/rules.d is ok
>> with all the rules that udevd does not find at boot.
>
> No I would guess it was because of the upgrade of
> sys-apps/baselayout to 2.1-r1. Things got crazy here with that
> upgrade. I had to re-merge every package with files under /lib/ In
>   your case re-merging udev should to the trick.
>>>
 The package clearly informed you that you need to reboot for
 things to work properly

 "You should reboot the system now to get /run mounted with tmpfs!"

 Have a look on pkg_postinst() function in that ebuild. You chose to
 ignore it and this is why you had these problems after the update.
>>>
>>> 
>>> I asked about this a while back but never got a decent answer...
>>>
>>> *Especially* for servers, there really, REALLY needs to be a way to
>>> see this kind of warning BEFORE updating... ie, the warning should
>>> be printed to the screen during an 'emerge -pvuDN world' or
>>> something, so I know that a reboot will be required for this update.
>>> 
>>>
>> This kind of messages are also printed at the end of -uDNav world so
>> if you scroll your screen up you can see all the warning/log messages
>> from every package that you have updated. Also, these kind of
>> messages are logged in /var/log/portage/
> 
> You are missing the point.
> 
> Tanstaafl wants to know if a reboot *will* be required *before* he does
> the update. What you are describing tells him that after the update
> completes when it is already too late.
> 
> I face the same issue at work. We have a change policy requiring 14
> days advance notice of any change affecting service. If I do a routine
> world update then have to log an emergency change for an unexpected
> reboot, the change manager will have my nuts for breakfast.
> 
> If it happens more than once, I'd be having a really unusual
> conversation with the CTO which probably ends with him standing behind
> me watching while I migrate every single box that isn't RHEL6 (all 200
> of them) over to RHEL6 where I *do* have exact knowledge in advance of
> the impact of a change.
> 
> 
> 
Did either of you ever open a bug about this or even discuss it in the
gentoo-dev mailing list? What you say sounds like a valid concern to me
but unless you express your needs to maintainers, nothing is ever going
to happen. However, in this particular case, yes a news item would be
the ideal solution.

-- 
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2

Re: [gentoo-user] udevd boot messages

2012-05-23 Thread Alan McKinnon 
On Wed, 23 May 2012 22:25:37 +0100
Markos Chandras  wrote:

> On 05/23/2012 05:24 PM, Tanstaafl wrote:
> > On 2012-05-21 5:00 PM, Markos Chandras  wrote:
> >> On 05/21/2012 03:27 PM, Michael Hampicke wrote:
>  I updated udev from 171-r5 to 171-r6 and now i get several udevd
>    boot message as : udevd[1389]: can not find
>  '/lib/udev/rules.d/90-network.rules': No such file or directory
>  udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules': No
>  such file or directory .. and so on.
> 
>  /lib is a symlink pointing to /lib64. /lib64/udev/rules.d is ok
>  with all the rules that udevd does not find at boot.
> >>>
> >>> No I would guess it was because of the upgrade of
> >>> sys-apps/baselayout to 2.1-r1. Things got crazy here with that
> >>> upgrade. I had to re-merge every package with files under /lib/ In
> >>>   your case re-merging udev should to the trick.
> > 
> >> The package clearly informed you that you need to reboot for
> >> things to work properly
> >>
> >> "You should reboot the system now to get /run mounted with tmpfs!"
> >>
> >> Have a look on pkg_postinst() function in that ebuild. You chose to
> >> ignore it and this is why you had these problems after the update.
> > 
> > 
> > I asked about this a while back but never got a decent answer...
> > 
> > *Especially* for servers, there really, REALLY needs to be a way to
> > see this kind of warning BEFORE updating... ie, the warning should
> > be printed to the screen during an 'emerge -pvuDN world' or
> > something, so I know that a reboot will be required for this update.
> > 
> > 
> This kind of messages are also printed at the end of -uDNav world so
> if you scroll your screen up you can see all the warning/log messages
> from every package that you have updated. Also, these kind of
> messages are logged in /var/log/portage/

You are missing the point.

Tanstaafl wants to know if a reboot *will* be required *before* he does
the update. What you are describing tells him that after the update
completes when it is already too late.

I face the same issue at work. We have a change policy requiring 14
days advance notice of any change affecting service. If I do a routine
world update then have to log an emergency change for an unexpected
reboot, the change manager will have my nuts for breakfast.

If it happens more than once, I'd be having a really unusual
conversation with the CTO which probably ends with him standing behind
me watching while I migrate every single box that isn't RHEL6 (all 200
of them) over to RHEL6 where I *do* have exact knowledge in advance of
the impact of a change.



-- 
Alan McKinnnon
alan.mckin...@gmail.com

Re: [gentoo-user] udevd boot messages

2012-05-23 Thread Markos Chandras 
On 05/23/2012 05:24 PM, Tanstaafl wrote:
> On 2012-05-21 5:00 PM, Markos Chandras  wrote:
>> On 05/21/2012 03:27 PM, Michael Hampicke wrote:
 I updated udev from 171-r5 to 171-r6 and now i get several udevd
   boot message as : udevd[1389]: can not find
 '/lib/udev/rules.d/90-network.rules': No such file or directory
 udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules': No
 such file or directory .. and so on.

 /lib is a symlink pointing to /lib64. /lib64/udev/rules.d is ok
 with all the rules that udevd does not find at boot.
>>>
>>> No I would guess it was because of the upgrade of
>>> sys-apps/baselayout to 2.1-r1. Things got crazy here with that
>>> upgrade. I had to re-merge every package with files under /lib/ In
>>>   your case re-merging udev should to the trick.
> 
>> The package clearly informed you that you need to reboot for things to
>> work properly
>>
>> "You should reboot the system now to get /run mounted with tmpfs!"
>>
>> Have a look on pkg_postinst() function in that ebuild. You chose to
>> ignore it and this is why you had these problems after the update.
> 
> 
> I asked about this a while back but never got a decent answer...
> 
> *Especially* for servers, there really, REALLY needs to be a way to see
> this kind of warning BEFORE updating... ie, the warning should be
> printed to the screen during an 'emerge -pvuDN world' or something, so I
> know that a reboot will be required for this update.
> 
> 
This kind of messages are also printed at the end of -uDNav world so if
you scroll your screen up you can see all the warning/log messages from
every package that you have updated. Also, these kind of messages are
logged in /var/log/portage/

-- 
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2

Re: [gentoo-user] [OT] Thanks to the devs

2012-05-23 Thread Davide Carnovale 
+1
thank you guys!

D

2012/5/23 Michael Mol 

> I've noticed a lot of overt participation on this list by gentoo
> devs[1], especially in scenarios where they're explaining rationales
> and reasoning behind changes that affect users.
>
> I'd just like to say thank you for the work you guys do.
>
> Thank you for the work you guys do.
>
> There. I said it. *Goes back to work*
>
> [1] Perhaps they were already participating, and I didn't notice they were
> devs.
>
> --
> :wq
>
>

[gentoo-user] [OT] Thanks to the devs

2012-05-23 Thread Michael Mol 
I've noticed a lot of overt participation on this list by gentoo
devs[1], especially in scenarios where they're explaining rationales
and reasoning behind changes that affect users.

I'd just like to say thank you for the work you guys do.

Thank you for the work you guys do.

There. I said it. *Goes back to work*

[1] Perhaps they were already participating, and I didn't notice they were devs.

-- 
:wq

[gentoo-user] Re: Understanding new ruby dependencies

2012-05-23 Thread Hans de Graaff 
On Tue, 22 May 2012 23:35:21 -0700, Chris Stankevitz wrote:

> 1. What on my system is insisting on make.conf RUBY 1.9 USE_EXPAND
> changes?  An emerge --tree is not giving me a clear answer (as it
> usually does).  The original post in this thread provides a pastebin
> link to back up this claim.

It is implicit. dev-lang/ruby:1.9 requires a new enough version of rdoc 
with this particular USE flag enabled.

> 2. If the answer to (1) is "the gentoo system itself", then why doesn't
> "the gentoo system itself" update the USE_EXPAND by adding a reference
> to ruby19?  It appears "the gentoo system itself" presently only enables
> the ruby18 USE_EXPAND.
>   base $ find /usr/portage/profiles/ | xargs grep RUBY_TARGETS=
>   /usr/portage/profiles/base/make.defaults:RUBY_TARGETS="ruby18"

Right. We'll add ruby19 to that shortly. The reason we did not do that 
before was that we wanted to ease into ruby19, but there seem to be 
plenty of people that have a package depending on dev-lang/ruby on their 
system, so that plan didn't work very well.

> 4. I run a "stable" system that is somehow insisting on ruby19.  This
> webpage http://www.gentoo.org/proj/en/prog_lang/ruby/index.xml  says
> ruby19 is not for use on production systems.  Why the disconnect?
> Perhaps the ruby page is just out of date.

Correct conclusion, and I've just updated it for the various ruby 
implementations.

> Thank you for listening to me list the issues I am ignorant on.  Now I'm
> going to add RUBY_TARGETS="ruby19" to my make.conf and hope things "just
> work".

At this point I would recommend RUBY_TARGETS="ruby18 ruby19".

Kind regards,

Hans

[gentoo-user] Re: Screen blank on Nvidia GT 610M graphic card

2012-05-23 Thread Nikos Chantziaras 

On 23/05/12 18:59, du yang wrote:

Hi,

I recently bought a new notebook ASUS U31SG which has a nvidia GT 610M
graphic card,

I always get blank screen (X is running) no matter how i tune the
xorg.conf,


Delete your xorg.conf file.  Then, create 
"/etc/X11/xorg.conf.d/nvidia.conf" with these contents:



Section "Device"
Identifier "NVidia GeForce GTX 560 Ti"
Driver  "nvidia"
EndSection

Section "Screen"
Identifier "Screen0"
Device "NVidia GT 610M"
DefaultDepth24
Option "metamodes" "1920x1080 +0+0"
SubSection "Display"
Depth  24
EndSubSection
EndSection


(Replace "1920x1080" with the resolution you want.)

Also make sure to start "nvidia-settings --load-config-only" when 
starting X.  Unfortunately, Gentoo does not do this automatically (like 
Ubuntu and other distros), so you need to do it manually by putting this 
in "/etc/X11/xinit/xinitrc.d/95-nvidia-settings"



#!/bin/sh
[ -x /opt/bin/nvidia-settings ] &&
/opt/bin/nvidia-settings --load-config-only > /dev/null 2>&1


and make it executable:

$ chmod +x /etc/X11/xinit/xinitrc.d/95-nvidia-settings

Re: [gentoo-user] udevd boot messages

2012-05-23 Thread Tanstaafl 

On 2012-05-23 12:49 PM, Alex Schuster  wrote:

Tanstaafl writes:


*Especially* for servers, there really, REALLY needs to be a way to see
this kind of warning BEFORE updating... ie, the warning should be
printed to the screen during an 'emerge -pvuDN world' or something, so
I know that a reboot will be required for this update.



Indeed! I think eselect news read should show this, at least.


That would work for me... anytime I saw an update for system critical 
stuff (like baselayout or udev or openrc) I'd be sure to check things...


As it stands, I'm now very glad for my self imposed policy of waiting a 
few days for critical things like this...

Re: [gentoo-user] udevd boot messages

2012-05-23 Thread Alex Schuster 
Tanstaafl writes:

> *Especially* for servers, there really, REALLY needs to be a way to see 
> this kind of warning BEFORE updating... ie, the warning should be 
> printed to the screen during an 'emerge -pvuDN world' or something, so
> I know that a reboot will be required for this update.
> 

Indeed! I think eselect news read should show this, at least.

Wonko

Re: [gentoo-user] udevd boot messages

2012-05-23 Thread Tanstaafl 

On 2012-05-21 5:00 PM, Markos Chandras  wrote:

On 05/21/2012 03:27 PM, Michael Hampicke wrote:

I updated udev from 171-r5 to 171-r6 and now i get several udevd
  boot message as : udevd[1389]: can not find
'/lib/udev/rules.d/90-network.rules': No such file or directory
udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules': No
such file or directory .. and so on.

/lib is a symlink pointing to /lib64. /lib64/udev/rules.d is ok
with all the rules that udevd does not find at boot.


No I would guess it was because of the upgrade of
sys-apps/baselayout to 2.1-r1. Things got crazy here with that
upgrade. I had to re-merge every package with files under /lib/ In
  your case re-merging udev should to the trick.



The package clearly informed you that you need to reboot for things to
work properly

"You should reboot the system now to get /run mounted with tmpfs!"

Have a look on pkg_postinst() function in that ebuild. You chose to
ignore it and this is why you had these problems after the update.



I asked about this a while back but never got a decent answer...

*Especially* for servers, there really, REALLY needs to be a way to see 
this kind of warning BEFORE updating... ie, the warning should be 
printed to the screen during an 'emerge -pvuDN world' or something, so I 
know that a reboot will be required for this update.

[gentoo-user] Re: Screen blank on Nvidia GT 610M graphic card

2012-05-23 Thread du yang 
more information,

I have configure the kernel follow this guide,
http://www.gentoo.org/doc/en/nvidia-guide.xml


On Wed, May 23, 2012 at 11:59 PM, du yang  wrote:

> Hi,
>
> I recently bought a new notebook ASUS U31SG which has a nvidia GT 610M
> graphic card,
>
> I always get blank screen (X is running) no matter how i tune the
> xorg.conf,
>
> if there is no xorg.conf, X will be running smoothly with WM, though the
> monitor resolution is a bit lower.
>
> Anyone meet the same problem or know how to fix it?
>
> Many thanks in advance.
>
> Driver version:
> nvidia-drivers-295.53
>
> Here is my current /etc/X11/xorg.conf,
>
> 
>
> Section "ServerLayout"
> Identifier "X.org Configured"
> Screen  0  "Screen0" 0 0
> InputDevice"Mouse0" "CorePointer"
> InputDevice"Keyboard0" "CoreKeyboard"
> EndSection
>
> Section "Files"
> ModulePath  "/usr/lib64/xorg/modules"
> FontPath"/usr/share/fonts/misc/"
> FontPath"/usr/share/fonts/TTF/"
> FontPath"/usr/share/fonts/OTF/"
> FontPath"/usr/share/fonts/Type1/"
> FontPath"/usr/share/fonts/100dpi/"
> FontPath"/usr/share/fonts/75dpi/"
> FontPath"/usr/share/fonts/truetype/"
> EndSection
>
> Section "Module"
> #Load   "ddc"
> #Load   "dbe"
> #Load   "vbe"
> #Load   "bitmap"
> #Load   "type1"
> #Load   "freetype"
> Load   "glx"
> #Load   "extmod"
> #Load   "record"
> Disable "dri"
> Disable "dri2"
> EndSection
>
> Section "ServerFlags"
> Option "AllowEmptyInput" "false"
> Option "AllowMouseOpenFail" "true"
> Option "Xinerama" "0"
> EndSection
>
> Section "InputDevice"
> Identifier "Keyboard0"
> Driver "evdev"
> Option "CoreKeyboard"
> Option "XkbRules" "xorg"
> Option "XkbModel" "endev"
> Option "XkbOptions"
> "grp:toggle,grp_led:scroll,terminate:ctrl_alt_bksp"
> Option "XkbVariant" ",winkeys"
> Option "XkbLayOut" "us"
> EndSection
>
> Section "InputDevice"
> Identifier "Mouse0"
> Driver "evdev"
> Option "Protocol" "auto"
> Option "Device" "/dev/input/mice"
> Option "ZAxisMapping" "4 5 6 7"
> EndSection
>
> Section "Monitor"
> Identifier "Monitor0"
> VendorName "Monitor Vendor"
> ModelName  "Monitor Model"
> Option "DPMS"
> #HorizSync  30-50
> #VertRefresh50-100
> # 1368x768 @ 60.00 Hz (GTF) hsync: 47.70 kHz; pclk: 85.86 MHz
> #Modeline "1368x768_60.00"  85.86  1368 1440 1584 1800  768 769 772
> 795  -HSync +Vsync
> Option "ConnectedMonitor" "DFP-0"
> Option "CustomEDID" "DFP-0:/etc/X11/edid.bin"
> EndSection
>
> Section "Device"
> Identifier "Card0"
> Driver "nvidia"
> Option "UseDisplayDevice" "DFP-0"
> Option "HWCursor" "false"
> BusID  "PCI:1:0:0"
> EndSection
>
> Section "Screen"
> Identifier "Screen0"
> Device "Card0"
> Monitor"Monitor0"
> DefaultDepth32
> #Option "TwinView" "0"
> #Option "TwinViewXinramaInfoOrder" "DFP-0"
> #Option "metamodes" "nvidia-auto-select +0+0"
> SubSection "Display"
> #Viewport0 0
> Depth   32
> Modes  "1366x768_60"
> EndSubSection
> EndSection
>
>
>
> my Xorg.0.log, there is no errors..
>
> ---
> [   543.167]
> X.Org X Server 1.12.1
> Release Date: 2012-04-13
> [   543.169] X Protocol Version 11, Revision 0
> [   543.169] Build Operating System: Linux 3.3.5-gentoo x86_64 Gentoo
> [   543.169] Current Operating System: Linux omega 3.3.5-gentoo #23 SMP
> Mon May 21 01:01:18 CST 2012 x86_64
> [   543.170] Kernel command line: root=/dev/sda3 rootfstype=ext4
> video=uvesafb:mtrr:3,ywrap,1024x768-32@60 console=tty1 quiet
> [   543.170] Build Date: 19 May 2012  10:17:30AM
> [   543.171]
> [   543.171] Current version of pixman: 0.24.4
> [   543.172] Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> [   543.173] Markers: (--) probed, (**) from config file, (==) default
> setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [   543.175] (==) Log file: "/var/log/Xorg.0.log", Time: Wed May 23
> 00:35:59 2012
> [   543.175] (==) Using config file: "/etc/X11/xorg.conf"
> [   543.176] (==) Using system config directory
> "/usr/share/X11/xorg.conf.d"
> [   543.177] (==) ServerLayout "X.org Configured"
> [   543.177] (**) |-->Screen "Screen0" (0)
> [   543.177

[gentoo-user] Screen blank on Nvidia GT 610M graphic card

2012-05-23 Thread du yang 
Hi,

I recently bought a new notebook ASUS U31SG which has a nvidia GT 610M
graphic card,

I always get blank screen (X is running) no matter how i tune the
xorg.conf,

if there is no xorg.conf, X will be running smoothly with WM, though the
monitor resolution is a bit lower.

Anyone meet the same problem or know how to fix it?

Many thanks in advance.

Driver version:
nvidia-drivers-295.53

Here is my current /etc/X11/xorg.conf,


Section "ServerLayout"
Identifier "X.org Configured"
Screen  0  "Screen0" 0 0
InputDevice"Mouse0" "CorePointer"
InputDevice"Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
ModulePath  "/usr/lib64/xorg/modules"
FontPath"/usr/share/fonts/misc/"
FontPath"/usr/share/fonts/TTF/"
FontPath"/usr/share/fonts/OTF/"
FontPath"/usr/share/fonts/Type1/"
FontPath"/usr/share/fonts/100dpi/"
FontPath"/usr/share/fonts/75dpi/"
FontPath"/usr/share/fonts/truetype/"
EndSection

Section "Module"
#Load   "ddc"
#Load   "dbe"
#Load   "vbe"
#Load   "bitmap"
#Load   "type1"
#Load   "freetype"
Load   "glx"
#Load   "extmod"
#Load   "record"
Disable "dri"
Disable "dri2"
EndSection

Section "ServerFlags"
Option "AllowEmptyInput" "false"
Option "AllowMouseOpenFail" "true"
Option "Xinerama" "0"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "evdev"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "endev"
Option "XkbOptions"
"grp:toggle,grp_led:scroll,terminate:ctrl_alt_bksp"
Option "XkbVariant" ",winkeys"
Option "XkbLayOut" "us"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "evdev"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName  "Monitor Model"
Option "DPMS"
#HorizSync  30-50
#VertRefresh50-100
# 1368x768 @ 60.00 Hz (GTF) hsync: 47.70 kHz; pclk: 85.86 MHz
#Modeline "1368x768_60.00"  85.86  1368 1440 1584 1800  768 769 772
795  -HSync +Vsync
Option "ConnectedMonitor" "DFP-0"
Option "CustomEDID" "DFP-0:/etc/X11/edid.bin"
EndSection

Section "Device"
Identifier "Card0"
Driver "nvidia"
Option "UseDisplayDevice" "DFP-0"
Option "HWCursor" "false"
BusID  "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor"Monitor0"
DefaultDepth32
#Option "TwinView" "0"
#Option "TwinViewXinramaInfoOrder" "DFP-0"
#Option "metamodes" "nvidia-auto-select +0+0"
SubSection "Display"
#Viewport0 0
Depth   32
Modes  "1366x768_60"
EndSubSection
EndSection



my Xorg.0.log, there is no errors..
---
[   543.167]
X.Org X Server 1.12.1
Release Date: 2012-04-13
[   543.169] X Protocol Version 11, Revision 0
[   543.169] Build Operating System: Linux 3.3.5-gentoo x86_64 Gentoo
[   543.169] Current Operating System: Linux omega 3.3.5-gentoo #23 SMP Mon
May 21 01:01:18 CST 2012 x86_64
[   543.170] Kernel command line: root=/dev/sda3 rootfstype=ext4
video=uvesafb:mtrr:3,ywrap,1024x768-32@60 console=tty1 quiet
[   543.170] Build Date: 19 May 2012  10:17:30AM
[   543.171]
[   543.171] Current version of pixman: 0.24.4
[   543.172] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   543.173] Markers: (--) probed, (**) from config file, (==) default
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   543.175] (==) Log file: "/var/log/Xorg.0.log", Time: Wed May 23
00:35:59 2012
[   543.175] (==) Using config file: "/etc/X11/xorg.conf"
[   543.176] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   543.177] (==) ServerLayout "X.org Configured"
[   543.177] (**) |-->Screen "Screen0" (0)
[   543.177] (**) |   |-->Monitor "Monitor0"
[   543.177] (**) |   |-->Device "Card0"
[   543.177] (**) |-->Input Device "Mouse0"
[   543.177] (**) |-->Input Device "Keyboard0"
[   543.177] (==) Automatically adding devices
[   543.177] (==) Automatically enabling devices
[   543.177] (**) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,

Re: [gentoo-user] Re: Understanding new ruby dependencies

2012-05-23 Thread Chris Stankevitz 
On Tue, May 22, 2012 at 11:35 PM, Hans de Graaff  wrote:
> For now this should be
>
> RUBY_TARGETS="ruby18 ruby19"

As you all suspected, I updated /etc/make.conf, "emerge --newuse
--deep world && emerge -Du world" and all is well.  Here are the lines
I added:

# 2012-MAY-22 ruby19 is required but is not in the profile (yet)
RUBY_TARGETS="ruby18 ruby19"

Thank you all,

Chris

Re: [gentoo-user] Issues with >=x11-drivers/xf86-video-ati-6.14.4: driver issue or hardware issue?

2012-05-23 Thread Michael Scherer 
- Original Message - 
From: "Andrey Moshbear" 

To: "gentoo-user" 
Sent: Tuesday, 22 May, 2012 08:02
Subject: [gentoo-user] Issues with >=x11-drivers/xf86-video-ati-6.14.4: driver 
issue or hardware issue?



Lately, I've been having some issues with segfaults when running
startx and it's been pretty persistent.

Xorg.0.log and emerge --info are available at https://gist.github.com/2766926 .
Kernel config is available at https://gist.github.com/276943 .

I've tried downgrading, but <=x11-drivers/xf86-video-ati-6.14.2 fails
to compile due to incomplete structs.

Is this more a driver or a hardware issue?

--
001100 m0shbear
010010
00 andrey at moshbear dot net
11 andrey dot vul at gmail
101101
110011




first thing thing is your usage of ACCEPT_KEYWORDS="amd64 ~amd64". with ~amd64 
you globally
allow all packages masked for amd64. unless you are a developer/tester for 
gentoo you should remove
this keyword, because gentoo usually has good reasons to mask some packages. if 
for some reason you
really need a masked package, you can do this easily only for that package.
global unmasking alone might be the reason for half of your troubles.

second, it is advisable to use kernel modesetting, which is obviously not 
enabled. gentoo has a detailed
howto for this under http://www.gentoo.org/doc/en/xorg-config.xml. this gives 
you all necessary details.

just a quick shot for the moment. your kernel config doesn't under the link you 
give, I'd like to see that
too, and maybe /etc/X11/xorg.conf or the contents of /etc/X11/xorg.conf.d, if 
you have any of these,

regards, nichael

Re: [gentoo-user] Re: Understanding new ruby dependencies

2012-05-23 Thread kwkhui 
On Tue, 22 May 2012 23:35:21 -0700
Chris Stankevitz  wrote:

> On Tue, May 22, 2012 at 10:13 PM,   wrote:
> > I suggest keeping an eye on ${PORTDIR}/profiles/desc directory too.
> > This is where every one of the USE_EXPAND variables is explained in
> > details.
> 
> Thank you for all your patient help.  I've been using Gentoo for years
> and for some reason this RUBY thing has me flustered.
> 
> 1. What on my system is insisting on make.conf RUBY 1.9 USE_EXPAND
> changes?  An emerge --tree is not giving me a clear answer (as it
> usually does).  The original post in this thread provides a pastebin
> link to back up this claim.

Basically the newslot upgrade ruby 1.8.x -> 1.9.x.

For example, you can see that in
${PORTDIR}/dev-ruby/json/json-1.5.4-r1.ebuild there is the line

PDEPEND="
rdoc? ( >=dev-ruby/rdoc-3.9.4[ruby_targets_ruby19] )
xemacs? ( app-xemacs/ruby-modes )"

Previously in json-1.5.4.ebuild there is no such check, as you can
diff for yourself.

> 2. If the answer to (1) is "the gentoo system itself", then why
> doesn't "the gentoo system itself" update the USE_EXPAND by adding a
> reference to ruby19?  It appears "the gentoo system itself" presently
> only enables the ruby18 USE_EXPAND.
>   base $ find /usr/portage/profiles/ | xargs grep RUBY_TARGETS=
>   /usr/portage/profiles/base/make.defaults:RUBY_TARGETS="ruby18"

That is usual... profile changes lag behind the ebuild changes.

> 4. I run a "stable" system that is somehow insisting on ruby19.  This
> webpage http://www.gentoo.org/proj/en/prog_lang/ruby/index.xml  says
> ruby19 is not for use on production systems.  Why the disconnect?
> Perhaps the ruby page is just out of date.

I suppose ruby19 is in a state similar to python3 --- not ready to be
default since *something* break, but it has been out long enough to be 
considered "stable".

> 5. I have no idea what RUBY is and have never installed it directly.
> Yet I have to understand RUBY USE_EXPANDs which seem to be described
> only in the RUBY installation guide, gentoo dev manual, or in ebuild
> scripting guides.  I am a gentoo "layperson" in general and am
> completely clueless about RUBY in particular.  I believe talk about
> this "required and automatically installed package" should appear not
> in obscure dev documentation, but in the handbook.  Perhaps with more
> time/volunteers this would have happened.

TBH, I'm not a ruby person either.  The only thing here on my system
that pulls in ruby is dev-texlive/texlive-pictures, plus I need ruby
for some random scripts I pulled from the web (which I could have
rewritten in python or bash but I can't be bothered).

> 6. Why does emerge insist on me adding USE="ruby_targets_ruby19" to a
> bunch of projects, yet the users of this group recommend a change in
> make.conf?  I suspect the disconnect that the two approaches are
> equivalent, just emerge does not have the "street smarts" to recommend
> the proper change.

That is how ebuild (and hence portage) works --- it didn't check
RUBY_TARGETS but instead the specified use flags for dependencies
specified the ebuild. Hence the error message is "add use flag bar to
package foo, regardless of whether bar is actually an expanded flag.  As
you see in the example above json ebuild tells portage to check
dev-ruby/rdoc is built with ruby_targets_ruby19 use flag (which is what
RUBY_TARGETS=ruby19 would have expanded to) enabled and so that is what
portage did (and screamed when it can't).

Kerwin.


signature.asc
Description: PGP signature

[gentoo-user] Re: Understanding new ruby dependencies

2012-05-23 Thread Hans de Graaff 
On Tue, 22 May 2012 18:10:18 -0700, Chris Stankevitz wrote:

> On Tue, May 22, 2012 at 11:32 AM,   wrote:
>> No!  Don't do that!  Instead, you should add a line
>>
>> RUBY_TARGETS=ruby19

For now this should be

RUBY_TARGETS="ruby18 ruby19"

We currently don't support running with ruby19 only. It might work, we 
just don't support it. :-)

> f) [your idea here]

f) It should just have worked.

I tried to be conservative and not add ruby19 in RUBY_TARGETS right away, 
but as you have noticed this causes problems for rdoc and friends. I'll 
add ruby19 to the default setting in the profile within a few days so 
that this problem goes away.

Kind regards,

Hans