© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I suspect that we're now seeing some of these in the error tracker:
https:/
What's very odd is that neither the server or client has changed in months. What I don't know is whether some configuration on the server could be affecting this. Why si client should be more robust in the face of dangling symlinks, the server should very definitely not be generating tarballs with such dangling symlinks.