On Wednesday 30 June 2010 22:52:13 Alan McKinnon wrote:
> On Wednesday 30 June 2010 23:17:28 Mick wrote:
> > On Tuesday 29 June 2010 22:56:56 Alan McKinnon wrote:
> > > Seems like the horrendous screw-up that was the libpng-1.4 update never
> > > got fixed properly and is hitting stable users now.
> > > 
> > > Flameeyes, in his usual in-your-face style, has documented what needs
> > > to be done:
> > > 
> > > http://blog.flameeyes.eu/2010/06/29/stable-users-libpng-update
> > > 
> > > If you are a stable user, save yourself a lot of trouble over the next
> > > few days, read his blog and do what he says. He has this uncanny
> > > ability of almost always being correct on technical toolchain matters
> > 
> > Blast!  I emerged media-libs/libpng-1.4.3 only 2 days ago and ... I
> > followed what the elog told me which was to run the very scrip that
> > Flameeyes says it causes long term problems!  O_O
> > 
> > This is what I have in terms of libpng* (on an amd64 system):
> > 
> > # ls -la /usr/lib/libpng*
> > -rw-r--r-- 1 root root 236422 Jun 28 12:56 /usr/lib/libpng14.a
> > -rw-r--r-- 1 root root    935 Jun 28 12:57 /usr/lib/libpng14.la
> > lrwxrwxrwx 1 root root     18 Jun 28 12:56 /usr/lib/libpng14.so ->
> > libpng14.so.14.3.0
> > lrwxrwxrwx 1 root root     18 Jun 28 12:56 /usr/lib/libpng14.so.14 ->
> > libpng14.so.14.3.0
> > -rwxr-xr-x 1 root root 158400 Jun 28 12:56 /usr/lib/libpng14.so.14.3.0
> > lrwxrwxrwx 1 root root     10 Jun 28 12:56 /usr/lib/libpng.a ->
> > libpng14.a -rw-r--r-- 1 root root    935 Jun 28 12:57 /usr/lib/libpng.la
> > lrwxrwxrwx 1 root root     11 Jun 28 12:56 /usr/lib/libpng.so ->
> > libpng14.so
> > 
> > # ls -la /usr/lib64/libpng*
> > -rw-r--r-- 1 root root 236422 Jun 28 12:56 /usr/lib64/libpng14.a
> > -rw-r--r-- 1 root root    935 Jun 28 12:57 /usr/lib64/libpng14.la
> > lrwxrwxrwx 1 root root     18 Jun 28 12:56 /usr/lib64/libpng14.so ->
> > libpng14.so.14.3.0
> > lrwxrwxrwx 1 root root     18 Jun 28 12:56 /usr/lib64/libpng14.so.14 ->
> > libpng14.so.14.3.0
> > -rwxr-xr-x 1 root root 158400 Jun 28 12:56 /usr/lib64/libpng14.so.14.3.0
> > lrwxrwxrwx 1 root root     10 Jun 28 12:56 /usr/lib64/libpng.a ->
> > libpng14.a -rw-r--r-- 1 root root    935 Jun 28 12:57
> > /usr/lib64/libpng.la lrwxrwxrwx 1 root root     11 Jun 28 12:56
> > /usr/lib64/libpng.so -> libpng14.so
> > 
> > Is this OK?  What now?
> 
> I remember now what I eventually did to fix all my libpng problems back
> then:
> 
> unmerge libpng
> delete everything left with libpng in it's name
> emerge -pvuND world just to see what was now busted
> same with revdep-rebuild
> re-emerge libpng and let portage pick the version to merge
> emerge -avuND world
> revdep-rebuild
>   repeat till no problems reported
> 
> and lafilefixer --justfixit somewhere in the mix as well just for good
> measure.
> 
> This is called the "throw shit at the wall and hope some of it sticks"
> method of updating systems. By happy good fortune, it worked out for me.
> 
> aka the dark underside of source-based systems :-)

I'm sure that I followed your scientific approach too because my system still 
works ... although I may have lost the will to live somewhere in between the 
lafilefixer and revdep-rebuild for the nth time and decided to emerge -e 
world.  :-))

Strangely enough two other x86 boxen were updated without any much drama.
-- 
Regards,
Mick