On Wed, May 02, 2007 at 03:26:25PM -0600, Coleman Kane wrote: > On Wed, 2007-05-02 at 15:43 -0400, Kris Kennaway wrote: > > On Wed, May 02, 2007 at 02:40:26PM -0500, Stephen Montgomery-Smith wrote: > > > > > > > > > On Wed, 2 May 2007, Kris Kennaway wrote: > > > > > > >Hi all, > > > > > > > >After many months of hard work (mostly by flz@, as well as others) we > > > >are approaching readiness of the xorg 7.2 upgrade. Because this is a > > > >huge and disruptive change, we're going to approach it very carefully. > > > > > > I tried X 7.2 about a week ago, and I can report some minor problems. > > > > > I've been following the xorg 7.2 tree for some time, and recently around > the time of either the move to /usr/local or the ruby18 update (they > happened pretty close together for me) portupgrade -na seems to have > broken for me. It just hangs there forever, seemingly doing something in > the background and never actually starts checking for updated ports. > Tried rebuilding INDEX, INDEX.db, and pkgdb.db to no avail... Once I let > it go overnight and the process died with an Illegal Instruction > signal...
One of the effects of portupgrade -a using the wrong upgrade order is that is possible to introduce cycles into the dependency graph (A depends on B, B depends on A, where I have seen A = xorg-libraries and B = libXft). In my case it was pkg_create and a cycle in the +REQUIRED_BY lists (pkg_create looped for an hour between these two ports but eventually gave up and proceeded). It is possible that portupgrade might get itself into a similar state somehow. pkgdb -L might fix it for you. Kris _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
