On Fri, 2011-11-04 at 13:12 -0400, Tom Lane wrote:
I did test rebuilds in mock of all rawhide packages that are reported to
be dependent on libpng. Out of 964 packages with dependencies on libpng,
we have:
Packages that rebuilt successfully with 1.5 658
Packages that FTBFS for
On Mon, Dec 5, 2011 at 5:41 PM, Adam Jackson a...@redhat.com wrote:
On Fri, 2011-11-04 at 13:12 -0400, Tom Lane wrote:
I did test rebuilds in mock of all rawhide packages that are reported to
be dependent on libpng. Out of 964 packages with dependencies on libpng,
we have:
Packages that
Adam Jackson a...@redhat.com writes:
I've been doing driveby rebuilds for some of these that happen to have
been in a default install on my machine, but we still have a huge pile
of things built against the old libpng in rawhide:
[ajax@f17 cairomm]$ repoquery --whatrequires libpng-compat | wc
On Mon, Dec 05, 2011 at 17:44:12 +,
Peter Robinson pbrobin...@gmail.com wrote:
Go for it, I think it makes sense. For those that don't support 1.5
they can stay against the compat in the mean time.
Based on the sample I worked with, most of the ones with failed builds
are likely to be
On Mon, Dec 5, 2011 at 12:52 PM, Bruno Wolff III br...@wolff.to wrote:
On Mon, Dec 05, 2011 at 17:44:12 +,
Peter Robinson pbrobin...@gmail.com wrote:
Go for it, I think it makes sense. For those that don't support 1.5
they can stay against the compat in the mean time.
Based on the
Michael Schwendt mschwe...@gmail.com writes:
With
pkgconfig(libpng) = 1.2.46
pkgconfig(libpng12) = 1.2.46
once libpng12.pc gets removed from the distribution, the dep-chains
break, of course.
As a temporary work-around, you could have provided that thing manually
in the libpng-devel
On Mon, 21 Nov 2011 16:26:02 -0500, TL (Tom) wrote:
With
pkgconfig(libpng) = 1.2.46
pkgconfig(libpng12) = 1.2.46
once libpng12.pc gets removed from the distribution, the dep-chains
break, of course.
As a temporary work-around, you could have provided that thing manually
in
On Wed, 09 Nov 2011 10:42:10 -0500, TL (Tom) wrote:
On Fri, 2011-11-04 at 13:12 -0400, Tom Lane wrote:
I plan to provide the 1.2.x libpng shared library (and only the library,
not its devel support files) in a libpng-compat subpackage for the time
being.
Any reason why the compat
On Wed, 2011-11-09 at 10:42 -0500, Tom Lane wrote:
Nils Philippsen n...@redhat.com writes:
On Fri, 2011-11-04 at 13:12 -0400, Tom Lane wrote:
I plan to provide the 1.2.x libpng shared library (and only the library,
not its devel support files) in a libpng-compat subpackage for the time
On Fri, 2011-11-04 at 13:12 -0400, Tom Lane wrote:
In either case, as per the discussion at
http://lists.fedoraproject.org/pipermail/devel/2011-October/157712.html
I plan to provide the 1.2.x libpng shared library (and only the library,
not its devel support files) in a libpng-compat
Nils Philippsen n...@redhat.com writes:
On Fri, 2011-11-04 at 13:12 -0400, Tom Lane wrote:
I plan to provide the 1.2.x libpng shared library (and only the library,
not its devel support files) in a libpng-compat subpackage for the time
being.
Any reason why the compat package ships the
...snip...
Excellent background and detective work! Kudos!
Some quick questions:
Whats upstreams schedule like? How long will 1.4 and 1.5 continue to be
supported, and when do they plan on a 1.6?
Is there possibly a way to switch to 1.4, but warn (buildtime) about
this going away soon, etc?
Once upon a time, Tom Lane t...@redhat.com said:
Any opinions on which way to jump?
How hard is it to fix source that accesses the fields directly? Do all
the fields that were previously exposed have direct accessor functions?
If that's the case, it should be straight-forward (although time
Kevin Fenzi ke...@scrye.com writes:
Some quick questions:
Whats upstreams schedule like? How long will 1.4 and 1.5 continue to be
supported, and when do they plan on a 1.6?
1.4 will be supported for a long time, though presumably not as long as
1.5. I don't think there are any active plans
On Fri, 04 Nov 2011 14:54:28 -0400
Tom Lane t...@redhat.com wrote:
Kevin Fenzi ke...@scrye.com writes:
Some quick questions:
Whats upstreams schedule like? How long will 1.4 and 1.5 continue
to be supported, and when do they plan on a 1.6?
1.4 will be supported for a long time,
Chris Adams cmad...@hiwaay.net writes:
Once upon a time, Tom Lane t...@redhat.com said:
Any opinions on which way to jump?
How hard is it to fix source that accesses the fields directly? Do all
the fields that were previously exposed have direct accessor functions?
AFAIK, they all do, and
fre 2011-11-04 klockan 13:12 -0400 skrev Tom Lane:
Packages that rebuilt successfully with 1.5 658
Packages that FTBFS for non-libpng reasons186
Packages that rebuilt with 1.4, but not 1.5 74
Packages that need help even with 1.4 46
With this data my gut feeling is to go for
On 13:12 Fri 04 Nov , Tom Lane wrote:
I have been looking into replacing Fedora's obsolete version of libpng
(1.2.x release series) with something more modern. The possible choices
are the 1.4.x and 1.5.x release series. The 1.5.x series adds some more
features that 1.4.x did not have,
Dr Andrew John Hughes ahug...@redhat.com writes:
FYI, Gentoo already went to libpng 1.5 and so have patches floating around
for a lot of stuff that breaks.
Oh, thanks, that's very useful to know! I think the availability of
such patches should substantially reduce the pain involved.
Given
Dr Andrew John Hughes wrote:
FYI, Gentoo already went to libpng 1.5 and so have patches floating around
for a lot of stuff that breaks.
from a _quick_ search:
http://software.opensuse.org/search?q=libpngbaseproject=openSUSE%3AFactorylang=enexclude_debug=true
suse1.4.x/1.2.x stable
Kevin Fenzi wrote:
Whats upstreams schedule like? How long will 1.4 and 1.5 continue to be
supported, and when do they plan on a 1.6?
forever :-?
See http://libpng.sf.net/
UPDATE 2 November 2011: The latest released version is libpng-1.5.6 [DOWNLOAD].
* For legacy applications,
Henrik Nordström wrote:
Documentaiton on how to adopt application code to work properly with
libpng 1.4+ is readily available.
Some notes from upstream: http://www.libpng.org/pub/png/libpng.html
==cut==
Portability Note
The libpng 1.5.x series continues the evolution of the libpng API,
22 matches
Mail list logo