From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 62125138334 for ; Wed, 12 Sep 2018 14:50:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E7B82E0C5A; Wed, 12 Sep 2018 14:50:16 +0000 (UTC) Received: from mail-pl1-f182.google.com (mail-pl1-f182.google.com [209.85.214.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 8F3B3E0A9C for ; Wed, 12 Sep 2018 14:50:16 +0000 (UTC) Received: by mail-pl1-f182.google.com with SMTP id s17-v6so1091600plp.7 for ; Wed, 12 Sep 2018 07:50:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=muHa677j+/je13ufwY9oTtkLcNayIH1iK2+CpnJ6ZY8=; b=DC+Ve7dB3ilKExMmEDDkrmhTUYXn3TsEg1bNk1nEyz5R9Cz5PMkQmpfOvqiOPdRt+u 9uty+r1WM1Epaj+FMdMUQC/OA5RGzNielVNKoExAGdzr5zFL7MR3BSNkV3pnZWHkPPfI UwZSqtTj1XXANOTXfZp7RQFZW4CskA2ftyzw7Kz0z/ssRSEsIkX5oLgEGPg+qHWa8qMv 64V7C7cv/RW0dMY0BvaHgxBHF1g0uUz8w9SnP31ZL+H2scH99hYD2YhAC4ZA04kFUKnO LJgOVlsLzf+DdBkY7vGSuPaELTNaXI3X3/UUFhQjAfdOs+otnMcsCknUK/Bvd455u/JD v1NA== X-Gm-Message-State: APzg51DWux4E/WI+alzUYUGfARBd4GKnpBA6EF+jT4BTEkpd76zRyAqW s3w77njQXJeqbp+x9qGCVG3hdD9sT/TCWawQWOGSw27o X-Google-Smtp-Source: ANB0VdaaPGC2bp4SvHAVxp31p1CJbB+mV/8luS6IhKSY2vfcSfHvdfS6nwL1MgoZCMnDuD9ZrXlONJhjXmuG/NJj6TY= X-Received: by 2002:a17:902:722:: with SMTP id 31-v6mr2677831pli.207.1536763814735; Wed, 12 Sep 2018 07:50:14 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 References: <20180909143221.21d784d02f51623e8c57c545@gentoo.org> <1536510660.863.9.camel@gentoo.org> <20180910074539.GA6512@baraddur.perfinion.com> <0d8b7f02-9c38-969c-413b-69d4dee6ca89@gentoo.org> <20180912085649.GA16516@baraddur.perfinion.com> In-Reply-To: <20180912085649.GA16516@baraddur.perfinion.com> From: Rich Freeman Date: Wed, 12 Sep 2018 10:50:03 -0400 Message-ID: Subject: Re: [gentoo-dev] Changing policy about -Werror To: gentoo-dev Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: e0ca2615-4fe2-4e39-8e52-0d03d24a61d7 X-Archives-Hash: d7e5ca86d3f8c0db6b597d8b14bf0c65 On Wed, Sep 12, 2018 at 4:56 AM Jason Zaman wrote: > > Replying to a somewhat random post. There are two separate things here > that people are discussing here but are not the same thing. Three, really... > > 1) We want to know when a package has terrible warnings when installing > it so we can report upstream and know that something might have gone > wrong. There is also the case where we want these warnings to block installation, because the risk of there being a problem is too great. > > Stick this in your make.conf: > PORTAGE_ELOG_SYSTEM="echo save" > PORTAGE_ELOG_CLASSES="warn error log qa" > I'm pretty sure toralf's tinderbox already has these enabled but all > devs should too. The problem is that this will make the warnings non-fatal. Do we still tell users not to report these kinds of warnings in bugzilla? If they're the sort we consider serious then we would want to know about it so that we can address it, vs just waiting for upstream to fix them in a future release. There might be a better solution than -Werror, such as a flag in an ebuild that makes the existing QA warning fatal and tells the user to log a bug. -- Rich