From: Ben Kohler <bkohler@gmail.com>
To: gentoo-releng@lists.gentoo.org
Subject: [gentoo-releng] Setting --autounmask=n for autobuilds
Date: Tue, 3 Apr 2018 08:46:27 -0500 [thread overview]
Message-ID: <CANSUr=KTYbxsn7tXgBAB4Wsz9a=Pb-5HqVcj=okicnM7-4QZ_A@mail.gmail.com> (raw)
Hi guys,
I'd like to propose adding --autounmask=n to EMERGE_DEFAULT_OPTS, at
least for nightheron builds but preferably everywhere. Due to a known
portage bug [1], when a keyword or USE change is required by some
package, the chain of deps shown in the autounmask output cannot be
trusted. It will very often blame the completely wrong package for
the unmask.
Since the autobuild process cannot make real use of autounmask anyway,
I propose that we turn it off. The main downside I see, is that for
complex changes requiring several new package.* entries,
--autounmask=n will cause it to stop after only the first one is
printed.
But I think this will be worth it. It will really help us quickly get
to the bottom of failures like this [2] and this [3]. BTW does anyone
know where those s390 builds happen?
Thoughts?
[1] https://bugs.gentoo.org/419381
[2] https://archives.gentoo.org/gentoo-releng-autobuilds/message/6a1c4b6bdfba9bc204af3172beb2287a
[3] https://archives.gentoo.org/gentoo-releng-autobuilds/message/8689b65e9502fba1717714cbf9514bd4
-Ben
reply other threads:[~2018-04-03 13:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANSUr=KTYbxsn7tXgBAB4Wsz9a=Pb-5HqVcj=okicnM7-4QZ_A@mail.gmail.com' \
--to=bkohler@gmail.com \
--cc=gentoo-releng@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox