If you use something like Samba / CIFS to share the contents of /usr/portage across several machines as we do, the names of some files in there make it impossible to access them over the network. apr-util current suffers this problem as one of the patch files has a name containing a : Although the file is visable, attempts to access it cause "not a directory" errors and the ebuild fails. Similar issues may exist in other applications. Currently this is making it nigh on impossible to update our web servers as Apache requires apr-util. Work arounds include changing the ebuild and manifests etc to match a renamed file, not pretty and gets over written next emerge sync. Or maintaining a complete portage tree on ever server, which seems a bit silly. The latter is of course not possible if you use a windows based file server to house /usr/portage, but admitedly that'd be an odd thing to do. A policy and/or naming convention that excludes "silly characters" such as : would make life much easier and maintain compatability with whatever a user wishes to do.
This has nothing to do w/ distfiles, changing the summary. I suppose you mean apr-util-0.9.x-161086:161087.patch
I was hoping to get a more wide spread fix that would stop this causing issues in the future... but right now I'll settle for an APR Util fix. And yes, that's the problem file.
(In reply to comment #2) > I was hoping to get a more wide spread fix that would stop this causing issues > in the future... distfiles means /usr/portage/distfiles, I assume. I highly doubt that upstream uses : in tarball names. If you are aware of any other offending filenames in patches etc., then add the respective ebuilds, otherwise it's hard to assign such bugs. ;)
Patch renamed in CVS.
