#66 compose-partial-copy needs to understand s390x arch
Closed: Duplicate 6 years ago Opened 6 years ago by mohanboddu.

When I ran compose-partial-copy with s390x arch, it rsync'ed but in an oddly different path:

[mohanboddu@bodhi-backend01 releng][PROD]$ compose-partial-copy --arch=armhfp --arch=x86_64 --arch src --arch=aarch64 --arch=i386 --arch=ppc64 --arch=ppc64le --arch=s390x /mnt/koji/compose/27/Fedora-Modular-27-20171108.2/compose/$dir/ /pub/fedora/linux/modular/releases/test/27_Modular_Beta/$dir/ --variant Server --dry-run
rsync -avHh /mnt/koji/compose/27/Fedora-Modular-27-20171108.2/compose/Server /pub/fedora/linux/modular/releases/test/27_Modular_Beta//mnt/koji/compose/27/Fedora-Modular-27-20171108.2/compose

[mohanboddu@bodhi-backend01 releng][PROD]$ compose-partial-copy --arch=armhfp --arch=x86_64 --arch src --arch=aarch64 --arch=i386 --arch=ppc64 --arch=ppc64le /mnt/koji/compose/27/Fedora-Modular-27-20171108.2/compose/$dir/ /pub/fedora/linux/modular/releases/test/27_Modular_Beta/$dir/ --variant Server --dry-run
rsync -avHh /mnt/koji/compose/27/Fedora-Modular-27-20171108.2/compose//Server/aarch64 /mnt/koji/compose/27/Fedora-Modular-27-20171108.2/compose//Server/armhfp /mnt/koji/compose/27/Fedora-Modular-27-20171108.2/compose//Server/i386 /mnt/koji/compose/27/Fedora-Modular-27-20171108.2/compose//Server/ppc64 /mnt/koji/compose/27/Fedora-Modular-27-20171108.2/compose//Server/ppc64le /mnt/koji/compose/27/Fedora-Modular-27-20171108.2/compose//Server/source /mnt/koji/compose/27/Fedora-Modular-27-20171108.2/compose//Server/x86_64 /pub/fedora/linux/modular/releases/test/27_Modular_Beta//Server

Not sure if #61 is a fix, but just proposing the issue.


This is indeed the same issue as what #61 fixed. Please update to compose-utils 0.1.17 which contains the fix.

As a workaround you can remove the trailing slash from the path to the compose. Please note that the example command in the description uses an undefined variable $dir. In the script the snippet is taken from it may be defined to something reasonable, but I would recommend double checking just to be sure.

Metadata Update from @lsedlar:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)

6 years ago

Login to comment on this ticket.

Metadata