Nicolas Schodet [11/Feb 10:24pm +01] wrote: > I think many of us needs to understand how the system works under the > hood to trust it. > > The best explanation I found was in the sevice design document[1]. I > have the feeling that at least the overall structure and dataflow could > be added to the manual page. > > Before reading this doc, I had questions about how the package was > uploaded. Do I need ssh access somewhere? Do I need to push to a special > repository? How is it related to dgit? > > As a DM, I was also wondering whether I had the right access to use it > (it’s clear now, I only need push access to salsa).
You found the document that would satisfy what you wanted to know, TAG2UPLOAD-DESIGN.txt. We could consider adding a reference to that to the bottom of the manpage. We are keen that git-debpush(1) remains short and sweet. Not mentioning dgit is important because many people would find that off-putting. > On a separate topic, now I want to try to use dgit (and git-debrebase!), > but I did not find how pushing to the dgit repo is done (I suppose it > needs my ssh pubkey), maybe it’s not possible for a DM, or maybe > git-debpush renders dgit push obsolete? dgit pushes aren't obsolete because you need them to do source+binary uploads to NEW. As a DM, in order to use dgit (but not tag2upload), you need your key adding to a certain keyring. Send it in a signed message to [email protected]. -- Sean Whitton
signature.asc
Description: PGP signature
