shipitjs/shipit

mv: illegal option -- T

Open

#173 建立於 2018年1月24日

在 GitHub 查看
 (7 留言) (1 反應) (0 負責人)JavaScript (5,331 star) (194 fork)batch import
buggood first issuehelp wanted

描述

An error is produced on FreeBSD. It seems that FreeBSD does not have -T option for mv command. This option was introduced with shipit-deploy 2.5.0

'deploy:publish' errored after 553 ms
Error: Command failed: ssh user@server "cd /usr/home/…/nodejs && if [[ -d current && ! (-L current) ]]; then echo \"ERR: could not make symlink\"; else ln -nfs releases/20171204175536 current_tmp && mv -fT current_tmp current; fi"
mv: illegal option -- T
usage: mv [-f | -i | -n] [-hv] source target
       mv [-f | -i | -n] [-v] source ... directory

貢獻者指南

技術棧
shellnodejs
領域
devopscli
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
shell scripting basicscross platform compatibility awareness
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
The issue is from shipitjs/shipit, but the actual error comes from shipit deploy where the `mv fT` command is used. The fix requires replacing the ` T` flag with a portable alternative that works on FreeBSD. For example, use `ln nfs current tmp current && rm rf current tmp` or similar. The relevant code is likely in shipit deploy's publish task. Check the linked PR #122 for context. Test the change on a FreeBSD system or CI.