can't publish a specific architecture after source is already published

[Jamie Strandboge]

With dak, I used to be able to publish source and binaries for completed architectures, but I cannot with soyuz. Eg:

1. upload openoffice.org
2. it builds on all architectures except armel, which is still slowly building
3. unembargo (syncSource?) openoffice.org
4. after armel finishes, try to unembargo it. This fails because the source is already published

This is an issue for the security team when there is an emergency update and we can't/don't want to wait around for an unofficial architecture to finish building, but do want to eventually publish it for that architecture.

[Julian Edwards (julian-edwards)]

The package copier infrastructure doesn't cope at all with this scenario :(

[Cody A.W. Somerville (cody-somerville)]

If "unembargo" means copy, this would also be an important issue to resolve for the OEM Services team.

[Robert Collins (lifeless)]

Does the new copier deal any better?

[Julian Edwards (julian-edwards)]

No, it's the same copier :)

[William Grant (wgrant)]

This probably works with the new copyPackage API.