Date: Tue, 28 Jul 2009 10:43:23 -0700 From: "Kevin Oberman" <oberman@es.net> To: Andriy Gapon <avg@icyb.net.ua> Cc: ports@freebsd.org, gnome@freebsd.org, Joe Marcus Clarke <marcus@freebsd.org> Subject: Re: after update - not all jpeg files are displayable Message-ID: <20090728174323.869591CC31@ptavv.es.net> In-Reply-To: Your message of "Tue, 28 Jul 2009 20:05:14 %2B0300." <4A6F2FCA.2080908@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Tue, 28 Jul 2009 20:05:14 +0300 > From: Andriy Gapon <avg@icyb.net.ua> > Sender: owner-freebsd-gnome@freebsd.org > > on 28/07/2009 19:56 Joe Marcus Clarke said the following: > > > > No. It's an issue with an incomplete PORTREVISION bump on ports which > > depend on libjpeg. Really, you need to do a portupgrade -rf jpeg to fix > > this. What you must avoid is one port being linked to both jpeg.9 and > > .10. When that happens, applications crash trying to open JPEGs. > > This is not an issue for me as far I can see. > libchk reported that no binaries/libraries were linked to libjpeg.so.9 in > lib/compat/pkg - I have even removed it now from . > Everything is linked to libjpeg.so.10, no unresolved libraries. > > Any further suggestions? > Maybe you could try to reproduce the issue for yourself? I have had things slip through libchk in the past. I did a 'portupgrade -rf jpeg' and rebuilt about 295 ports on all three of my systems running Gnome. That seems to have gotten everything happy again. (Of course, rebuilding 290+ ports does take a bit of time.) Gee.This might be a good time to try 8.0-Beta! You will need to re-build all ports then, anyway. ;-) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090728174323.869591CC31>