diff options
author | Peter Melnichenko <mpeterval@gmail.com> | 2016-10-12 19:37:46 +0300 |
---|---|---|
committer | Peter Melnichenko <mpeterval@gmail.com> | 2016-10-12 19:48:11 +0300 |
commit | 8ce99cc3d2d12eb0b0e4808e5dd1fc402b8603d4 (patch) | |
tree | d8ba60e8ec896c3506fdb44e9670d820b9cbfc24 /spec | |
parent | d0edbc1873ca9165d968752a67fabc4f580856df (diff) | |
download | luarocks-8ce99cc3d2d12eb0b0e4808e5dd1fc402b8603d4.tar.gz luarocks-8ce99cc3d2d12eb0b0e4808e5dd1fc402b8603d4.tar.bz2 luarocks-8ce99cc3d2d12eb0b0e4808e5dd1fc402b8603d4.zip |
Fix manif.find_{current,next}_provider returning "untracked" incorrectly
`find_providers` function used by `manif.find_current_provider`
and `manif.find_next_provider` needs relative path from a directory
an installed file is deployed in (bin dir, lua dir, or lib dir) to the file.
It then uses that path as key in manifest, converting it to
module name beforehand for lua files and lib files.
It happened to leave a leading slash in this relative path for
lua and lib files. `path.path_to_module` has a workaround stripping
leading dots caused by leading slashes. However, if the file
doesn't have `.lua` extension, slashes are not converted to dots
and the workaround doesn't trigger.
The issue results in files falsely considered "untracked" and backed-up
when reinstalling a different version of a rock,
see sailorproject/sailor#138.
The fix is to use correct relative paths without leading slashes.
Diffstat (limited to 'spec')
0 files changed, 0 insertions, 0 deletions