On Tue, 26 May 2020 at 22:15, Łukasz Zemczak <email address hidden>
wrote:
> Ok, that makes sense. But I think in this case we would still need this
> to be built in a security-enabled PPA and then copy it over to
> -proposed. Since if in the end we'd want to release this into both
> -updates and -security, we can't do that if we build it against
> -proposed. So in this case we'd need: upload to security-ppa (or
> tinkered bileto), bin sync to -proposed, testing in -proposed, release
> to -updates/-security.
>
On Tue, 26 May 2020 at 22:15, Łukasz Zemczak <email address hidden>
wrote:
> Ok, that makes sense. But I think in this case we would still need this
> to be built in a security-enabled PPA and then copy it over to
> -proposed. Since if in the end we'd want to release this into both
> -updates and -security, we can't do that if we build it against
> -proposed. So in this case we'd need: upload to security-ppa (or
> tinkered bileto), bin sync to -proposed, testing in -proposed, release
> to -updates/-security.
>
Oh in that case, reject the one in the queue and copy-with-binaries from /launchpad. net/~ubuntu- mozilla- security/ +archive/ ubuntu/ rust-updates/ +packages
https:/
--
the packages are usually copied from here into -security.