| 1 |
I don't think I had any traces of libpng1.2. I followed these steps for updating my libpng. |
| 2 |
|
| 3 |
http://blog.flameeyes.eu/2010/06/29/stable-users-libpng-update |
| 4 |
|
| 5 |
So I had no traces of the old version. I haven't been using --as-needed. |
| 6 |
|
| 7 |
I depclean and revdep after every update, I have buildpackage in my features. My machine is already doing it's revdep back to 1.2. Hopefully it will be done when I get back in to work tomorrow. I'll let you know if that helps. |
| 8 |
|
| 9 |
--- On Thu, 7/8/10, Duncan <1i5t5.duncan@×××.net> wrote: |
| 10 |
|
| 11 |
> From: Duncan <1i5t5.duncan@×××.net> |
| 12 |
> Subject: [gentoo-desktop] Re: [kde-sunset] kmail-3.5.10 crashes |
| 13 |
> To: gentoo-desktop@l.g.o |
| 14 |
> Date: Thursday, July 8, 2010, 4:16 PM |
| 15 |
> Nicholas Robbins posted on Thu, 08 |
| 16 |
> Jul 2010 08:09:24 -0700 as excerpted: |
| 17 |
> |
| 18 |
> > Just a me-too message. I recently started having these |
| 19 |
> crashes as well. |
| 20 |
> > They started about when I upgraded to libpng1.4. |
| 21 |
> |
| 22 |
> Ugh. Sounds like you still have the earlier version, |
| 23 |
> and some library |
| 24 |
> using it, while another pulls in the new version, with both |
| 25 |
> used by kmail, |
| 26 |
> so it's pulling in both versions into the same executable, |
| 27 |
> and that's a |
| 28 |
> certain recipe for disaster, or at least crashes. |
| 29 |
> |
| 30 |
> I take it you've completed a revdep-rebuild and running it |
| 31 |
> now comes up |
| 32 |
> clean? Do you run with as-needed in your |
| 33 |
> ldflags? That will certainly |
| 34 |
> help, as will having lafilefixer in your portage |
| 35 |
> post-install hooked |
| 36 |
> routines. (If you don't know what I'm talking about, |
| 37 |
> you may want to read |
| 38 |
> up on flameeyes' blog... the mentioned tricks can |
| 39 |
> definitely save you a |
| 40 |
> **LOT** of trouble.) |
| 41 |
> |
| 42 |
> What about depclean? Do you use it regularly? |
| 43 |
> |
| 44 |
> If you're not doing that sort of stuff routinely, it may be |
| 45 |
> that a |
| 46 |
> complete emerge --emptytree world is needed to get the |
| 47 |
> cruft cleaned out, |
| 48 |
> but before you go to that trouble, I'd suggest setting up |
| 49 |
> as-needed in |
| 50 |
> your ldflags, lafilefixer in your post-install, doing a |
| 51 |
> --depclean -- |
| 52 |
> pretend and adding to world what you don't want removed, |
| 53 |
> and consider |
| 54 |
> setting FEATURES=buildpkg, before you do the rebuild, so |
| 55 |
> that when you're |
| 56 |
> done, you'll have the full world built cleanly with those |
| 57 |
> options, and |
| 58 |
> binpkg backups for every package, as well. After that |
| 59 |
> it should be MUCH |
| 60 |
> easier to keep up with routine maintenance, always doing a |
| 61 |
> revdep-rebuild |
| 62 |
> and a depclean (I always use ask, to see what it's going to |
| 63 |
> do, before |
| 64 |
> letting it go ahead, for both of these), after every update |
| 65 |
> or package |
| 66 |
> removal. |
| 67 |
> |
| 68 |
> -- |
| 69 |
> Duncan - List replies preferred. No HTML |
| 70 |
> msgs. |
| 71 |
> "Every nonfree program has a lord, a master -- |
| 72 |
> and if you use the program, he is your master." |
| 73 |
> Richard Stallman |
| 74 |
> |
| 75 |
> |
| 76 |
> |
Archives