Hello,

Otto Kekäläinen [10/Feb 11:54pm +08] wrote:
> The tag2upload service is tightly coupled with dgit, and while dgit by
> design will never support pristine-tar type of ability to reproduce
> upstream tarballs bit-for-bit, it should at least have the actual
> upstream signed tags instead (from upstreams that publish them).

This is completely false.

There are no fundamental design blockers for any of this.

> There were already suggestions on debian-devel@ that maintainers
> should use dgit push for the initial -1 upload and git debpush for the
> -1+N uploads. That is obviously overly complex and shows that this is
> not ready to be recommended to newbies in the developers reference.

This advanced workflow might be useful to some maintainers and I'm glad
to see them discussing it, but it's not what the tag2upload Delegates
would recommend to newcomers -- we do not need to do that.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature

Reply via email to