This appears fixed for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680138
Title:
fails with Invalid cross-device link if cwd is not same filesystem as $HOME
--
ubuntu-bugs mailing list
So, it looks like it is fixed, but I don't think that its a good idea to
change the cwd in the testdrive.py . Changing of current working
directory is an unexpected side effect of calling 'get_proto' that might
break other things.
I would suggest only changing the working directory in the
This bug was fixed in the package testdrive - 3.3-0ubuntu1
---
testdrive (3.3-0ubuntu1) natty; urgency=low
* Fix zsync failure if cwd is not same filesystem as $HOME (LP: #680138)
- Thanks to Scott Moser for providing a better patch.
-- Andres Rodriguez andres...@ubuntu.com
** Branch linked: lp:testdrive
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680138
Title:
fails with Invalid cross-device link if cwd is not same filesystem as $HOME
--
ubuntu-bugs mailing list
Hi Scott,
Sorry for the delay. Could you please test this to see if it is fixed,
with the following patch?
http://bazaar.launchpad.net/~testdrive/testdrive/trunk/revision/308
Thank you!
** Changed in: testdrive (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug
Note, the subject of the bug says:
if cwd is not same filesystem as home
I can reproduce this on a lucid server I have access to , so I suspect
its also a bug on maverick.
the bug is actually in zsync, which is (i think) trying to create a
hardlink.
$ df / /home
Filesystem
Hi Scott,
I've tested this in Maverick and can't reproduce this bug. I see that
you already running natty, so that might be the reason why this is
failing. Unfortunately, I don't have anything running natty just yet.
I'll take a look at it again whenever I upgrade to natty, which should
be in the
