severity 475529 important thanks > (There *are* patches to pull.)
Indeed. Isaac, what about upgrading the package to 2.0 (or orphaning/RFAing it in case you don't have the time to work on it?) This bug only affects sparc, so I'm lowering the severity. It seems ssh is started, but the weird thing is that the password prompt from ssh is printed after darcs is gone already, and ssh is dead due to that of course. I could imagine that this 0 (sid)[EMAIL PROTECTED]:~$ darcs get [EMAIL PROTECTED]:/tmp/foo 127 (sid)[EMAIL PROTECTED]:~$ [EMAIL PROTECTED]'s password: [EMAIL PROTECTED]'s password: [EMAIL PROTECTED]'s password: (the 127 is the exit code from darcs). Even more weird, if I strace darcs, it doesn't even try to start ssh, but instead tries to access a file called [EMAIL PROTECTED]:/tmp/foo. I didn't have a close look in that, though. Rebuilding the package doesn't make things better... -- Bernd Zeimetz Debian GNU/Linux Developer GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
