Re: [RFC] General Resolution to deploy tag2upload

[Ian Jackson <ijackson@chiark.greenend.org.uk>]

Andreas Tille writes ("Re: [RFC] General Resolution to deploy tag2upload"):
> That means some package build process is done before the source
> package is forwarded to dak and sends some e-mail back?

Only a source package build.

> I know we have this.  My point is that tag2upload users might forget
> to use it before using tag2upload service.  I simply want to make
> sure that tag2upload is not another way to upload anything that does
> not build on buildservices.

I'm afriad that tag2upload is precisely another way to do that.

That's because that's how uploading works now, and tag2upload is
another way to make an upload.  Uploads must be source-only nowadays
(in most cases).  So there is, by design, nothing in the existing
setup that ensures that a maintainer built binaries.  (I get the
feeling that you're not happy with this situation, but that's how
Debian is now, and I think it's a jolly good thing.)

You might argue that tag2upload makes this worse because it makes it
easier to perform uploads.  It certainly *does* make it easier to
perform uploads.  That's a big part of the point.

I think this can only be a *downside* if you think it is a good
thing that uploading is difficult.

Ian.

-- 
Ian Jackson <ijackson@chiark.greenend.org.uk>   These opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.