On 16/04/2019 14.06, Robie Basak wrote: > Note that Ubuntu developers may upload (to Ubuntu) without updating the > VCS first. This is rather like an NMU in Debian, but more common. For > example, in Ubuntu uploads needed for library transitions are generally > driven from the library provider end, rather than the library consumer > end, and so uploads relating to a transition may just "appear" in the > archive. If this happens, you'll need to pull in those uploads to your > VCS, as the archive remains the single source of truth.
Thanks for the explanation. Come to think of it, in Debian, any DD can upload without touching the VCS, so... it's the same. :) >> I'll go ahead and create a team on LP as that seems to be a step in the >> right direction. Then I'll try to reflect the current state of Ubuntu >> packages in the Git repositories on salsa under ubuntu/ (changelog, >> patches, etc.) so that all of this can be unified. I'd still need >> sponsorship to upload though, but that can be sorted later. > > I suggest you announce your intentions to ubuntu-devel@ and > ubuntu-motu@, together with details on how to contact your team (perhaps > nominate ubuntu-motu@ for now, and subscribe). Ok so I'm now subscribed to ubuntu-motu and ubuntu-devel-announce lists (and ubuntu-devel if I manage to). What's the best way to represent this in Launchpad? - Shall I create a new team on LP or rather claim the team https://launchpad.net/~pkg-shibboleth-devel ("Is this a team you run?")? - Do I need to create a project as well? Etienne
signature.asc
Description: OpenPGP digital signature
-- Ubuntu-motu mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
