upgrading all ports
nikolas.britton at gmail.com
Mon Jun 27 18:46:04 GMT 2005
On 6/27/05, Denny White <dennyboy at cableone.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On Mon, 27 Jun 2005, Nikolas Britton wrote:
> >> This couldn't have come at a better time for me.
> >> I really boned things up about 40 hours ago. I was
> >> getting ready to leave and because I'd been doing
> >> some learning/experimenting with portupgrade on
> >> some held ports, I hit the wrong switch. I think
> >> it was portupgrade -arRF & now, about 40 hours
> >> later, shortly after returning home, we're still
> >> going, going, going....... Things are really in
> >> a mess & I've read the recent posts on this thread
> >> & can attest, sitting here for several hours, that
> >> "visits some ports many times" is an understatement.
> >> It's becoming rediculous & I'm wondering if, at
> >> some point, when clean is going after something
> >> else was just upgraded, if I can break out & go
> >> back with a simple portupgrade -arR & not screw
> >> things up to badly. Any help/feedback on this will
> >> be GREATLY appreciated. :)
> >> Denny White
> > You shouldn't have any problems if you do that but kill it at the
> > beginning of the next build, not when it's cleaning.
> Thanks so much for the personal speedy reply. I've worked
> for a month getting this system to about where I want it,
> & I hate to see it all go down the tubes. Sure glad you
> straightened me out on when to break out, too. I see you
> didn't put in a cc to freebsd-questions, so I guess I
> won't either. After breaking out of the loop, what's the
> best thing to do at that point? The only way I could come
> up with to try to start is:
> cvsup ports-supfile
> portsdb -Uu
> portversion -l "<"
> portupgrade -arR (no F this time)
Just restart portupgrade without the F flag, it will pick-up where it left off.
> If I can get things back right, I'll just learn to live
> with the "held" ports. I never remember telling it to
> hold anything, & it's probably pretty apparent I don't
> understand as much as I should about portupgrade. I
> learned what I know from Dru Lavigne's blogs at Oreilly,
> & until I fat-fingered the F without thinking, it was
> working okay, except for the held ports. Thanks again
> for your help.
> Denny White
I'm not sure what you mean by held ports?
More information about the freebsd-questions