From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Stable users: libpng-1.4
Date: Wed, 30 Jun 2010 23:15:34 +0100 [thread overview]
Message-ID: <201006302315.35754.michaelkintzios@gmail.com> (raw)
In-Reply-To: <201006302352.14268.alan.mckinnon@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 3446 bytes --]
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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-06-30 22:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 21:56 [gentoo-user] Stable users: libpng-1.4 Alan McKinnon
2010-06-30 0:16 ` Willie Wong
2010-06-30 12:10 ` Alan McKinnon
2010-06-30 13:00 ` Dale
2010-06-30 21:17 ` Mick
2010-06-30 21:30 ` Bill Longman
2010-06-30 23:27 ` Peter Humphrey
2010-06-30 21:52 ` Alan McKinnon
2010-06-30 22:15 ` Mick [this message]
2010-06-30 22:35 ` Alan McKinnon
2010-07-01 9:05 ` Dale
2010-06-30 22:40 ` Neil Bothwick
2010-07-01 1:05 ` Willie Wong
2010-07-04 12:52 ` Philip Webb
2010-07-04 16:24 ` Dale
2010-07-04 19:10 ` Philip Webb
2010-07-04 20:44 ` Dale
2010-07-05 5:12 ` [gentoo-user] " Grant Edwards
2010-07-05 6:05 ` Dale
2010-07-06 5:34 ` Grant Edwards
2010-07-06 9:40 ` Dale
2010-07-06 23:34 ` Walter Dnes
2010-07-05 7:39 ` Neil Bothwick
2010-07-05 7:45 ` Alan McKinnon
2010-07-05 12:20 ` Philip Webb
2010-07-06 0:08 ` Jake Moe
2010-07-06 5:36 ` Grant Edwards
2010-07-06 8:18 ` Neil Bothwick
2010-07-04 19:11 ` [gentoo-user] " Mick
2010-07-04 20:48 ` Dale
2010-07-05 5:10 ` [gentoo-user] " Grant Edwards
2010-07-05 12:17 ` Philip Webb
2010-07-01 1:30 ` walt
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=201006302315.35754.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@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