From: | Ben Kohler <bkohler@×××××.com> |
---|---|
To: | gentoo-releng@l.g.o |
Subject: | [gentoo-releng] Setting --autounmask=n for autobuilds |
Date: | Tue, 03 Apr 2018 13:46:31 |
Message-Id: | CANSUr=KTYbxsn7tXgBAB4Wsz9a=Pb-5HqVcj=okicnM7-4QZ_A@mail.gmail.com |
1 | Hi guys, |
2 | |
3 | I'd like to propose adding --autounmask=n to EMERGE_DEFAULT_OPTS, at |
4 | least for nightheron builds but preferably everywhere. Due to a known |
5 | portage bug [1], when a keyword or USE change is required by some |
6 | package, the chain of deps shown in the autounmask output cannot be |
7 | trusted. It will very often blame the completely wrong package for |
8 | the unmask. |
9 | |
10 | Since the autobuild process cannot make real use of autounmask anyway, |
11 | I propose that we turn it off. The main downside I see, is that for |
12 | complex changes requiring several new package.* entries, |
13 | --autounmask=n will cause it to stop after only the first one is |
14 | printed. |
15 | |
16 | But I think this will be worth it. It will really help us quickly get |
17 | to the bottom of failures like this [2] and this [3]. BTW does anyone |
18 | know where those s390 builds happen? |
19 | |
20 | Thoughts? |
21 | |
22 | [1] https://bugs.gentoo.org/419381 |
23 | [2] https://archives.gentoo.org/gentoo-releng-autobuilds/message/6a1c4b6bdfba9bc204af3172beb2287a |
24 | [3] https://archives.gentoo.org/gentoo-releng-autobuilds/message/8689b65e9502fba1717714cbf9514bd4 |
25 | |
26 | -Ben |