I cvsuped Wednesday, March 27 at 4:32 PM PST. I ran portupgrade -vr ruby (which upgraded portupgrade to 20020327.2) I then ran portupgrade -vr gettext (which upgrade gettext and ORBit). After upgrading ORBit, there was a hang during "Cleaning out obsolete shared libraries" (I assume this is part of portsclean -L) After several (close to five) minutes, I hit control-C, and portupgrade continued. (Nothing else needed to be upgraded, and portupgrade reported the results.) I then ran portupgrade -v linux-netscape, and portupgrade again hung in the same place. Again, a control-C allowed portupgrade to finish successfully. However, I am not sure that portsclean -L is actually finishing, since I don't see any reference to ldconfig running. How-To-Repeat: Try to portupgrade a port with shared libraries.
I ran portsclean -L (in non-interactive mode). portsclean still asked me a question and stopped and waited for input from me. overwrite /usr/local/lib/compat/pkg/libfreetype.so.6? (y/n [n]) My guess is that running portsclean -L from within portupgrade does not print the question to the console, so it is waiting for a user response which never comes. This appears as a hang in portupgrade. My response of control-C stopped portsclean and allowed portupgrade to continue. Al -- Albert Kinderman California State University, Northridge Department of Systems and Operations Management
Responsible Changed From-To: freebsd-ports->knu Over to maintainer
At Wed, 27 Mar 2002 20:13:31 -0800, Albert Kinderman wrote: > I ran portsclean -L (in non-interactive mode). portsclean still > asked me a question and stopped and waited for input from me. > > overwrite /usr/local/lib/compat/pkg/libfreetype.so.6? (y/n [n]) > > My guess is that running portsclean -L from within portupgrade > does not print the question to the console, so it is waiting for a > user response which never comes. This appears as a hang in > portupgrade. My response of control-C stopped portsclean and > allowed portupgrade to continue. Thanks for the report. I've just released 20020328 which should fix the problem. Fortunately, it is 100% safe to abort at the `Cleaning out obsolete shared libraries' because it is done at the very end of the upgrading procedure. Regards, -- / /__ __ Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "Somewhere out of a memory.. of lighted streets on quiet nights.."
State Changed From-To: open->closed Should be fixed in 20020328. Thanks for the report.