Refusing to make a decision is a decision. Ansgar has explicitly set a requirement for including the checksums of the end result Debian source package in the tag. This requirement was not withdrawn or overridden by other FTP masters in the public list communications. And all (detailed) explanations why this requirement is not appropriate have been ignored. Ansgar even explicitly stated that no replies or explanations were read (due to lack of time).
If FTP masters (as a team) override this requirement publicly, then there should be no further obstacles to deploying tag2upload. Everything else has been already fully discussed. If not, then the GR is quite appropriate IMHO. If this was the same kind of discussion that happened five years ago, I can see why it was not continued. There is no point in service building a Debian source package where there is a hard requirement that the Debian source package must be a part of the inputs provided to the system. On Thu, Jun 27, 2024, 12:30 Joerg Jaspert <jo...@debian.org> wrote: > > > The ftpmaster team have refused to trust uploads coming from the > > tag2upload service. This GR is to override that decision. > > This is wrong, there has *NOT* been such a decision. > > > > In our design, the git tag contains simple metadata that can be > > written > > out by hand. ftpmaster stated a hard requirement that the signed tag > > must additionally include a manifest of all files in the .dsc. > > And that is wrong too. > > >
