Bug 13053 – --usepkgonly incorectly referencing actual ebuild files

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Mark Guertin 2003-01-01 17:21:20 UTC]

THis has been the cause of several bugs so far (will include in followup  
posts)  
  
It is being called like this from grp-install.sh script:  
  
PKGDIR="blah" emerge -K --nodeps ${FULLIST}  
  
FULLIST is the full cat/pkg-version.tbz2 file list of all deps for a group.  
  
Probably something trying to touch or verify an ebuild for a db update (just a  
guess).  This is a big blocker, and will probably require rebuilding stages,  
etc (or having users update portage before doing a binary based install -  
which makes things tough for offline installs :( )

[Comment 1 Nicholas Jones (RETIRED) 2003-01-02 21:59:26 UTC]

the category is probably the problem.

[Comment 2 Nicholas Jones (RETIRED) 2003-01-02 22:00:56 UTC]

cvs should support this presently. I'll probably have a working 2.0.47
or a >4 pre version out within the next 12-24 hours.

[Comment 3 Mark Guertin 2003-01-08 09:51:57 UTC]

Yep its in and working , tested last night, thanks Nick

[Comment 4 Jared H. Hudson (RETIRED) 2003-02-24 07:12:54 UTC]

2.0.46-r12 has this problem and is currently unmasked. So anyone installing Gentoo today and trying to use GRP via grp-install.sh or emerge -K gnome (new method)
will fail.

If 2.0.47+ is unstable, perhaps this fix could be backported?

[Comment 5 Paul Tötterman 2003-07-17 05:34:24 UTC]

This seems to be fixed in a newer version of portage that has already been unmasked. Could this be marked as fixed?

[Comment 6 Nicholas Jones (RETIRED) 2003-07-17 05:59:21 UTC]

Should be working fine.