On Wed, 30 Mar 2016 16:52:13 +0200
Patrick Lauer wrote:
> On 03/30/2016 04:32 PM, mgo...@bonedaddy.net wrote:
> > Looks like someone just broke Gentoo!
> >
> > New issues:
> > https://qa-reports.gentoo.org/output/gentoo-ci/33f062a/output.html#dev-db/aerospike-server-community
> >
> >
> > Introduced by commits:
> > https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=54033c5
> >
> >
> > Changes since last check:
> > https://gitweb.gentoo.org/repo/gentoo.git/log/?qt=range&q=0d2b3ad..54033c5
> >
> > --
> > Gentoo repository CI
> ... can you please either use repoman like everyone else, or fix
> repoman to match the behaviour you like?
>
> 'cause it's annoying to have repoman say all is well and then get
> such a nice response. Hard to comply with rules if there's no good
> way to check the rules.
>
>
Yeah, it would be nice to have a final resolution to the
metadataDTD ==> xmlshema change so the repoman metadata module can get
a proper re-write.
In the meantime, repoman can not detect the recent change to the
maintainer field.
--
Brian Dolbec
