Control: severity -1 important
Reinhard Tartler writes ("Bug#848512: Probably cause: Dangling symlink in
upstream tarball"):
> I think I've found the issue: the upstream tarball contains a symlink
> to an non-existing target:
I think you have identified the cause.
> While I agree that this is not an ideal situation, I'd argue that dgit
> should handle this situation gracefully, which in this case means
> importing a dangling symlink.
Indeed, you are entirely right.
> Or, if that's difficult, at least not fail
> while importing.
No, it should import it correctly :-).
Workarounds:
* Using dgit fetch (which can be done in a tree you've just done `git
init' in) will avoid this step entirely.
* Use patch to edit /usr/bin/dgit with the diff below.
If you apply the patch please let me know if it fixes it.
Thanks,
Ian.
diff --git a/dgit b/dgit
index 983f97c..fbf0f22 100755
--- a/dgit
+++ b/dgit
@@ -3261,7 +3261,7 @@ sub clone_finish ($) {
runcmd qw(bash -ec), <<'END';
set -o pipefail
git ls-tree -r --name-only -z HEAD | \
- xargs -0r touch -r . --
+ xargs -0r touch -h -r . --
END
printdone "ready for work in $dstdir";
}
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
