This is something I've never done before. How do I do an strace on the process?Redeeman wrote:could you try attach strace to the process?


Code: Select all
athas local # svn co http://kaspersandberg.com/fluidportage
svn: REPORT request failed on '/fluidportage/!svn/vcc/default'
svn: REPORT of '/fluidportage/!svn/vcc/default': 400 Bad Request (http://kaspersandberg.com)
First make sure you have strace (emerge strace if there is no such command). Running "strace emerge hal-cvs" might be a bit too much, so first just run "emerge hal-cvs" and if it starts "stalling" just ctrl-c or kill it somehow. Then "cd /var/tmp/portage/hal-cvs-<version>/work/hal/doc/spec" and run "make", if it again starts stalling kill it again and then try "strace make", this should stop at some point (start stalling again, but you should see a _very long_ output of what the program was doing and hopefully some of it reveals why the program is stalling (if you can't figure it out yourself post the end (a few "pages") of the output here).gungholady wrote:This is something I've never done before. How do I do an strace on the process?Redeeman wrote:could you try attach strace to the process?
Works just fine here, the server was probably down for a small (?) while.BNoise wrote:why is that?Code: Select all
athas local # svn co http://kaspersandberg.com/fluidportage svn: REPORT request failed on '/fluidportage/!svn/vcc/default' svn: REPORT of '/fluidportage/!svn/vcc/default': 400 Bad Request (http://kaspersandberg.com)

I'm trying something else first. I got to looking at the hal-cvs ebuild and there were dependencies for gnome. I had -gnome in my cflags. I'm trying USE="gnome" emerge hal-cvs. It finished all the gnome dependencies but at the moment it can't access the url to get hal-cvs. I'll have to wait a little bit and try it again. Then if that doesn't solve the problem, I'll try the strace. I already emerged strace just iin case I need it.sn4ip3r wrote:First make sure you have strace (emerge strace if there is no such command). Running "strace emerge hal-cvs" might be a bit too much, so first just run "emerge hal-cvs" and if it starts "stalling" just ctrl-c or kill it somehow. Then "cd /var/tmp/portage/hal-cvs-<version>/work/hal/doc/spec" and run "make", if it again starts stalling kill it again and then try "strace make", this should stop at some point (start stalling again, but you should see a _very long_ output of what the program was doing and hopefully some of it reveals why the program is stalling (if you can't figure it out yourself post the end (a few "pages") of the output here).gungholady wrote:This is something I've never done before. How do I do an strace on the process?Redeeman wrote:could you try attach strace to the process?



The next update of fluidcvs will have docbook/doxygen docs disabled. The strange thing is that I have no problem with the current ebuild.gungholady wrote:An email from the hal mailing list says it needs to have doxygen and doc disabled which is done by the ebuild for hal-0.2.97. That is why it works. The email said to bug my distribution about this.
Code: Select all
svn: REPORT request failed on '/fluidportage/!svn/vcc/default'
svn: REPORT of '/fluidportage/!svn/vcc/default': 400 Bad Request (http://kaspersandberg.com)
Code: Select all
# ls trunk
ls: trunk: No such file or directory

Code: Select all
svn co http://redeeman.kaspersandberg.com/fluidportage/trunk/
svn: REPORT request failed on '/fluidportage/!svn/vcc/default'
svn: REPORT of '/fluidportage/!svn/vcc/default': Could not read status line: Connection reset by peer (http://redeeman.kaspersandberg.com)