Re: Problems with cvsup on FreeBSD 9, AMD64, osreldate: 900038
On 07/03/2011 03:51 PM, Stephen Montgomery-Smith wrote: On 07/02/2011 10:25 PM, jhell wrote: Use csup(1) in base. This is in 7, 8 9. cvsup has been deprecated for much longer than it really needed to be and should probably be removed from use as a client entirely and links generated for installation of cvsup - csup. Only drawback for you may be no X interface but it really was not that pretty in the first place and served no real good purpose over the functionality of the command line client. Another drawback to csup is that csup doesn't seem to recognize the .cvsup/auth file. At least not on FreeBSD 7 of a few months ago. I run CTM generation, and I need access to cvsup-master. My mistake. I found that in FreeBSD-CURRENT that csup does recognize .csup/auth. Any timetable on when this will by MFCed to FreeBSD 7 and 8? Incidentally, csup needs the following diff applied, so that I can continue to use FreeBSD in my auth file: 195c195 if (strcmp(auth-server, server) != 0) --- if (strcasecmp(auth-server, server) != 0) I'll file a PR. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Problems with cvsup on FreeBSD 9, AMD64, osreldate: 900038
On 02/07/2011 17:07, Garrett Cooper wrote: On Sat, Jul 2, 2011 at 8:33 AM, Vassilis Laganakos vassilis.lagana...@yahoo.com wrote: Hello, I am facing the same problems as Holger here: http://lists.freebsd.org/pipermail/freebsd-current/2011-June/025205.html although CVSup dies in gmtime_r in libc.so.7: ... Updating collection src-all/cvs Edit src/UPDATING Program received signal SIGSEGV, Segmentation fault. 0x2ca10fb9 in gmtime_r () from /lib/libc.so.7 ... See full gdb backtrace at: http://www.pastie.org/pastes/2154271 So I'm now stuck in osrel 900038... I guess I need to rebuild libc.so.7 with debugging symbols to find out what is going wrong there. Any quick ideas on how to correct this, or if someone else is seeing this issue? Have you tried recompiling cvsup and all of its dependencies? Yeah, I rebuilt every port installed with pormaster -dBfa, hoping that that would correct it, but that gave the same behaviour. Thanks, Vassilis L. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Problems with cvsup on FreeBSD 9, AMD64, osreldate: 900038
On 02/07/2011 17:54, Kurt Jaeger wrote: Hi! Any quick ideas on how to correct this, or if someone else is seeing this issue? Does csup work ? Yeah! That works! I see that csups is part of the build system. So is this to replace the cvsup port? Thanks, Vassilis L. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Problems with cvsup on FreeBSD 9, AMD64, osreldate: 900038
On 03/07/2011 04:25, jhell wrote: On Sat, Jul 02, 2011 at 04:33:39PM +0100, Vassilis Laganakos wrote: Hello, I am facing the same problems as Holger here: http://lists.freebsd.org/pipermail/freebsd-current/2011-June/025205.html although CVSup dies in gmtime_r in libc.so.7: ... Updating collection src-all/cvs Edit src/UPDATING Program received signal SIGSEGV, Segmentation fault. 0x2ca10fb9 in gmtime_r () from /lib/libc.so.7 ... See full gdb backtrace at: http://www.pastie.org/pastes/2154271 So I'm now stuck in osrel 900038... I guess I need to rebuild libc.so.7 with debugging symbols to find out what is going wrong there. Any quick ideas on how to correct this, or if someone else is seeing this issue? Use csup(1) in base. This is in 7, 8 9. cvsup has been deprecated for much longer than it really needed to be and should probably be removed from use as a client entirely and links generated for installation of cvsup - csup. Oh, I wasn't aware of that. csup worked sweet, thanks! So I'll remove the cvsup port and switch to using csup. Only drawback for you may be no X interface but it really was not that pretty in the first place and served no real good purpose over the functionality of the command line client. An alternative if you need and X interface is creating a icon on your desktop that runs ( xterm -e csup /path/to/supfile ) or something similiar. Ok. I haven't been using the X interface, and I agree it hasn't been that great. Thanks for the information! Vassilis L. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Problems with cvsup on FreeBSD 9, AMD64, osreldate: 900038
On 07/02/2011 10:25 PM, jhell wrote: Use csup(1) in base. This is in 7, 8 9. cvsup has been deprecated for much longer than it really needed to be and should probably be removed from use as a client entirely and links generated for installation of cvsup - csup. Only drawback for you may be no X interface but it really was not that pretty in the first place and served no real good purpose over the functionality of the command line client. Another drawback to csup is that csup doesn't seem to recognize the .cvsup/auth file. At least not on FreeBSD 7 of a few months ago. I run CTM generation, and I need access to cvsup-master. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Problems with cvsup on FreeBSD 9, AMD64, osreldate: 900038
Hello, I am facing the same problems as Holger here: http://lists.freebsd.org/pipermail/freebsd-current/2011-June/025205.html although CVSup dies in gmtime_r in libc.so.7: ... Updating collection src-all/cvs Edit src/UPDATING Program received signal SIGSEGV, Segmentation fault. 0x2ca10fb9 in gmtime_r () from /lib/libc.so.7 ... See full gdb backtrace at: http://www.pastie.org/pastes/2154271 So I'm now stuck in osrel 900038... I guess I need to rebuild libc.so.7 with debugging symbols to find out what is going wrong there. Any quick ideas on how to correct this, or if someone else is seeing this issue? Thanks, Vassilis L. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
