When repoman runs from a category dir, interpret the metadata.xml of the category is a package name and try to create metadata.xml/Manifest in an endless loop.
What is this? A mental note to self?
sorry if it was too laconic, but it contains all the useful info repoman thinks that metadata.xml file found in every category directory is a package name, so it tries to create metadata.xml/Manifest which, of course, it fails. still, it doesn't give up, it just keeps trying in an endless loop. do you need more info about it?
mrness isnt a portage developer (afaik) so chances are he's reporting it to the portage devs to have it fixed ;P
A track back, screen dump or any detailed info you can provide helps. Most of us have not really honed our mind reading skills (our fault) so you should atleast let everybody know what version of portage your talking about.. emerge -V
bash-2.05b$ bash-2.05b$ emerge -V Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.4.3-20050110, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r4 i686) I don't have a screen capture because I needed to move www-proxy to net-proxy as fast as I could. Maybe I wasn't clear enough (excuse my poor English), but I don't see a reason for your sarcasm. If I'd received a bug like this on a program maintained by me, I would understand the problem. It's just a confusion that "repoman commit" makes about package names inside a category.
Created attachment 56966 [details, diff] Patch to only do Manifest creation on directories that exist This needs testing but is pretty straight forward.
Fixed on or before 2.0.51.22-r1
Looking through the batch of bugs, I'm not sure that some of these are actually fixed in stable. Others, the requirements have possibly changed after the initial fix was committed. If you think this bug has been closed incorrectly, please reopen or ask that it be reopened.
