Bug 237824 – app-portage/autounmask - Unsuccessful stat on filename containing newline at /usr/bin/autounmask line 304.

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Bartosz Krzeszewski 2008-09-16 11:14:47 UTC]

ESPRIMO etc # autounmask x11-base/xorg-x11-7.4

 autounmask version 0.21 (using PortageXS-0.02.07 and portage-2.1.4.4)

Unsuccessful stat on filename containing newline at /usr/bin/autounmask line 304.
Unsuccessful stat on filename containing newline at /usr/bin/autounmask line 307.
Unsuccessful stat on filename containing newline at /usr/bin/autounmask line 304.
Unsuccessful stat on filename containing newline at /usr/bin/autounmask line 307.
 * Using repository: /usr/portage

 * Using package.keywords file: /etc/portage/package.keywords
 * Using package.unmask file: /etc/portage/package.unmask

 * Unmasking x11-base/xorg-x11-7.4 and its dependencies.. this might take a while..

 * Added '=x11-base/xorg-x11-7.4 ~' to /etc/portage/package.keywords
 * Added '=x11-base/xorg-x11-7.4 ~' to /etc/portage/package.keywords
 * Added '=x11-base/xorg-x11-7.4 ~' to /etc/portage/package.keywords
 * Added '=x11-base/xorg-x11-7.4 ~' to /etc/portage/package.keywords

[Comment 1 Jeroen Roovers (RETIRED) 2008-09-16 12:53:04 UTC]

So, er, what do you think is the bug? I'm going for a descriptive summary here. :)

[Comment 2 Bartosz Krzeszewski 2008-09-16 17:43:53 UTC]

Autounmask is adding the same ebuil in endless loop into /etc/portage/package.keywords

and what about "Unsuccessful stat on filename containing newline at /usr/bin/autounmask line
304."?

[Comment 3 Jeroen Roovers (RETIRED) 2008-09-16 21:56:15 UTC]

Please post your `emerge --info' too.

[Comment 4 Christian Hartmann (RETIRED) 2008-09-17 07:16:52 UTC]

Upgrading to PortageXS-0.02.08 should fix it.

[Comment 5 Bartosz Krzeszewski 2008-09-17 11:33:01 UTC]

(In reply to comment #4)
> Upgrading to PortageXS-0.02.08 should fix it.
> 

PortageXS-0.02.08 fixed endless loop but there is still problem with
Unsuccessful stat on filename containing newline at /usr/bin/autounmask line 304.
Unsuccessful stat on filename containing newline at /usr/bin/autounmask line 307.
Unsuccessful stat on filename containing newline at /usr/bin/autounmask line 304.
Unsuccessful stat on filename containing newline at /usr/bin/autounmask line 307.

[Comment 6 Bartosz Krzeszewski 2008-09-17 11:34:50 UTC]

Created attachment 165631 [details]
emerge --info

[Comment 7 Aniruddha 2008-09-17 15:20:13 UTC]

I encountered the same bug with app-portage/autounmask when I upgraded to portage 2.2 

[Comment 8 Antti Mäkelä 2008-10-05 16:31:10 UTC]

I'm getting the Unsuccesful stats with portage  2.1.4.4. 

Also, trying to autounmask kde-base/kde-meta-4.1.2 (at least now while it's still hard-masked) yields nothing..

[Comment 9 Wonko 2008-10-10 03:04:39 UTC]

Having the same problems.

"Unsuccessful stat..." messages come from $curPath containing a newline, it looks like "/usr/portage/profiles/default/linux/x86/2008.0/desktop/..
../../../../../targets/desktop", with the newline being after the first "..".

Autounmasking kde-base/kde-meta-4.1.2 works fine after upgrade of PortageXS to 0.02.08.

[Comment 10 Antti Mäkelä 2008-10-10 21:29:28 UTC]

(In reply to comment #9)
> Autounmasking kde-base/kde-meta-4.1.2 works fine after upgrade of PortageXS to
> 0.02.08.
> 

Not for me.

Or rather, the weird part is this:

 autounmask version 0.21 (using PortageXS-0.02.07 and portage-2.1.4.5)

...even though I just updated PortageXS to 0.02.08!

[Comment 11 Manfred Knick 2008-11-13 09:26:08 UTC]

(In reply to comment #10)
> (In reply to comment #9)

> Or rather, the weird part is this:
>  autounmask version 0.21 (using PortageXS-0.02.07 and portage-2.1.4.5)
> ...even though I just updated PortageXS to 0.02.08!

YES,weird indeed - 

4 lines of "Unsuccessful stat on filename containing newline ..." 
still remain at the beginning,

but after a reboot, e.g. "autounmask -p  =kde-base/kde-meta-3.5.10" works ...

[Comment 12 Sebastian Pipping 2008-11-18 17:26:18 UTC]

(In reply to comment #4)
> Upgrading to PortageXS-0.02.08 should fix it.

I think you should still try to fix it.

Is there more to do than building a set of strings and skipping verything already in there?

Thanks in advance.

[Comment 13 Christian Hartmann (RETIRED) 2008-12-01 20:56:39 UTC]

Please upgrade to autounmask 0.23 (which will pull in PortageXS 0.02.09 which now contains the fixed functions).