RE: autoconf failure
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chad Perrin Sent: 04 October 2007 00:35 To: FreeBSD Questions Subject: autoconf failure First, portversion reports as follows: # portversion -v|grep -v = autoconf-2.53_4 needs updating (port has 2.61_2) autoconf-2.59_3 needs updating (port has 2.61_2) Then, /usr/ports/UPDATING fails to note anything about the new autoconf version other than the following: The ports tree has been migrated to the latest version of autoconf, 2.61. Versions 2.53 and 2.59 were declared obsolete and removed. Finally, using portupgrade to try to update my autoconf version yields the following results: === autoconf-2.61_2 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/autoconf261 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/devel/autoconf261. *** Error code 1 Stop in /usr/ports/devel/autoconf261. ** Command failed [exit code 1]: /usr/bin/script -qa \ /tmp/portupgrade.31535.1 env UPGRADE_TOOL=portupgrade \ UPGRADE_PORT=autoconf-2.53_4 UPGRADE_PORT_VER=2.53_4 make reinstall --- Restoring the old version I also get this: ** Port marked as IGNORE: x11-servers/xorg-server-snap: is outdated I'm not entirely sure what that's about. I imagine it wouldn't be safe to `make deinstall` all things autoconf, then try to `make install` autoconf. Am I wrong about that? Is there some other way to fix this? Have I overlooked something obvious? Chad, Had the same thought's here - don't know for certain that it's the right thing to do, but I did: cd /usr/ports/devel/autoconf261 make deinstall make reinstall This seemed to remove the older versions of autoconf. Following that a portupgrade -av built the few other ports that had been skipped previously. Cheers, Barry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: autoconf failure
On Friday 05 October 2007 11:19:55 Barry Byrne wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chad Perrin Sent: 04 October 2007 00:35 To: FreeBSD Questions Subject: autoconf failure First, portversion reports as follows: # portversion -v|grep -v = autoconf-2.53_4 needs updating (port has 2.61_2) autoconf-2.59_3 needs updating (port has 2.61_2) Then, /usr/ports/UPDATING fails to note anything about the new autoconf version other than the following: The ports tree has been migrated to the latest version of autoconf, 2.61. Versions 2.53 and 2.59 were declared obsolete and removed. Had the same thought's here - don't know for certain that it's the right thing to do, but I did: cd /usr/ports/devel/autoconf261 make deinstall make reinstall It's simpler then that: pkg_delete -f autoconf-2.5[39]* -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: autoconf failure
On Fri, Oct 05, 2007 at 12:10:12PM +0200, Mel wrote: It's simpler then that: pkg_delete -f autoconf-2.5[39]* I came to the same conclusion before seeing this email, but figured I'd see if anyone had said something about it. pkg_cutleaves seemed to indicate it was a leave package with no dependencies, and autoconf --version indicates that the currently installed/used version is 2.6.1, which of course would mean that the old version is just wedged on uninstall. . . . so thanks for confirming what I've surmised. I'll feel a lot better about removing it now. -- CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ] John Kenneth Galbraith: If all else fails, immortality can always be assured through spectacular error. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
autoconf failure
First, portversion reports as follows: # portversion -v|grep -v = autoconf-2.53_4 needs updating (port has 2.61_2) autoconf-2.59_3 needs updating (port has 2.61_2) Then, /usr/ports/UPDATING fails to note anything about the new autoconf version other than the following: The ports tree has been migrated to the latest version of autoconf, 2.61. Versions 2.53 and 2.59 were declared obsolete and removed. Finally, using portupgrade to try to update my autoconf version yields the following results: === autoconf-2.61_2 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/autoconf261 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/devel/autoconf261. *** Error code 1 Stop in /usr/ports/devel/autoconf261. ** Command failed [exit code 1]: /usr/bin/script -qa \ /tmp/portupgrade.31535.1 env UPGRADE_TOOL=portupgrade \ UPGRADE_PORT=autoconf-2.53_4 UPGRADE_PORT_VER=2.53_4 make reinstall --- Restoring the old version I also get this: ** Port marked as IGNORE: x11-servers/xorg-server-snap: is outdated I'm not entirely sure what that's about. I imagine it wouldn't be safe to `make deinstall` all things autoconf, then try to `make install` autoconf. Am I wrong about that? Is there some other way to fix this? Have I overlooked something obvious? -- CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ] Larry Wall: A script is what you give the actors. A program is what you give the audience. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
