sample case: retrace failed to retrace properly

[yarikoptic]

trafficstars

@yarikoptic (me) experienced this on v0.0.5-142-g88e5aca which is the one (#220)

niceman retrace ~/anaconda-4.4.0-3.6/envs/datalad/bin/datalad ~/deb/gits/fail2ban/setup.py /usr/bin/fail2ban ~datalad/datalad/venvs/dev/bin/datalad e41aa8f26a77ec2dacd1bbc2afa08f0cf92a4407cacac92fb888e0723a867446 52fe1e86d334

so docker image , debian fail2ban failed to be traced

[yarikoptic]

my bad with /usr/bin/fail2ban -- indeed there is no such thing

docker image managed to get assigned to a git repository:

- name: git
  packages:
  - path: /home/yoh/proj/repronim/niceman-master
    files:
    - 52fe1e86d334
    branch: master
    hexsha: 717ad47612156b9fc8a20b3af788d4b9147c3cb3
    describe: v0.0.5-165-g717ad47
    tracked_remote: origin
    remotes:
      gh-chaselgrove:
        url: git://github.com/chaselgrove/niceman
      gh-kyleam:
        url: https://github.com/kyleam/niceman
      gh-mjtravers:
        url: https://github.com/mjtravers/ReproNim
      gh-rbuccigrossi:
        url: git://github.com/rbuccigrossi/ReproNim
      gh-yarikoptic:
        url: [email protected]:yarikoptic/ReproNim
      origin:
        contains: true
        url: [email protected]:ReproNim/niceman

[kyleam]

Odd. Do you see that with every docker image you retrace? I've tried a few images, from within and outside a git repo, and can't convince retrace to assign it to a git repo.