Summary: | repoman metadata.xml validation doesn't match documented behaviour | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Ryan Hill (RETIRED) <rhill> |
Component: | Repoman | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | comrel |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ryan Hill (RETIRED)
2009-05-15 05:21:32 UTC
CCing the doc maintainers; they can sort out what needs to be changed. http://archives.gentoo.org/gentoo-dev/msg_3e335b01696e786598c55b6ace346beb.xml repoman should check the value for <herd> against herds listed in herds.xml (In reply to comment #2) > http://archives.gentoo.org/gentoo-dev/msg_3e335b01696e786598c55b6ace346beb.xml > > repoman should check the value for <herd> against herds listed in herds.xml > thought I was in a tab inputting a new bug :( (In reply to comment #2) > http://archives.gentoo.org/gentoo-dev/msg_3e335b01696e786598c55b6ace346beb. > xml > > repoman should check the value for <herd> against herds listed in herds.xml We've had a herds check since portage-2.1.9: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=7c11c8ec5f568984ee720fc677959f9d2c9dfd32 That comment was unrelated to this bug. Is this still a problem with the new split repoman pkg? Herds are no longer, not sure this is still releveant, closing, re-open if it is. |