Unhappy Xorg upgrade

[vehemens]

On Saturday 31 January 2009 01:25:21 pm Alex Goncharov wrote:
> ,--- You/vehemens (Sat, 31 Jan 2009 11:53:58 -0800) ----*
>
> | In general when upgrading, you take your chances.  If a port upgrade
> | fails, you should fall back to what worked.
>
> So, a *fundamental* (practically an OS component) port is brought in
> -- and it disables my system.  What is my way of action?  Right --
> install the old packages, taken from an FTP site (is there a way to
> get the previous "source", that is all the ports/*/*/Makefile files?
> Csup can only go forward -- or can it go back?)

You ignored the first part of the email which is that the ports system is 
flawed due to the lack of a stable versus current branch.  It seems to me 
that you want to run a stable branch, while the ports tree is effectively a 
current branch.

> When I install the old packages, I can no longer rebuild and install
> new (say `csup'ed on 2009-03-01) port components, as one whole -- I
> can only do it selectively, excluding from the upgrade most
> X-dependent things.  That sucks and will lead to a problem earlier or
> later.

I never update /usr/ports directly.  I have a separate csup ports area.  When 
I update, I save the old ports tree and replace it with a new one.  If a 
problem occurs, I can fall back to the old tree or pieces of it.

> | Trying to partial rebuild ports versus rebuilding from scratch after
> | a major update is just asking for problems.
>
> Exactly -- but I haven't done this -- and I have big problems with the
> new X.
>
> | There probably needs to be a more incremental approach when
> | upgrading major ports.  For example, I updated my system a piece at
> | a time over the last several months, and had no significant problems
> | with the offical x11 upgrade as the changes were small.
>
> I've been rebuilding and reinstalling ports every weekend, for about
> 1.5 years -- with no problem until the last one, when the new X was
> in.

Well, it depends on which ports you are updating.  If you only run X, then I 
would expect your statement to be correct.

> | And last, many of the video drivers have little if any support.  If
> | you have something other then ati/intel/nivdia, you should expect
> | problems.  Input drivers are in a similar state.
>
> Both my systems I've been reporting problems with are using the `nv'
> driver:
>
>   $ grep /modules/drivers /var/log/Xorg.0.log
>   (II) Loading /usr/local/lib/xorg/modules/drivers//nv_drv.so
>
> One system (Dell Latitude) could not be made operational with the new
> X at all; the other has garbage in the windows and the "captive mouse
> pointer" -- both issues new in the new X.

See above :)