shipitjs/shipit

mv: illegal option -- T

Open

#173 opened on Jan 24, 2018

View on GitHub
 (7 comments) (1 reaction) (0 assignees)JavaScript (5,331 stars) (194 forks)batch import
buggood first issuehelp wanted

Description

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

Contributor guide

Tech stack
shellnodejs
Domain
devopscli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
shell scripting basicscross platform compatibility awareness
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
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.