Re: [gentoo-portage-dev] Portage 2.0.53_rc7 and overlay problems in porthole

[Brian]

On Mon, 2005-21-11 at 20:47 -0800, Brian wrote:
> It seems that all the recent patches in portage may have affected the
> ability to get info reliably from packages in the overlay.  At least for
> porthole.

I've done some more debugging and found that the portage code does not
always return versions for a package that exists only in the overlay.
The following portage code in this porthole module was not returning
results for 2 packages in my overlay.  Both are in the dev-python
category.  But it does return versions for porthole (in both the portage
tree and my overlay) as well as porthole-cvs (app-portage category)
which only exists in my overlay.  This happens repeatedly for these
packages.

code snipit:

    def get_versions(self, include_masked = True):
        """Returns all available ebuilds for the package"""
        # Note: this is slow, especially when include_masked is false
        criterion = include_masked and 'match-all' or 'match-visible'
        dprint("PORTAGELIb: get_versions(); criterion = %s, package = %s" %(str(criterion),self.full_name))
        v = portage.portdb.xmatch(criterion, str(self.full_name))
        dprint("PORTAGELIb: get_versions(); v = %s" %str(v))
        return  v #portage.portdb.xmatch(criterion, str(self.full_name))


So, I did some more checking and moved the kiwi directory to my
app-portage overlay category and re-tested.

It worked correctly.  Further digging, I found the permissions on my
overlay dev-python directory to be 754 and not 755 as is the app-portage
category.  Changing the permissions fixed the problem.


Perhaps it might be a good idea if portage could report a permissions
problem encountered in an overlay.  This portage behaviour has changed
from the past.  Perhaps a QA type notice about the permissions not being
set correctly should be printed.
-- 
Brian <dol-sen@×××××.net>

-- 
gentoo-portage-dev@g.o mailing list