What were you trying to do that didn't work?

Backing up using RSYNC and a rsync:// BACKUP_URL while using the ISO output (with a file:// OUTPUT_URL).

What is the impact of this issue to you?

Could have impact on customers, I suppose RSYNC is often used. Fortunately it does not lead to silent malfunction - the error is detected during mkrescue.

Please provide the package NVR for which the bug is seen:

rear-2.9-4.el10

How reproducible is this bug?:

well reproducible

Steps to reproduce

1. Use

   OUTPUT=ISO
   OUTPUT_URL=file:///mnt/scratchspace
   BACKUP=RSYNC
   BACKUP_PROG_EXCLUDE=( '/home/reartestuser/rsyncbackup' )
   BACKUP_URL=rsync://...
   

2. set up rsync server corresponding to BACKUP_URL
3. mkdir /mnt/scratchspace
4. run rear mkrescue

Expected results

rescue ISO is produced under /mnt/scratchspace

Actual results

ERROR: Could not copy result file /var/lib/rear/output/rear-vm-x.iso to /mnt/scratchspace/vm-x at file location
Some latest log messages since the last called script 950_copy_result_files.sh:
  2025-11-28 10:23:16.463303891 Copying resulting files to file location
  '/usr/share/rear/conf/templates/RESULT_usage_ISO.txt' -> '/var/tmp/rear.AYwNDVfJjaXuQ3r/tmp/README'
  2025-11-28 10:23:16.474936356 Saving /var/log/rear/rear-vm-x.log as rear-vm-x.log to file location
  2025-11-28 10:23:16.480851599 Copying result files '/var/lib/rear/output/rear-vm-x.iso /var/tmp/rear.AYwNDVfJjaXuQ3r/tmp/VERSION /var/tmp/rear.AYwNDVfJjaXuQ3r/tmp/README /var/tmp/rear.AYw
  '/var/lib/rear/output/rear-vm-x.iso' -> '/mnt/scratchspace/vm-x/'
  cp: cannot create regular file '/mnt/scratchspace/vm-x/': Not a directory