On 06 Nov 2008, at 04:11, Jean-François Mertens wrote:
> Does upstream have anything to say about why they
> don't want to incorporate it ?
OK _ (at least part of) the discussion seemsto be here :
http://sourceforge.net/mailarchive/message.php?
msg_name=3.0.6.32.20070420132821.012dd8e8%40mail.
On 06 Nov 2008, at 02:45, David R. Morrison wrote:
> Here's what I managed to find out about APNG:
>
> http://littlesvr.ca/apng/
>
> It looks like a patch that is no longer being maintained by its author
> and has not been integrated into the main line of libpng code. How
> should we proceed?
N
David R. Morrison wrote:
> Here's what I managed to find out about APNG:
>
> http://littlesvr.ca/apng/
>
> It looks like a patch that is no longer being maintained by its author
> and has not been integrated into the main line of libpng code. How
> should we proceed?
That is correct. The l
File bug against seamonkey upstream? Seems poor for them to require
unreleased code in an external dependency (and at best they should be
forced to know they're doing so). Or does seamonkey have an on-board
libpng source and upstream will just say "use the one we ship"?
dan
On Wed, Nov 05, 2008 a
Here's what I managed to find out about APNG:
http://littlesvr.ca/apng/
It looks like a patch that is no longer being maintained by its author
and has not been integrated into the main line of libpng code. How
should we proceed?
-- Dave
On Nov 4, 2008, at 6:27 PM, Jean-François Mertens
It appears to screw up colors on some types of PNG images.
Before (libpng-1.2.5-4):
http://ranger.befunk.com/misc/libpng-1.2.5-4.jpg
After (libpng-1.2.6-6):
http://ranger.befunk.com/misc/libpng-1.2.6-6.jpg
:P
--
Benjamin Reed, a.k.a. Ranger Rick
[EMAIL PROTECTED] / http://ranger.befunk.com/
"Ye
Hi David,
I just got an email warning for our RedHat Enterprise Linux 3 subscriptions that
there's a security issue for libpng 1.2.5. Sure enough, there's a note at
http://www.libpng.org/pub/png/libpng.html
Regards,
Blair
--
Blair Zajac <[EMAIL PROTECTED]>
Plots of your system's performance - ht
That document from Apple's site is a bit misleading, in a number of respects.
For example, you don't need to install zlib under 10.2 because it is
already there!
In the Fink project, we updated to the latest version of libpng a while
back, and the new Fink package is called "libpng3".
-- Dave
On Freitag, Juni 20, 2003, at 07:23 Uhr, Craig Hotchkiss wrote:
I'm trying to configure my php install with the libpng library based
on the instructions from
http://developer.apple.com/internet/macosx/php.html and have run into
an error (libpng.(also) not found.) where it appears that libjpg i
Title: Message
I'm trying to
configure my php install with the libpng library based on the instructions from
http://developer.apple.com/internet/macosx/php.html and
have run into an error (libpng.(also) not found.) where it appears that libjpg
is dependent on libpng. I installed and setup fi
I can do it. Let me make sure I put down an answer that is useful:
1) The problem only afflicts unstable, correct?
2) The problem is being fixed.
3) Users should start by updating those packages that are complaining.
4) If the update doesn't solve the problem, let the maintainer know.
On Mon, 3
Maybe we can add a FAQ item on the libpng / libpng3 issue. I know we
are transiting to libpng3 anyway, but for those people in a (semi)
broken state already it would be nice if they had a way to find out
what is going on and how to get out of it. Also it would be
convenient for us: whenever a m
On Thursday, February 6, 2003, at 10:06 PM, Randal L. Schwartz wrote:
About half of the packages I install replace libpng3 with libpng. And
the other half replace libpng back with libpng3.
I wish they'd make up their mind.
Which is it? And why are these two packages so easily replaced with
About half of the packages I install replace libpng3 with libpng. And
the other half replace libpng back with libpng3.
I wish they'd make up their mind.
Which is it? And why are these two packages so easily replaced with
each other? Surely, libpng3 has to have more things than libpng,
right?
At 14:44 Uhr -0500 30.01.2003, David R. Morrison wrote:
Sure, but I think there are really two things going on.
1) If you have an old imlib and are building a package which links libpng3,
there is no way you can ever build it correctly.
Could somebody explain to me why exactly this is a problem
Sure, but I think there are really two things going on.
1) If you have an old imlib and are building a package which links libpng3,
there is no way you can ever build it correctly.
2) If you've updated imlib, then once in a while, due to a bug in fink,
you'll have a problem with libpng vs. libpng
On Thursday, January 30, 2003, at 02:28 PM, David R. Morrison wrote:
I think actually it is packages that use imlib that we need to be more
concerned about, than libpng. Any package using both imlib and libpng
should be updated to libpng3, and also should have a versioned
dependency
on the late
I think actually it is packages that use imlib that we need to be more
concerned about, than libpng. Any package using both imlib and libpng
should be updated to libpng3, and also should have a versioned dependency
on the latest imlib from unstable.
-- Dave
---
Would it be helpful for me to come up with a list of remaining packages
that use libpng, sorted by maintainer?
--
Alexander K. Hansen
Associate Research Scientist, Columbia University
visiting MIT Plasma Science and Fusion Center
Levitated Dipole Experiment
175 Albany Street, NW17-219
Cambridge, M
Seems vitriolic.
It looked like there was some confusion with respect to the cause of the
problem, so I posted a clarification including the imlib version
numbers.
On Tue, 2003-01-21 at 13:38, David R. Morrison wrote:
> In case anyone wants to follow the thread over at macosxhints forum, here
> i
In case anyone wants to follow the thread over at macosxhints forum, here
it is:
http://forums.macosxhints.com/showthread.php?s=&postid=43170#post43170
---
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training?
From: Thomas Thatcher <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Hi Dave,
An avid fink user in the MacOSX Hints forum has reported an unusual
problem this morning. I wonder if you might know anything about it
since the cvs update for this morning installed new versions of libpng
which is supp
So I've been running into weird runtime errors when using libpng...
KDE and Qt had been updated to use libpng3 instead of libpng back in
the 3.1 betas. Unfortunately, it turns out that not everything KDE
links against has been, and it turns out that in certain situations, it
freaks out. :(
=?ISO-8859-1?Q?Jorge_Acereda_Maci=E1?= <[EMAIL PROTECTED]> wrote:
> On Sunday, February 10, 2002, at 05:08 PM, David R. Morrison wrote:
>
> > The libpng library has been updated recently in a way that is not
> > backward-compatible. Our new shared libraries policy can handle this
>
> Where can
The libpng library has been updated recently in a way that is not
backward-compatible. Our new shared libraries policy can handle this
gracefully, but only after every package which Depends on libpng is
revised to say:
Depends: libpng-shlibs
BuildDepends: libpng
The new libpng3 and libpng3-s
At Peter's suggestion, I am enclosing the info files for libpng and
libpng-shlibs. Perhaps studying them will help folks figure out how
this works. (It certainly took a while for it to sink in, for me!)
There are also patch files, which are identical for the two packages
(and copied from the pr
I'll take over as the new libpng maintainer (from chrisp). I made a fink
package for the latest upstream version. However, I have not put it on
CVS, because the major version number has changed and if you install the
new one, you will break around a dozen other packages which depend on it
(unles
27 matches
Mail list logo
