Ah, my mistake. I misinterpreted this section. The .dsc file is correct. However, the .changes file is not. The relevant section, quoted below, implies that the Binary field of a .changes file must not list package names of binaries not actually built -- it's difficult to upload a non- existent file. I.e. Files and Binary must agree in a .changes file.
--------------------------------------------------------- 5.6.19 Binary This field is a list of binary packages. When it appears in the .dsc file it is the list of binary packages which a source package can produce. It does not necessarily produce all of these binary packages for every architecture. The source control file doesn't contain details of which architectures are appropriate for which of the binary packages. When it appears in a .changes file it lists the names of the binary packages actually being uploaded. The syntax is a list of binary packages separated by commas[36]. Currently the packages must be separated using only spaces in the .changes file. -- alsa-lib Binary: disagrees with Files: https://launchpad.net/bugs/88276 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
