syncSource doesn't send primary/partner archive syncs through queue
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
I attempted to work around bug 529933 by performing the sync myself. This failed with the following oops:
https:/
The component here, 'non-free', is the Debian component, and is not valid in Ubuntu. Even if syncSource did the standard component mappings performed elsewhere in Soyuz, which it should, this would end up in 'multiverse' when what I really want in this case is for it to go to 'partner'. In any case, as indicated in bug 529933, the end goal is to allow uploaders to perform syncs themselves, and for that to work properly syncs of new packages need to go through the NEW queue so that archive administrators can check them and apply overrides as necessary.
Please arrange for syncSource to the primary/partner archives to insert uploads into the queue rather than accepting them directly. Of course, this wouldn't be appropriate for PPAs.
| Julian Edwards (julian-edwards) wrote | #1 |
| Changed in soyuz: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: soyuz-core soyuz-upload |
| Julian Edwards (julian-edwards) wrote | #2 |
| Changed in launchpad: | |
| status: | Triaged → Won't Fix |
This is basically what native-source-sync from Debian will need to do, but leaving this bug open so Colin can track it separately.