The actual issue you were reported was because the partner-component permission for the ubuntu-archive team was on the *primary* archive, rather than the partner archive. If this permission has been fixed and you still experience this problem, please let us know.
Hi Dustin,
As in comment 2 above, the original problem seemed to be an incorrect permission: /bugs.edge. launchpad. net/soyuz/ +bug/530180/ comments/ 2
https:/
The actual issue you were reported was because the partner-component permission for the ubuntu-archive team was on the *primary* archive, rather than the partner archive. If this permission has been fixed and you still experience this problem, please let us know.