Created attachment 338046 [details] Funtoo's profile.desc Running the following command(s) on Gentoo will reproduce the issue: git clone http://git.funtoo.org/funtoo-overlay && \ cd funtoo-overlay/sys-boot/grub && \ repoman full The error that occurs on my system is: repoman: invalid arch: "arch" in /home/richard/devel/funtoo-overlay/profiles/profiles.desc line 16 I have attached Funtoo's profile.desc. Having no understanding of how these bits work, I cannot tell if the Funtoo stuff needs to be changed or if repoman should be extended. I asked zmedico in #gentoo-portage on freenode if filing a bug for the portage team was appropriate in this situation and he confirmed that it was.
Repoman uses the values from profiles/arch.list to validate the first column of profiles.desc. I guess maybe funtoo has patch repoman to make it handle profiles.desc differently?
Whatever the difference is, we could use a setting in metadata/layout.conf to make repoman handle profiles.desc differently. That's how we typically handle extensions like this.
(In reply to comment #1) > Repoman uses the values from profiles/arch.list to validate the first column > of profiles.desc. I guess maybe funtoo has patch repoman to make it handle > profiles.desc differently? Funtoo has no such patch and profiles/arch.list is unchanged from Gentoo's main tree. (In reply to comment #2) > Whatever the difference is, we could use a setting in metadata/layout.conf > to make repoman handle profiles.desc differently. That's how we typically > handle extensions like this. That will likely require a specification of the semantics of the extension. I hope that drobbins will find time to provide that.
With the stage 3 re-write of the repoman code, repoman should be fully plug-able and configurable. This can include addtional checks and plug-in modules to perform them. or even just a reduced set of checks. It will all be controlled via the repository in the metadata directory.
repoman support has been removed per bug 835013. Please file a new bug (or, I suppose, reopen this one) if you feel this check is still applicable to pkgcheck and doesn't already exist.