fly execute doesn't like hard links

[robdimsdale]

when forgetting to use -x fly tries to tar up the entire git repo which prints confusing output:

 2015-09-25 11:41:27 ☆ ruby 2.2.2p95 (system) clementina in ~/workspace/concourse
± |develop ✓| → fly e -c ./ci/baggageclaim.yml
executing build 7
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 95.6M    0 95.6M    0     0  3963k      0 --:--:--  0:00:24 --:--:-- 4445ktar: can't create hardlink from ./.git/modules/src/github.com/concourse/gate/objects/pack/pack-5e7625078c21d7505391d37335d947c6a7b7c912.idx to ././@LongHardLink: No such file or directory
tar: can't create hardlink from ./.git/modules/src/github.com/concourse/gate/objects/pack/pack-5e7625078c21d7505391d37335d947c6a7b7c912.pack to ././@LongHardLink: No such file or directory
100 1752M    0 1752M    0     0  14.9M      0 --:--:--  0:01:57 --:--:-- 16.5M
initializing with docker:///concourse/baggageclaim-ci

[concourse-bot]

Hi there!

We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.

The current status is as follows:

• #104201868 fly execute doesn't like hard links

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

[vito]

This looks like a quirk of OS X <-> Linux tar interaction or something similarly cryptic. I'm finding it hard to care until it becomes an actual issue (it looks like it kept going, from your snippet). There are similar problems you'll find on Windows with path names being too long (which node_modules quickly reveals); there's not a whole lot we can do about it.

If it keeps happening all the time and starts impeding your progress, feel free to reopen.