Date: Mon, 27 Jun 2005 13:46:02 -0500 From: Nikolas Britton <nikolas.britton@gmail.com> To: Denny White <dennyboy@cableone.net>, FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: upgrading all ports Message-ID: <ef10de9a05062711463fe2d9b1@mail.gmail.com> In-Reply-To: <20050627131609.P20858@dualman.cableone.net> References: <20050625112256.GA32433@lothlorien.nagual.st> <200506271318.18073.list-freebsd-2004@morbius.sent.com> <20050627112833.I11987@dualman.cableone.net> <ef10de9a05062710437b9a5272@mail.gmail.com> <20050627131609.P20858@dualman.cableone.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/27/05, Denny White <dennyboy@cableone.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 >=20 >=20 > On Mon, 27 Jun 2005, Nikolas Britton wrote: >=20 > >> > >> 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. > > > > >=20 > 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ef10de9a05062711463fe2d9b1>