Xorg 7.2 update

Kris Kennaway kris at obsecurity.org
Mon May 28 21:06:27 UTC 2007


On Mon, May 28, 2007 at 09:50:09PM +0100, Chris wrote:
> On 28/05/07, Giorgos Keramidas <keramida at ceid.upatras.gr> wrote:
> >On 2007-05-28 09:47, Andreas Klemm <andreas at freebsd.org> wrote:
> >> Hi,
> >> 1st of all, thanks for providing 7.2 in the tree !
> >
> >Well said.  The Ports team and the people who did the pretest runs with
> >the xorg update, before it was even committed, are the ones who deserve
> >all the thanks.  Thank you all guys :)
> >
> >> I had another little problem with xorg. While you did an upgrade
> >> installation, I nuked all of my ports and started over.
> >>
> >> I discovered, that an installation by compiling all myself failed
> >> very early.
> >>
> >> Its easily to reproduce by installing on a vanilla empty system.
> >>
> >> Sorry I didn't save the error message.
> >
> >Oh I did both :)
> >
> >First I tried "pkg_delete *", and rebuild everything.  One tricky part
> >here is that despite the fact that _nothing_ is installed, you have to
> >export XORG_UPGRADE='yes' in the environment before building from
> >scratch.  It's kind of unintuitive that you have to specify _UPGRADE_
> >for a clean installation, but it works fine.
> >
> >Then, I updated my ports tree again, after a couple of days:
> >
> >   portsnap fetch update
> >
> >and rebuilt everything with:
> >
> >   portupgrade -vu -N -ar
> >
> >A new version of the freetype2 port triggered a full xorg update, this
> >time using portupgrade.  XORG_UPGRADE='yes' is still required in the
> >running environment.
> >
> >It's hard to guess without seeing the exact error message, but if it was
> >related to `x11/xorg-libraries', then you were probably bitten by the
> >lack of $XORG_UPGRADE in the environment.  If you do repeat the build,
> >can you try catching any errors inside a script(1) session?  That would
> >be nice to have :)
> >
> >- Giorgos
> >
> >_______________________________________________
> >freebsd-current at freebsd.org mailing list
> >http://lists.freebsd.org/mailman/listinfo/freebsd-current
> >To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
> >
> 
> My concerns are these.
> 
> 1 - Was this tested on freebsd 5. if no should the port have been made
> to not install on 5.x, on a 5.x server I admin it has completely hosed
> the ports setup I had to use pgdb -F to remove all x11 dependencies
> that wont compile there is at least 5 diff x11 ports now that wont
> compile or install with pkg_add.

Yes, 5.x was tested.  In fact a complete package build has been
uploaded to the FTP servers, so it is known that it is in very good
shape.

> 2 - I read UPDATING but there is no mention of the
> USE_NONDEFAULT_X11BASE=yes I had to set on freebsd 6.1 servers, is it
> assumed everyone is using either 6.2 or 7.0? and is
> USE_NONDEFAULT_X11BASE=yes the correct one to use when also using
> WITHOUT_X11=    yes and WITHOUT_XPM=    yes?

Older releases are not officially supported by ports, but should
probably work.  As the error message instructs you,
USE_NONDEFAULT_X11BASE should be set.

Kris


More information about the freebsd-current mailing list