Gentoo Archives: gentoo-dev

From: "Michał Górny" <mgorny@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [PATCH v2] profiles.desc: Lower profiles with broken depgraph from dev to exp
Date: Thu, 11 Jan 2018 20:27:44
Message-Id: 1515702452.7268.2.camel@gentoo.org
In Reply to: Re: [gentoo-dev] [PATCH v2] profiles.desc: Lower profiles with broken depgraph from dev to exp by Mart Raudsepp
1 W dniu czw, 11.01.2018 o godzinie 22∶17 +0200, użytkownik Mart Raudsepp
2 napisał:
3 > On Thu, 2018-01-11 at 20:45 +0100, Michał Górny wrote:
4 > > # ARM64 Profiles
5 > > -arm64 default/linux/arm64/13.0 dev
6 > > +arm64 default/linux/arm64/13.0 exp
7 > > arm64 default/linux/arm64/13.0/desktop exp
8 > > -arm64 default/linux/arm64/13.0/desktop/systemd dev
9 > > +arm64 default/linux/arm64/13.0/desktop/systemd exp
10 > > arm64 default/linux/arm64/13.0/developer exp
11 > > arm64 default/linux/arm64/13.0/systemd exp
12 > > -arm64 default/linux/arm64/17.0 dev
13 > > +arm64 default/linux/arm64/17.0 exp
14 > > arm64 default/linux/arm64/17.0/desktop exp
15 > > -arm64 default/linux/arm64/17.0/desktop/systemd dev
16 > > +arm64 default/linux/arm64/17.0/desktop/systemd exp
17 > > arm64 default/linux/arm64/17.0/developer exp
18 > > arm64 default/linux/arm64/17.0/systemd exp
19 >
20 > With this I'll need to run through all of these profiles with
21 > repoman -e=y and wait a long time, instead of just the two (well, with
22 > 17.0 now 4) profiles that I actually care about and checks enough. I
23 > also will see a TON of issues from the musl profiles down below that
24 > main block (it doesn't inherit base or something).
25 >
26 > This would make arm64 work completely impossible, so NAK from me.
27
28 repoman has --include-arches option for a reason. Profile statuses are
29 not your private convenience.
30
31 > Additionally if depgraph wouldn't be broken anymore, we would be moving
32 > them to stable, not some separate "dev" step.
33 >
34 > Same goes for the mips main block changes.
35
36 But it is broken, and it won't become less broken if we keep ignoring
37 the fact and not reporting new breakages just because one developer
38 can't fix his workflow.
39
40 --
41 Best regards,
42 Michał Górny

Replies