fix: relative paths to dirs

[caarlos0]

closes #575

[codecov]

Codecov Report

Merging #576 (119958f) into main (5c3cc38) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #576      +/-   ##
==========================================
+ Coverage   70.22%   70.25%   +0.02%     
==========================================
  Files          21       21              
  Lines        3130     3133       +3     
==========================================
+ Hits         2198     2201       +3     
  Misses        715      715              
  Partials      217      217              

Impacted Files	Coverage Δ
internal/glob/glob.go	84.37% <100.00%> (+0.76%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[djgilcrease]

LGTM

[drakkan]

Hi,

this change broke my use case.

Please take a look here.
I now have this error:

cannot add "/home/nicola/goprojects/sftpgo/templates/webclient/twofactor.html" because "/home/nicola/goprojects/sftpgo/templates/webadmin/twofactor.html" is already present at the same destination (/usr/share/sftpgo/templates/twofactor.html): content collision

I have some files with the same name in templates/webclient and templates/webadmin. Can I fix this by changing my glob syntax? (I've tried some alternate globs with no luck). Thanks

EDIT: If I change

- src: "${BASE_DIR}/templates/*"
  dst: "/usr/share/sftpgo/templates/"

to

- src: "${BASE_DIR}/templates/*"
   dst: "/usr/share/sftpgo/templates"

it works as before. No problem if this is the intended behaviour

[caarlos0]

@drakkan yes, unfortunately this might be a breaking change for some... but I still think it was a bug before... I'll add a note about it in the release notes though.

[caarlos0]

https://github.com/goreleaser/nfpm/releases/tag/v2.22.1

[drakkan]

@drakkan yes, unfortunately this might be a breaking change for some... but I still think it was a bug before... I'll add a note about it in the release notes though.

no problem, thanks