On Fri, 14 Jun 2024 at 12:26:50 +0100, Ian Jackson wrote:
> Note however: right now you can't do a source-only upload of a new
> upstream version, and tag2upload only supports source-only uploads.
> So this situation generally won't arise: someone will have had to
> upload the orig.tar.gz the old way.
I think I must be misunderstanding you, because as far as I can see,
I do source-only uploads of new upstream versions rather frequently
(for example flatpak_1.14.8-1 was a source-only upload, for which
I think I used dgit). To achieve that, I need to arrange to have a
suitable orig.tar.* where dpkg-buildpackage or dgit are going to find it
(currently achieved with uscan and/or pristine-tar), which I recognise
is non-trivial to achieve for tag2upload.
You can't currently do a source-only upload of a completely new *package*,
or of a new upstream release that bumps SONAME or otherwise adds new
binary packages, because the ftp team requires a binary upload[1] for
anything that will go into the NEW queue. Is that what you're thinking of?
But most new upstream releases (at least for relatively mature packages)
don't break backwards compatibility and don't need to go through NEW.
smcv
[1] technically the upload needs at least one binary package, but
presumably the ftp team usually prefer uploaders to follow the spirit
of the rules as well as the letter, and the spirit of the rule is that
they want to see a comprehensive set of binary packages for at least
one architecture so that Lintian can flag any obvious mis-packaging
