Re: upgrade of portupgrade fails
On 16/12/06 Michael P. Soulier said: Stop in /usr/ports/lang/ruby18. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade12405.0 make PORT_UPGRADE=yes reinstall egrep: /var/db/pkg/ruby-1.8.4_9,1/+CONTENTS: No such file or directory --- Restoring the old version Any ideas why? So, the logs tell me why. swap_pager_getswapspace(9): failed swap_pager_getswapspace(9): failed swap_pager_getswapspace(2): failed swap_pager_getswapspace(3): failed swap_pager_getswapspace(2): failed swap_pager_getswapspace(2): failed pid 24321 (ruby18), uid 0, was killed: out of swap space I guess ruby used too much memory for my system. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgpxEO55HHPWE.pgp Description: PGP signature
Re: upgrade of portupgrade fails
Michael P. Soulier wrote: [ ... ] So, the logs tell me why. swap_pager_getswapspace(9): failed swap_pager_getswapspace(9): failed swap_pager_getswapspace(2): failed swap_pager_getswapspace(3): failed swap_pager_getswapspace(2): failed swap_pager_getswapspace(2): failed pid 24321 (ruby18), uid 0, was killed: out of swap space I guess ruby used too much memory for my system. Yes, for some reason generating the Ruby documentation takes a great deal of RAM, and may run very slowly on machines without enough of it. There is probably an option in the ports' Makefile to disable building the docs; check pkg-mesg...? You might also consider adding more RAM to the system in question; it will help performance for other tasks. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrade of portupgrade fails
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chuck Swiger wrote: Michael P. Soulier wrote: [ ... ] So, the logs tell me why. swap_pager_getswapspace(9): failed swap_pager_getswapspace(9): failed swap_pager_getswapspace(2): failed swap_pager_getswapspace(3): failed swap_pager_getswapspace(2): failed swap_pager_getswapspace(2): failed pid 24321 (ruby18), uid 0, was killed: out of swap space I guess ruby used too much memory for my system. Yes, for some reason generating the Ruby documentation takes a great deal of RAM, and may run very slowly on machines without enough of it. There is probably an option in the ports' Makefile to disable building the docs; check pkg-mesg...? You might also consider adding more RAM to the system in question; it will help performance for other tasks. cd /usr/ports/lang/ruby18/ make config ;) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFhZG1EnKyINQw/HARAgyBAJ9GsOl3MwVcyXG3sUP79yMWe/0wwgCffRIq Ab0yV8XihGVTdSvs68CAeqE= =8nvF -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
upgrade of portupgrade fails
I did a portupgrade -R on sysutils/portupgrade, and it started upgrading ruby. Unfortunately, it failed. No definition for sock_s_unpack_sockaddr_un stringio.c: c. strscan.c: cc. zlib.c: mcc... Generating RI... Killed *** Error code 137 Stop in /usr/ports/lang/ruby18/work/ruby-1.8.5. *** Error code 1 Stop in /usr/ports/lang/ruby18. *** Error code 1 Stop in /usr/ports/lang/ruby18. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade12405.0 make PORT_UPGRADE=yes reinstall egrep: /var/db/pkg/ruby-1.8.4_9,1/+CONTENTS: No such file or directory --- Restoring the old version Any ideas why? Thanks, Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgpslScfnxpX3.pgp Description: PGP signature
Re: upgrade of portupgrade fails
On Saturday 16 December 2006 20:24, Michael P. Soulier wrote: I did a portupgrade -R on sysutils/portupgrade, and it started upgrading ruby. Unfortunately, it failed. No definition for sock_s_unpack_sockaddr_un stringio.c: c. strscan.c: cc. zlib.c: mcc ... Generating RI... Killed *** Error code 137 Stop in /usr/ports/lang/ruby18/work/ruby-1.8.5. *** Error code 1 Stop in /usr/ports/lang/ruby18. *** Error code 1 Stop in /usr/ports/lang/ruby18. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade12405.0 make PORT_UPGRADE=yes reinstall egrep: /var/db/pkg/ruby-1.8.4_9,1/+CONTENTS: No such file or directory --- Restoring the old version Any ideas why? Thanks, Mike I had this problem as well after going from 6.1 to -CURRENT I fixed it by doing cd /usr/ports/lang/ruby18 make -DFORCE_PKG_REGISTER install and then rebuilt sysutils/portupgrade lane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrade of portupgrade fails
On Saturday 16 December 2006 20:24, Michael P. Soulier wrote: I did a portupgrade -R on sysutils/portupgrade, and it started upgrading ruby. Unfortunately, it failed. No definition for sock_s_unpack_sockaddr_un stringio.c: c. strscan.c: cc. zlib.c: mcc ... Generating RI... Killed *** Error code 137 Stop in /usr/ports/lang/ruby18/work/ruby-1.8.5. *** Error code 1 Stop in /usr/ports/lang/ruby18. *** Error code 1 Stop in /usr/ports/lang/ruby18. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade12405.0 make PORT_UPGRADE=yes reinstall egrep: /var/db/pkg/ruby-1.8.4_9,1/+CONTENTS: No such file or directory --- Restoring the old version Any ideas why? Thanks, Mike I had this problem as well after going from 6.1 to -CURRENT I fixed it by doing cd /usr/ports/lang/ruby18 make -DFORCE_PKG_REGISTER install and then rebuilt sysutils/portupgrade lane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrade of portupgrade fails
On 16/12/06 Lane said: I had this problem as well after going from 6.1 to -CURRENT I fixed it by doing cd /usr/ports/lang/ruby18 make -DFORCE_PKG_REGISTER install and then rebuilt sysutils/portupgrade Well, it seemed to be a problem in building the ruby rdocs, so I removed that option for now. I upgraded portupgrade on its own, and then upgraded ruby, and that seems to have worked. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgpQMapgaKZAz.pgp Description: PGP signature
