Recent massive port update.

Ion-Mihai Tetcu itetcu at FreeBSD.org
Sun Feb 7 09:19:42 UTC 2010


On Sat, 6 Feb 2010 15:53:57 -0600
ajtiM <lumiwa at gmail.com> wrote:

> On Saturday 06 February 2010 15:36:22 Miroslav Lachman wrote:
> > Ion-Mihai Tetcu wrote:
> > > On Sat, 06 Feb 2010 21:05:54 +0100
> > >
> > > Miroslav Lachman<000.fbsd at quip.cz>  wrote:
> > >> Matthew Seaman wrote:
> > >>> -----BEGIN PGP SIGNED MESSAGE-----
> > >>> Hash: SHA1
> > >>>
> > >>> On 06/02/2010 09:40, Heino Tiedemann wrote:
> > >>>> Shouldn't there be an entry in UPDATING, that "jpeg" has to be
> > >>>> rebuildet first?
> > >>>>
> > >>>> I rebuilded everything - but i have no idea about the order aof
> > >>>> port reinstalling.
> > >>>
> > >>> Actually that's not necessary in this case entirely because the
> > >>> commit was so large.  Every port that needs to be rebuilt
> > >>> because it depends on libjpeg has had it's PORTREVISION
> > >>> bumped.  That means that if you just do a 'portupgrade -a' or
> > >>> 'portmaster -a' the right thing will happen automatically.
> > >>
> > >> No metter if there is revision bump or not, it should be in
> > >> UPDATING as it was in case of jpeg-7.
> > >>
> > >> 20090719:
> > >>     AFFECTS: users of graphics/jpeg
> > >>     AUTHOR: dinoex at FreeBSD.org
> > >>
> > >>     The IJG jpeg library has been updated to version 7.0.  Please
> > >> rebuild all ports that depend on it.
> > >
> > > No need, since it a port has a new version, a rebuild is expected.
> > 
> > Is expected, but if somebody are not using portmaster or
> > portupgrade, simple upgrade of jpeg will break other ports and I
> > think that in the case of jpeg (widely used library) there will be
> > a lot of users asking "why my app XYZ is not working anymore".
> > 
> > So what was the reason to put UPDATING entry 20090719 for jpeg 7,
> > if it is no longer needed for jpeg 8?
> 
> And in my case, I use portmaster, rebuilding of QT33 and arts doesn't
> work and I screw many applications. Thank you for your hard work but
> I don't know why is a rush for something which doesn't work?

This is a QT / KDE problem. It doesn't depend on the tool you use
(portmaster, portupgrade or simple make). It would manifest if any of
the libs those KDE libs are linked against would have their versions
bumped. And it only manifest itself if QT / KDE is already installed,
hence we couldn't catch it on the cluster.

In other words, QT 3 / KDE 3 ports are in wrong, and the fact that we
see this problem after jpeg upgrade is an accident (in the sense that
it has nothing to do with jpeg).

-- 
IOnut - Un^d^dregistered ;) FreeBSD "user"
  "Intellectual Property" is   nowhere near as valuable   as "Intellect"
FreeBSD committer -> itetcu at FreeBSD.org, PGP Key ID 057E9F8B493A297B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20100207/9202c638/signature.pgp


More information about the freebsd-ports mailing list