From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Some tarballs still ship broken .png images that can't be viewed with libpng16, "Tracker" bug #468386
Date: Tue, 08 Apr 2014 22:25:16 +0300 [thread overview]
Message-ID: <53444D1C.2070600@gentoo.org> (raw)
In-Reply-To: <1396985171.2061.33.camel@belkin5>
On 08/04/14 22:26, Pacho Ramos wrote:
> El mar, 08-04-2014 a las 16:14 +0300, Samuli Suominen escribió:
>> It would take considerably amount of time to start extracting tarballs,
>> installing ebuilds, and reporting bugs about possible
>> broken .png files within packages.
>> The problem is broken IDAT lenght, an error that libpng15 still
>> gracefully ignored, but libpng16 no longer ignores.
>>
>> The bug, http://bugs.gentoo.org/468386
>> List created by Tobias at 2013 May,
>> https://bugs.gentoo.org/attachment.cgi?id=347306
>> <mailto:klausman@gentoo.org>
>>
>> This has been discussed on the ML before, and most important packages
>> got already fixed, but there are packages still
>> left. Any help addressing the issue is welcome, and I'm sending this
>> mail in hopes people will see packages on the lists
>> that intrest them, and fix them.
>>
>> Thanks,
>> Samuli
>> <mailto:klausman@gentoo.org>
>>
> If there exists a tool that detects that broken png files, maybe a QA
> portage check (like the one used to detect broken .desktop files) could
> be added to help to detect and fix the problematic images :/
>
>
Pretty good idea, there is the script in python, and Portage is python,
maybe it can be adopted somehow.
The script is at, https://bugs.gentoo.org/show_bug.cgi?id=466190#c11
- Samuli
next prev parent reply other threads:[~2014-04-08 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 13:14 [gentoo-dev] Some tarballs still ship broken .png images that can't be viewed with libpng16, "Tracker" bug #468386 Samuli Suominen
2014-04-08 13:17 ` Samuli Suominen
2014-04-08 19:26 ` Pacho Ramos
2014-04-08 19:25 ` Samuli Suominen [this message]
2014-04-08 20:26 ` Pacho Ramos
2014-04-08 20:39 ` Samuli Suominen
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=53444D1C.2070600@gentoo.org \
--to=ssuominen@gentoo.org \
--cc=gentoo-dev@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