Bugzilla Bug 216484

s939 ~ # autounmask gnome-base/gnome-2.22.0

 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/autounmask-gnome
 * Using package.unmask file: /etc/portage/package.unmask/autounmask-gnome

 * Unmasking gnome-base/gnome-2.22.0 and its dependencies.. this might take a
while..

 * Added '=gnome-base/gnome-2.22.0 ~' to
/etc/portage/package.keywords/autounmask-gnome
 * Added '=gnome-base/gnome-2.22.0 ~' to
/etc/portage/package.keywords/autounmask-gnome
 * Added '=gnome-base/gnome-2.22.0 ~' to
/etc/portage/package.keywords/autounmask-gnome
^C * Aborting due to user interrupt!
 * Restoring files because autounmask was called with the --pretend option.
 * done!

s939 ~ # 

Exiting on signal 2

s939 ~ # cat /etc/portage/package.keywords/autounmask-gnome 

# ---
# BEGIN: gnome-base/gnome-2.22.0
# ---
=gnome-base/gnome-2.22.0 ~
=gnome-base/gnome-2.22.0 ~
=gnome-base/gnome-2.22.0 ~

Created an attachment (id=148822) [details]
emerge --info

I've got the same problem here, with any package. I think it's because with
2008.0 profile (amd64/desktop), every package on portage start with a "*" i.e.
:

bluecat@Freija ~ $ eix gentoo-source
[D] sys-kernel/gentoo-sources
     Available versions:  
        (2.6.16-r13)    *2.6.16-r13
        (2.6.19-r5)     *2.6.19-r5
        (2.6.20-r10)    ~*2.6.20-r10
        (2.6.22-r10)    *2.6.22-r10
        (2.6.23-r9)     *2.6.23-r9
        (2.6.24)        ~*2.6.24
        (2.6.24-r1)     ~*2.6.24-r1
        (2.6.24-r2)     ~*2.6.24-r2
        (2.6.24-r3)     *2.6.24-r3
        (2.6.24-r4)     *2.6.24-r4
        (2.6.24-r5)     ~*2.6.24-r5
        {build symlink ultra1}
     Installed versions:  2.6.24-r4(2.6.24-r4)(16:22:18 07.04.2008)(-build
-symlink)
     Homepage:            http://dev.gentoo.org/~dsd/genpatches
     Description:         Full sources including the Gentoo patchset for the
2.6 kernel tree

Even they are on "package.keyword" or "package.unmask" files.

Maybe a portage or eix bug ?

Please add depends on #216917 (http://bugs.gentoo.org/show_bug.cgi?id=216917)

Ok, I've found something quite interressing : when it add line in
package.keyword, it only add a tild ("~") and not the arch, i.e. "~amd64". And
portage don't like that (and it's right !)

Actually it looks like a bug in the 2008.0 profiles (just did a quick check on
this) because it's not defining the "ARCH" variable.

waiting for a regular fix, may be useful this simple workaround:

in /usr/bin/autounmask, at line 42:

#my $arch                = $pxs->getArch(); # comment line 42
my $arch                = 'amd64'; # put here your arch.

(In reply to comment #5)
> Actually it looks like a bug in the 2008.0 profiles (just did a quick check on
> this) because it's not defining the "ARCH" variable.
> 

"ARCH" is defined in profiles/arch/  (which is inherited by
default/linux/$arch/)

*** Bug 220871 has been marked as a duplicate of this bug. ***

Updating to PortageXS 0.02.08 should fix this issue. Please test.

(In reply to comment #9)
> Updating to PortageXS 0.02.08 should fix this issue. Please test.
> 
for me it works.
 just a minor problem:

 s939 ~ # autounmask dev-haskell/iconv-0.4

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

 [...]
  * Unmasking dev-haskell/iconv-0.4 and its dependencies.. this might
 take a while..

  * Added '=dev-haskell/iconv-0.4 ~amd64' to
 /etc/portage/package.keywords/autounmask-iconv
  * done!

 look at the version line: PortageXS-0.02.07 is declared but
 PortageXS-0.02.08 is working.

I can confirm that on amd64 and sparc, PortageXS-0.02.08 works correctly
despite wrong version string and an unsuccessful stat on filename:


 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.

I can confirm that moving to PortageXS-0.02.08 solves the problem on x86, too.
Can we stabilize PortageXS-0.02.08?

No, as it has some small bugs I need to correct in the next release.

confirm the bug with x86

The bug is still here (tested with amd64) how about making autounmask unstable
until this is fixed?

Feel free. I'm not going to fix it.

(In reply to comment #15)
> The bug is still here (tested with amd64) how about making autounmask unstable
> until this is fixed?
> 
Just upgrade PortageXS to 0.02.08. That has fixed the bug on every machine that
I have tested it on ( > 20).

That means, autounmask depends on >=dev-perl/PortageXS-0.02.08. Changing the
dependency would still render autounmask unstable.

I will suggest re-opening this bug, claiming that the bug is simply there, if
you won't fix it, for what ever reason - reassign it to someone else, close
resolved wontfix is not the best way to handle this.

If I could do it, I would have done it, I am not a gentoo developer at this
point nor do I have the sufficient experience to fix this bug at this point.

I was not only the gentoo package-maintainer but also upstream maintainer of
the package in question. As I'm not going to work on this packages anymore
(because I retired; lack of time etc.) I think it's reasonable to close this as
wontfix.

Why this bug is closed as wontfix?If you upgrade to PortageXS as you said,
autounmask works fine. Just update the dependencies ;)

I would gladly pick up and maintain this package. If someone could point me in
the right direction on how to accomplish this. It's such a simple fix. How do I
get an updated ebuild into the gentoo repos?

I already fixed it. At least it's fixed if we are actually talking about the
same problem. Make sure you use the latest version of autounmask and PortageXS.

arr

Ok.. here we go.