hostname: unrecognized option: fqdn

[bantu]

Hello.

I am seeing this in my log output:

Fri Jan 17 17:12:19 UTC 2025: No changed files, but different commit ID. Changed files ignored or commit amended.
Fri Jan 17 17:12:19 UTC 2025: No files to sync. All changed files ignored.
hostname: unrecognized option: fqdn
BusyBox v1.36.1 (2024-06-10 07:11:47 UTC) multi-call binary.
Usage: hostname [-sidf] [HOSTNAME | -F FILE]
Show or set hostname or DNS domain name
	-s	Short
	-i	Addresses for the hostname
	-d	DNS domain name
	-f	Fully qualified domain name
	-F FILE	Use FILE's content as hostname
Fri Jan 17 17:12:19 UTC 2025: Remote locking @ on Fri, 17 Jan 2025 17:12:19 +0000.

I suppose this is because I passed the --lock option and this causes git-ftp to call hostname --fqdn.

[nebuIr]

Hi,

yes, that's because of the --lock option: https://github.com/git-ftp/git-ftp/blob/master/git-ftp#L603

Our Docker image uses Alpine Linux which uses BusyBox for it's hostname implementation. But it seems that implementation doesn't support the --fqdn option, only the -f option is supported for FQDN.

But as far as I can tell, remote locking should still work.