Downgrading
 

You don't even have to force-remove it. If you use "fink install imlib-1.9.10-9", a downgrade should occur automatically (I did it this afternoon).

Glanz,

There you have it, try that and let us know.

akhansen,

Are you 'the Alexander' that will all know, who helps hundreds of lost souls find their way at fink-users?

% fink -V
Package manager version: 0.11.2
Distribution version: 0.5.1.cvs

status name installed binary stable unstable category summary version
archived libpng 1.0.12-6 1.0.12-6 graphics PNG image format handling library 1.0.12-6
current libpng-shlibs 1.0.12-6 1.0.12-6 1.0.12-6 graphics PNG image format handling library 1.0.12-6
current libpng3 1.2.5-2 1.2.5-2 1.2.5-2 graphics PNG image format handling library 1.2.5-2
current libpng3-shlibs 1.2.5-2 1.2.5-2 1.2.5-2 graphics PNG image format handling library 1.2.5-2


#################
libpng warning: Application was compiled with png.h from libpng-1.2.5
libpng warning: Application is running with png.c from libpng-1.0.12
libpng error: Incompatible libpng version in application and library
gdk_imlib ERROR: Cannot load image: /sw/share/galeon/spinners/galeon/026.png
All fallbacks failed.
#######################and
libpng warning: Application was compiled with png.h from libpng-1.0.12
libpng warning: Application is running with png.c from libpng-1.2.5
libpng error: Incompatible libpng version in application and library

##################

The imlib downgrade worked!!!!
Hooooooooray!!!!!!!!!!!!!!!!!!!!!!

May I stop ranting now??????????

PleeeeeeZZZZZZZZZZZZZZZZZz

Phew!!!!!!!!!

That just goes to show ya how little I know!

Greetings from one of the Fink project leaders.

We're pretty proud of our responsiveness to user concerns over at Fink. We run three mailing lists there, and people who post problem reports on those lists usually get rapid responses.

We don't monitor other forums such as this one, however, so it is quite distressing to see people reporting on problems with Fink, mis-diagnosing them (as in this case), but NEVER bringing the matter to the attention of the Fink team.

In the case at hand, although the error messages referred to libpng, the cause was an update to the imlib package in Fink's unstable tree. If you downgrade your imlib package as mentioned earlier, everything should work fine.

I wonder if I should downgrade imlib even though I haven't had any problems? Of course, I don't have the whole gnome set up as Glanz and sao do.

David,

It's an honor that you pay us a visit. Here in the forums, you will probably find some of your most loyal Fink fans.

Glanz, probably panicked a bit to much, and I'm glad the solution to his problems is quite easy actually.

Please, I hope you can keep coming to visit us, if you can squeeze some free time to post here.

thatch:

You may not need to downgrade, unless you have problems with specific applications. One problem that I saw which surprised me is that the Eterm scrollbar disappeared.

Anyway, once you have deb files for both versions, you can switch back and forth.

sao:

I am indeed the same Alexander. dmrrsn pointed this thread out to me, and I saw that there was a bit of confusion, so I figured it would be a good idea to clarify the situation.

-- oops, that was already posted :)

Wow, what an honor to have you both here and at the same time..!

I'm not worthy....:)

Thanks a lot for coming and hope you stay for long.

What's this,... and now Ben Hines too, wowwww...!

This start to look like fink-users...

I brought this to the fink team's attention as soon as I found out about it for the benefit of all and at the unfortunate cost to Glanz. I also reported back here that it was imlib via quote from the fink team. So, somehow it apparently got misconstrued after that.

Okay, thanks for the reply. I'm just going to sit tight until I see something not right, otherwise do nothing.

thatch,

I know your intentions were very noble and good, trying to help Glanz, but you nearly brought the whole Fink Developers Team to visit us for a simple, little problem. :D

Best, is not to panic when some problem comes out, and is good to remember that everything has a solution, somehow.

Unfortunately, tonight I was late to come around.

sao,

I didn't panic. I just reported the problem. Glanz was too upset to do so and so I did it for him. Am I wrong for that?

Not at all...

Maybe just a bit loud...:D

I had a good laugh when I started seeing all the familiar faces from Fink. :)

I don't understand what about my reporting the problem for Glanz was loud. Could you please elaborate on what it was that I said that sounded loud to you?

Thatch,

Sorry if you misunderstood my words. Nothing personal here, on the contrary.

Okay then. It just kind of sounded like you thought I was being panicky and loud, neither of which I thought I was.

Looking back to the beginning of this thread, I was trying to calm Glanz down and be patient for a possible solution. And just to be clear, some quotes that were not referenced by anyone early in the thread that I posted were from the package maintainer and not from me.

I just don't want to be associated with panicking, being loud, not reporting or mis-diagnosing here.

thatch,

I apologize if you took my "mis-diagnosis" comment as being directed at you. You were extremely helpful in bringing this matter to the attention of the Fink team. This mis-diagonis, made by the original poster, was the assumption that the problem was with libpng, when in fact it was with imlib.

-- Dave

dmrrsn,

Thanks for saying so. For a minute there, I was feeling like the messenger who got killed.

And thanks for all your tremendous efforts at the fink project. As sao had said, you'll find a lot of fink users here that know it to be the greatest and so they are very loyal. And I am one.

Now I am certain.......
that....
any attempt to "upgrade" Gnome in the unstable tree will result in new and wonderful imlib crashes, new and refreshing ways to NOT render Portable Network Graphics, new ways to totally eliminate widgets from all browsers and window frames..., and the list goes on.

Granted, Fink uses APT, but this ends the similarity with Debian. For example, if you try to install something from the unstable tree that will affect the stability of "stable" apps already installed, you will be notified by APT. In Debian, one simply cannot do an upgrade that will render the system useless. In FINK, unhappily, this is not only a regular occurance, but it seems to be a way for their developers to get "testing" feedback because it is becoming evident they do little testing themselves.

Is this a criticism, you may ask? Yes it is..., but it's not the end of the world. The only criticism I have then is that it seems that the developers don't even bother to launch some of the apps they place in the unstable tree.

So I am hereby giving notice to them that the word "unstable" is just that.... a word. Therefore they may feel free (hopefully) not to take "unstable" as a requirement just to be semantically correct.

The purpose of APT/dpkg and the Debian tools is not only to facilitate installations of "no matter what" no matter what the effect. The Debian APT system was developped to insure relative system stability, even in the "unstable" distribution by averting the user of possible or certain inconsistencies. But that takes someone (hopefully human) to actually write the text of these warnings, and someone conscient, after a minimal amount of testing, of the possible inconsistencies.

It shouldn't be just a chaotic "grab-bag" of crashy applications emitted for feedback.