status of 7.0

[Garance A Drosihn]

At 6:07 PM -0400 7/8/07, Garance A Drosihn wrote:
>At 1:25 PM +0200 7/8/07, Marc "UBM" Bocklet wrote:
>>
>>I'd like to do some testing, but I'm a little bit afraid of the upgrade
>>procedure 6.2-stable to -current. Is it possible to do a simple upgrade
>>if I follow the guidelines in UPGRADE or are there any hidden caveats?
>>(like "you've to recompile all installed ports", etc. :-))
>
>For what it's worth, I just recently upgraded one of my i386 machines.
>I first upgraded to the latest snapshot of 6.2-stable, and then I went
>from there to 7.x-current.  I just did that on Friday, so I can't say
>that I've tested everything yet.  But so far I haven't had any problems.

Okay, I just hit one non-obvious problem.  On the system I had
upgraded, 'portupgrade' was out-of-date, but 'ruby' had already been
updated before the switch to 7.x-current.  Portupgrade *was* working,
but then I tried to upgrade it and it stopped working.  Lots of errors,
and then a program-interrupt while trying to do 'pkgdb -fu'.

On a hunch, I did:
      cd /usr/ports/lang/ruby18
      make deinstall
      make
      make install && make clean

and then portupgrade went back to working fine.  So, there might be
some cases where you'll have to build a few ports even though they
are already up-to-date.

-- 
Garance Alistair Drosehn            =   gad at gilead.netel.rpi.edu
Senior Systems Programmer           or  gad at freebsd.org
Rensselaer Polytechnic Institute    or  drosih at rpi.edu