This is just a change introduced to make debugging of ssh problems easier: we now show the stderr of scp, which has this not-so-great side-effect, which shows up when we check whether certain files exist remotely.
On Thu, Aug 7, 2008 at 3:33 AM, Barak A. Pearlmutter <[EMAIL PROTECTED]> wrote: > Package: darcs > Version: 2.0.2-2 > > Just upgraded, from v2.0.0, which did not exhibit this behaviour. > > Repo is v1 on both ends. > > [corti] ~/src/darcs/Grants/GPU-AD $ darcs -v > 2.0.2 (release) > > [corti] ~/src/darcs/Grants/GPU-AD $ darcs pull > scp: darcs/Grants/GPU-AD/_darcs/format: No such file or directory > scp: darcs/Grants/GPU-AD/_darcs/prefs/sources: No such file or directory > Pulling from "golconda:darcs/Grants/GPU-AD"... > No remote changes to pull in! > > [corti] ~/src/darcs/Grants/GPU-AD $ darcs push > scp: darcs/Grants/GPU-AD/_darcs/format: No such file or directory > scp: darcs/Grants/GPU-AD/_darcs/prefs/sources: No such file or directory > Pushing to "golconda:darcs/Grants/GPU-AD"... > No recorded local changes to push! > > Seemed to pushing a change fine earlier, so maybe this is just an > inconsequential warning. Yet for some reason I find it disquieting. > > --Barak. > -- > Barak A. Pearlmutter > Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland > http://www.bcl.hamilton.ie/~barak/ > > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
