<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>180062</bug_id>
          
          <creation_ts>2007-05-27 22:21 0000</creation_ts>
          <short_desc>dev-perl/PortageXS-0.02.07 - autounmask doesn&apos;t find the layman repositories</short_desc>
          <delta_ts>2007-06-02 08:36:16 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Applications</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>bruno.roggeri@metz.supelec.fr</reporter>
          <assigned_to>ian@gentoo.org</assigned_to>
          <cc>perl@gentoo.org</cc>

      

      
          <long_desc isprivate="0">
            <who>bruno.roggeri@metz.supelec.fr</who>
            <bug_when>2007-05-27 22:21:47 0000</bug_when>
            <thetext>This is because layman modifies the PORTDIR_OVERLAY variable through a file that must be &quot;source&quot;-d in make.conf.
To make it a bit clearer, my /etc/make.conf contains the following line

source /usr/portage/local/layman/make.conf

and /usr/portage/local/layman/make.conf looks like this :
PORTDIR_OVERLAY=&quot;
/usr/portage/local/layman/nouveau
/usr/portage/local/layman/kde
$PORTDIR_OVERLAY
&quot;

It seems PortageXS doesn&apos;t process the &quot;source&quot; keyword, and maybe doesn&apos;t do bash style variable appending either...


Reproducible: Always

Steps to Reproduce:
1. emerge layman autounmask
2. fetch an overlay with layman
3. add &quot;source /usr/portage/local/layman/make.conf&quot; to your /etc/make.conf
4. try to autounmask an ebuild in the layman overlay

Actual Results:  
# autounmask --pretend kde-base/kdelibs-9999.4

 autounmask version 0.15 (using PortageXS-0.02.07)
 Bugs and requests go to ian &lt;ian@gentoo.org&gt;.

 * Using repository: /usr/portage

 * The given category/package-version does not seem to exist. Please check and try again.



Expected Results:  
The line 
 * Using repository: /usr/portage

should mention the layman repositories, and then the ebuilds would be found</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ian@gentoo.org</who>
            <bug_when>2007-05-29 19:44:51 0000</bug_when>
            <thetext>Should work in 0.18. Please reopen this bug if the problem still remains.

If this works flawlessy it will go into one of the next releases of PortageXS.

Thanks for bringing this to my attention!</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>bruno.roggeri@metz.supelec.fr</who>
            <bug_when>2007-05-29 22:01:28 0000</bug_when>
            <thetext>Hello,

Thank you a lot for the quick fix (or rather, the quick new feature, as full bash interpretation is quite an improvement :) )

However ... it seems there&apos;s kind of a regression :  autounmask doesn&apos;t manage to compute the list of ebuilds to unmask anymore

Example with a package from the official portage tree :
________
# autounmask --pretend x11-themes/gnome-themes-extras-0.9.0

 autounmask version 0.18 (using PortageXS-0.02.07)
 Bugs and requests go to ian &lt;ian@gentoo.org&gt;.

 * Using repositories:
     /usr/portage
     /usr/portage/local/layman/nouveau
     /usr/portage/local/layman/kde

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

 * Unmasking x11-themes/gnome-themes-extras-0.9.0 and its dependencies.. this might take a while..

 * Restoring files because autounmask was called with the --pretend option.
 * done!
_______

</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ian@gentoo.org</who>
            <bug_when>2007-05-30 14:07:26 0000</bug_when>
            <thetext>Shame on me. - Should be fixed in 0.19.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>bruno.roggeri@metz.supelec.fr</who>
            <bug_when>2007-05-30 15:39:03 0000</bug_when>
            <thetext>OK, now it works, but is it normal behaviour that autounmask selects several versions of the same packages for unmasking ? I didn&apos;t use autounmask before so I don&apos;t know if this was the former behaviour:

Example with kdelibs from the kde repo from layman :
# autounmask kde-base/kdelibs-9999.4

 autounmask version 0.19 (using PortageXS-0.02.07)
 Bugs and requests go to ian &lt;ian@gentoo.org&gt;.

 * Using repositories:
     /usr/portage/local/layman/nouveau
     /usr/portage/local/layman/kde

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

 * Unmasking kde-base/kdelibs-9999.4 and its dependencies.. this might take a while..

 * Added &apos;=kde-base/kdelibs-9999.4 **&apos; to /etc/portage/package.keywords
 * Added &apos;=dev-util/cmake-2.4.6 ~amd64&apos; to /etc/portage/package.keywords
 * Added &apos;=dev-util/cmake-2.4.5 ~amd64&apos; to /etc/portage/package.keywords
 * Added &apos;=x11-libs/qt-4.3.0_beta **&apos; to /etc/portage/package.keywords
 * Added &apos;=x11-libs/qt-4.3.0_beta1 **&apos; to /etc/portage/package.keywords
 * Added &apos;=x11-libs/qt-20070423 **&apos; to /etc/portage/package.keywords
 * Added &apos;=x11-libs/qt-4.3.0_rc1 **&apos; to /etc/portage/package.keywords
 * Added &apos;=kde-misc/strigi-9999 **&apos; to /etc/portage/package.keywords
 * Added &apos;=dev-libs/soprano-9999 **&apos; to /etc/portage/package.keywords
 * done!

Anyway, this is really not a big deal as the unmasking lines are clearly tagged in package.keywords. So, thanks a lot!</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>slong@rathaus.eclipse.co.uk</who>
            <bug_when>2007-05-30 19:35:49 0000</bug_when>
            <thetext>Use --noversions to only have the package name in keywords.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ian@gentoo.org</who>
            <bug_when>2007-05-31 07:05:52 0000</bug_when>
            <thetext>Thanks everybody! :)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>bruno.roggeri@metz.supelec.fr</who>
            <bug_when>2007-06-01 20:03:16 0000</bug_when>
            <thetext>Well, I&apos;m sorry, I can&apos;t leave you in peace yet ;) :

It seems that now, the main repositories isn&apos;t detected if the PORTDIR variable isn&apos;t explicitely set in make.conf

example :
# autounmask --pretend media-video/mplayer-1.0.20070427

 autounmask version 0.19 (using PortageXS-0.02.07)
 Bugs and requests go to ian &lt;ian@gentoo.org&gt;.

 * Using repositories:
     /usr/portage/local/layman/nouveau
     /usr/portage/local/layman/kde
     /usr/portage/local/layman/kde-experimental

 * The given category/package-version does not seem to exist. Listing existing versions:

 * nouveau (/usr/portage/local/layman/nouveau):
     none

 *  (/usr/portage/local/layman/kde):
     none

 * genkdesvn-kde3 (/usr/portage/local/layman/kde-experimental):
     none

 * Please pick one of the versions given above and try again.

workaround: write PORTDIR=/usr/portage in /etc/make.conf

Cheers,</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ian@gentoo.org</who>
            <bug_when>2007-06-02 08:36:16 0000</bug_when>
            <thetext>Good catch! Fixed in 0.20.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>