configure-instance: ignore mtime when copying into chroot

The rework of copying files into the chroot changed the semantics, by using cp -u. Before the files were copied in all cases, now it's guarded by a check on the sources mtime. In some cases this leads to a file not being copied despite having changed. Two cases which I've seen:

  • /var/spool/postfix/etc/services having a mtime of some minutes ago, while /etc/services has one of 4 months ago (when it was last packaged I assume (2025-03-15 23:55:22))
  • postfix check running directly before /etc/localtime is changed (ctime/mtime of both files is the same)

This results in warnings about the files differing, which would not happen before. Additionally having the same contents in the chrooted files should cause far fewer surprises, while the cost in terms of I/O should not be to high.

Fixes: ca823921 ("d/configure-instance.sh: optimize file copying") Signed-off-by: Stoiko Ivanov s.ivanov@proxmox.com

Merge request reports

Loading