From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 430911381F3 for ; Wed, 24 Apr 2013 10:47:56 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0F7B2E0CDE; Wed, 24 Apr 2013 10:47:18 +0000 (UTC) Received: from mail.schwarzvogel.de (skade.schwarzvogel.de [144.76.18.87]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2369DE0CD4 for ; Wed, 24 Apr 2013 10:47:16 +0000 (UTC) Received: from klausman by mail.schwarzvogel.de with local (Exim 4.80.1) (envelope-from ) id 1UUxEJ-0009hk-13 for gentoo-dev@lists.gentoo.org; Wed, 24 Apr 2013 12:47:15 +0200 Date: Wed, 24 Apr 2013 12:47:15 +0200 From: Tobias Klausmann To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] FYI: libpng16 won't be able to show some broken icons libpng15 was still able to Message-ID: <20130424104714.GA35614@skade.schwarzvogel.de> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <51703A47.4060304@gentoo.org> <20130422110334.GA76925@skade.schwarzvogel.de> <51766167.9050306@gmail.com> <51766374.1030107@gentoo.org> <20854.26649.991033.420549@a1i15.kph.uni-mainz.de> <20130423111905.GA92694@skade.schwarzvogel.de> <20130423181410.GA4335@waltdnes.org> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130423181410.GA4335@waltdnes.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: Tobias Klausmann X-Archives-Salt: 45a7b508-8bf7-45e6-b433-500427fa219c X-Archives-Hash: d3ad753acf3fd96b1a8ad89ea29b2736 Hi! On Tue, 23 Apr 2013, Walter Dnes wrote: > On Tue, Apr 23, 2013 at 01:19:05PM +0200, Tobias Klausmann wrote > > The second problem, however, is trickier. We can rely on people > > noticing the error messages/broken packages and hope they file > > bugs. The other option is to have a QA-like check for it, again > > using the simplest possible binary to do so. > > Will those messages be during the ebuild? There are currently > messages like... > > > QA Notice: Package triggers severe warnings which indicate that it > > may exhibit random runtime failures. > > ExtensionSubtables.cpp:32:31: warning: dereferencing type-punned > > pointer will break strict-aliasing rules > > > > Please do not file a Gentoo bug and instead report the above > > QA issues directly to the upstream developers of this software. > > Homepage: http://www.icu-project.org/ > > A similar message, about non-displaying icons instead of "random > runtime failures" may be in order. At the very least, it will let end > users know who to report the problem to. Exactly. I'd envision something like this: [snip] QA Notice: Package installs broken PNG files that may cause warnings, errors or fail to display completely. [... list of bad PNGs ...] See http://to-be-written-page/ for more information on how to fix these files. Please do not file a Gentoo bug and instead report the above QA issues directly to the upstream developers of this software. Homepage: http://project-homepage/ [pins] Regards, Tobias