Dear Maintainer,

I am setting up a mirror on a system in an area with very limited internet
access, to deploy Wheezy i386, Stretch i386 or Stretch amd64 (depending on
the hardware capability) on several older machines.

As I did not see the need to mirror Wheezy amd64, I used the line
@arches="i386,amd64(-wheezy)"; in my debmirror.conf file.

This may explain why, when attempting finalize the mirror today, an apt-get
update for Stretch amd64 would fail (404 for the main repo Package
manifest).  When I looked in the mirror repo, I have found:

joel@cybaryme ~> ls -l /tank/deb/dists/stretch/main/
total 13
drwxr-xr-x 2 joel joel 5 Nov  1 16:37 binary-i386/
drwxr-xr-x 3 joel joel 3 Nov  1 16:37 debian-installer/
drwxr-xr-x 2 joel joel 6 Nov  1 16:37 dep11/
drwxr-xr-x 2 joel joel 3 Nov  1 16:37 i18n/
joel@cybaryme ~>

I could try dropping the exclusion however I don't want to exceed the 160GB
allowance for the mirror (currently at 108GiB).

Below is my snippet of my .debmirror.conf for reference

# Download options
$host="mirror.its.dal.ca";
$user="anonymous";
$passwd="anonymous@";
$remoteroot="debian";
$download_method="ftp";
@dists="stretch,wheezy";
@sections="main,main/debian-installer,contrib,non-free";
@arches="i386,amd64(-wheezy)";
$omit_suite_symlinks=0;
$skippackages=0;
$i18n=0;
$getcontents=0;
$do_source=0;
$max_batch=0;

Control: retitle -1 debmirror: ability to specify architectures to mirror per suite
Control: severity -1 wishlist

I'm not sure where you found this syntax, but as far as I can see it's
nowhere in the debmirror documentation, and it'd simply mean "mirror the
architectures called 'i386' and 'amd64(-wheezy)'".  Since there's no
architecture called 'amd64(-wheezy)', you get the behaviour you
observed.

I'm therefore turning this bug into a feature request for the ability to
do what you're asking for here (probably not with exactly that syntax),
since as far as I know it's simply not possible with debmirror today.
(It might be possible with multiple runs on a shared directory and a
great deal of care, but I don't see how you'd be able to do cleanup in a
sensible way, at least not without reimplementing that part.)