"cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead" while running update.sh

[Fvbor]

Contribution guidelines

• I've read the contribution guidelines and wholeheartedly agree

I've found a bug and checked that ...

• ... I understand that not following the below instructions will result in immediate closure and/or deletion of my issue.
• ... I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
• ... I have understood that answers are voluntary and community-driven, and not commercial support.
• ... I have verified that my issue has not been already answered in the past. I also checked previous issues.

Description

While Updating my Mailcow to 2025-01 I got a warning in the logs.

cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead

I guess it should be this line -> https://github.com/mailcow/mailcow-dockerized/blob/244d4b8c4c3973c4c5a88b269aff1a230c160468/update.sh#L1447

Sadly I found after a short googling no good source to this. Only threads in forums and mailinglists with discussions about this.

mailcow-dockerized/update.sh

Line 1447 in 244d4b8

cp -n -d data/assets/ssl-example/*.pem data/assets/ssl/

Logs:

update.sh log around this warning

Fetching new images, if any...
[+] Pulling 18/18
 ✔ mysql-mailcow Pulled1.1s
 ✔ ipv6nat-mailcow Pulled1.1s
 ✔ postfix-mailcow Pulled1.2s
 ✔ rspamd-mailcow Pulled1.1s
 ✔ sogo-mailcow Pulled1.2s
 ✔ php-fpm-mailcow Pulled1.1s
 ✔ unbound-mailcow Pulled1.2s
 ✔ ofelia-mailcow Pulled1.2s
 ✔ dockerapi-mailcow Pulled1.1s
 ✔ memcached-mailcow Pulled1.1s
 ✔ acme-mailcow Pulled1.2s
 ✔ netfilter-mailcow Pulled1.1s
 ✔ watchdog-mailcow Pulled1.1s
 ✔ nginx-mailcow Pulled1.1s
 ✔ redis-mailcow Pulled1.2s
 ✔ clamd-mailcow Pulled1.2s
 ✔ olefy-mailcow Pulled1.1s
 ✔ dovecot-mailcow Pulled1.0s
cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead
Checking IPv6 settings...
Starting mailcow...
[+] Running 19/19
 ✔ Network mailcowdockerized_mailcow-network        Created0.2s
 ✔ Container mailcowdockerized-memcached-mailcow-1  Started2.9s
 ✔ Container mailcowdockerized-netfilter-mailcow-1  Started1.3s
 ✔ Container mailcowdockerized-dockerapi-mailcow-1  Started3.0s
 ✔ Container mailcowdockerized-olefy-mailcow-1      Started2.9s
 ✔ Container mailcowdockerized-sogo-mailcow-1       Started3.1s
 ✔ Container mailcowdockerized-unbound-mailcow-1    Healthy36.0s
 ✔ Container mailcowdockerized-clamd-mailcow-1      Started34.1s
 ✔ Container mailcowdockerized-redis-mailcow-1      Started3.0s
 ✔ Container mailcowdockerized-mysql-mailcow-1      Started4.5s
 ✔ Container mailcowdockerized-php-fpm-mailcow-1    Started4.7s
 ✔ Container mailcowdockerized-dovecot-mailcow-1    Started6.1s
 ✔ Container mailcowdockerized-postfix-mailcow-1    Started34.2s
 ✔ Container mailcowdockerized-ofelia-mailcow-1     Started6.9s
 ✔ Container mailcowdockerized-rspamd-mailcow-1     Started34.4s
 ✔ Container mailcowdockerized-nginx-mailcow-1      Started35.2s
 ✔ Container mailcowdockerized-acme-mailcow-1       Started36.2s
 ✔ Container mailcowdockerized-watchdog-mailcow-1   Started37.2s
 ✔ Container mailcowdockerized-ipv6nat-mailcow-1    Started37.4s
Collecting garbage...

Steps to reproduce:

Run update.sh

Which branch are you using?

master

Which architecture are you using?

x86

Operating System:

Ubuntu 24.04.1

Server/VM specifications:

2

Is Apparmor, SELinux or similar active?

no

Virtualization technology:

KVM

Docker version:

27.4.1

docker-compose version or docker compose version:

v2.32.1

mailcow version:

2025-01

Reverse proxy:

No

Logs of git diff:

No

Logs of iptables -L -vn:

Not requiered

Logs of ip6tables -L -vn:

Not requiered

Logs of iptables -L -vn -t nat:

Not requiered

Logs of ip6tables -L -vn -t nat:

Not requiered

DNS check:

Not requiered

[Habetdin]

Related to #6197