Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 180062 - dev-perl/PortageXS-0.02.07 - autounmask doesn't find the layman repositories
Summary: dev-perl/PortageXS-0.02.07 - autounmask doesn't find the layman repositories
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Christian Hartmann (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-27 22:21 UTC by Bruno Roggeri
Modified: 2007-06-02 08:36 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Roggeri 2007-05-27 22:21:47 UTC
This is because layman modifies the PORTDIR_OVERLAY variable through a file that must be "source"-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="
/usr/portage/local/layman/nouveau
/usr/portage/local/layman/kde
$PORTDIR_OVERLAY
"

It seems PortageXS doesn't process the "source" keyword, and maybe doesn't do bash style variable appending either...


Reproducible: Always

Steps to Reproduce:
1. emerge layman autounmask
2. fetch an overlay with layman
3. add "source /usr/portage/local/layman/make.conf" 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 <ian@gentoo.org>.

 * 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
Comment 1 Christian Hartmann (RETIRED) gentoo-dev 2007-05-29 19:44:51 UTC
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!
Comment 2 Bruno Roggeri 2007-05-29 22:01:28 UTC
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's kind of a regression :  autounmask doesn'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 <ian@gentoo.org>.

 * 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!
_______

Comment 3 Christian Hartmann (RETIRED) gentoo-dev 2007-05-30 14:07:26 UTC
Shame on me. - Should be fixed in 0.19.
Comment 4 Bruno Roggeri 2007-05-30 15:39:03 UTC
OK, now it works, but is it normal behaviour that autounmask selects several versions of the same packages for unmasking ? I didn't use autounmask before so I don'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 <ian@gentoo.org>.

 * 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 '=kde-base/kdelibs-9999.4 **' to /etc/portage/package.keywords
 * Added '=dev-util/cmake-2.4.6 ~amd64' to /etc/portage/package.keywords
 * Added '=dev-util/cmake-2.4.5 ~amd64' to /etc/portage/package.keywords
 * Added '=x11-libs/qt-4.3.0_beta **' to /etc/portage/package.keywords
 * Added '=x11-libs/qt-4.3.0_beta1 **' to /etc/portage/package.keywords
 * Added '=x11-libs/qt-20070423 **' to /etc/portage/package.keywords
 * Added '=x11-libs/qt-4.3.0_rc1 **' to /etc/portage/package.keywords
 * Added '=kde-misc/strigi-9999 **' to /etc/portage/package.keywords
 * Added '=dev-libs/soprano-9999 **' 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!
Comment 5 Steve L 2007-05-30 19:35:49 UTC
Use --noversions to only have the package name in keywords.
Comment 6 Christian Hartmann (RETIRED) gentoo-dev 2007-05-31 07:05:52 UTC
Thanks everybody! :)
Comment 7 Bruno Roggeri 2007-06-01 20:03:16 UTC
Well, I'm sorry, I can't leave you in peace yet ;) :

It seems that now, the main repositories isn't detected if the PORTDIR variable isn'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 <ian@gentoo.org>.

 * 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,
Comment 8 Christian Hartmann (RETIRED) gentoo-dev 2007-06-02 08:36:16 UTC
Good catch! Fixed in 0.20.