Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 27 Mar 2010 20:10:41 +0100
From:      Erik Trulsson <ertr1013@student.uu.se>
To:        Programmer In Training <pit@joseph-a-nagy-jr.us>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Enough Is Enough
Message-ID:  <20100327191041.GA66104@owl.midgard.homeip.net>
In-Reply-To: <4BAE4E4A.4000002@joseph-a-nagy-jr.us>
References:  <4BAE3E5C.8020905@joseph-a-nagy-jr.us> <201003271906.24857.tijl@coosemans.org> <4BAE4E4A.4000002@joseph-a-nagy-jr.us>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 27, 2010 at 01:28:26PM -0500, Programmer In Training wrote:
> On 03/27/10 13:06, Tijl Coosemans wrote:
> <snip>
> > In /usr/ports/UPDATING look for the 20100205 entry for "users of Qt 3
> > and KDE 3".
> 
> Pointless in as far as that does not address the underlying problem of
> rebuilding EVERYTHING that needs to link against the jpeg library. GIMP
> and gegl failed because a dependency for it is linked against jpeg-7 and
> not jpeg-8.
> 
> If I cannot basically reinstall the entire system via portupgrade -a I'm
> reduced to fixing the problem ad-hoc and that is unacceptable because
> eventually I'll have to deal with programs that link to whatever just
> got rebuilt. In essence, this is a problem that is not easily solved
> just by reading /usr/ports/UPDATING for Qt because it involves more than
> Qt (by the way, thanks for the hat tip on Qt, but it's not high on my
> priority list for being fixed right now, GIMP, Scribus and possibly a
> few other apps that I'm currently unaware of there being an issue with
> ARE).

So don't use portupgrade if doesn't do what is needed.

The simple solution is to *first* deinstall *all* ports (or at least
all ports that depend, directly or indirectly, on jpeg in this case)
and then reinstall them all.  This might require a bit more manual
intervention than using portupgrade would have, but on the other hand
it is almost guaranteed to work correctly every time.

The problems you are running into is essentially due to trying to build
updated binaries while still having old binaries installed (and having
this trigger bugs in the build mechanism of various ports.)
If you first remove all the old binaries and then build new ones you
avoid many potential problems.



-- 
<Insert your favourite quote here.>
Erik Trulsson
ertr1013@student.uu.se



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100327191041.GA66104>