Gentoo Archives: gentoo-dev

From: Brian Dolbec <dolsen@g.o>
To: Patrick Lauer <patrick@g.o>
Cc: mgorny@×××××××××.net, gentoo-automated-testing@l.g.o, "gentoo-dev@l.g.o" <gentoo-dev@l.g.o>
Subject: Re: [gentoo-dev] Re: BROKEN: repository became broken!
Date: Wed, 30 Mar 2016 15:04:18
Message-Id: 20160330080312.7190d824.dolsen@gentoo.org
In Reply to: [gentoo-dev] Re: BROKEN: repository became broken! by Patrick Lauer
1 On Wed, 30 Mar 2016 16:52:13 +0200
2 Patrick Lauer <patrick@g.o> wrote:
3
4 > On 03/30/2016 04:32 PM, mgorny@×××××××××.net wrote:
5 > > Looks like someone just broke Gentoo!
6 > >
7 > > New issues:
8 > > https://qa-reports.gentoo.org/output/gentoo-ci/33f062a/output.html#dev-db/aerospike-server-community
9 > >
10 > >
11 > > Introduced by commits:
12 > > https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=54033c5
13 > >
14 > >
15 > > Changes since last check:
16 > > https://gitweb.gentoo.org/repo/gentoo.git/log/?qt=range&q=0d2b3ad..54033c5
17 > >
18 > > --
19 > > Gentoo repository CI
20 > ... can you please either use repoman like everyone else, or fix
21 > repoman to match the behaviour you like?
22 >
23 > 'cause it's annoying to have repoman say all is well and then get
24 > such a nice response. Hard to comply with rules if there's no good
25 > way to check the rules.
26 >
27 >
28
29 Yeah, it would be nice to have a final resolution to the
30 metadataDTD ==> xmlshema change so the repoman metadata module can get
31 a proper re-write.
32
33 In the meantime, repoman can not detect the recent change to the
34 maintainer field.
35
36 --
37 Brian Dolbec <dolsen>