Debian package repository cannot be mirrored by Aptly

[jstangroome]

The Architectures: line in the Release file conflicts with the architectures of the available packages.

$ curl http://packages.elastic.co/logstashforwarder/debian/dists/stable/Release
Architectures: noarch
...
SHA1:
 da39a3ee5e6b4b0d3255bfef95601890afd80709                0 Release
 5f6fcbd97954082f65caf5fd11802a558e8c7dc8              690 main/binary-all/Packages
 be5ae50d21ecd76e0779bb934a601897b434520c              476 main/binary-all/Packages.gz
 5f6fcbd97954082f65caf5fd11802a558e8c7dc8              690 main/binary-amd64/Packages
 be5ae50d21ecd76e0779bb934a601897b434520c              476 main/binary-amd64/Packages.gz
 5f6fcbd97954082f65caf5fd11802a558e8c7dc8              690 main/binary-i386/Packages
 be5ae50d21ecd76e0779bb934a601897b434520c              476 main/binary-i386/Packages.gz
...

Subsequently Aptly tries to access the noarch Packages file but gets a 404. I suspect the Elastic Release file should specify Architectures: i386 amd64 or similar.

I will raise a similar issue with Aptly to cope with the existing format of the Release file.

[jstangroome]

Issue for Aptly: https://github.com/smira/aptly/issues/305

[ruflin]

@tsg Does this affect us also in beats-packer? https://github.com/elastic/beats-packer