dgit can upload to the main Debian archive and various overlay suites
(security, proposed-updates, backports), but not currently to fasttrack
(https://fasttrack.debian.net/). I'm experimenting with using fasttrack
for leaf packages that are not supportable with minimal changes for the
duration of a stable release, like src:openjk (which is "backported" from
experimental, and has never had any sort of a formal upstream release).

fasttrack is technically a separate archive (separate dak instance) like
-security, but it exists in the same package/version namespace as the
main Debian archive, so I think it could make sense to push its packages'
source to dgit.debian.org.

I tried this configuration in ~/.gitconfig, based on how -security works:

[dgit-distro "debian-fasttrack"]
	archive-query = "aptget:"
	upload-host = fasttrack
	nominal-distro = debian
[dgit-suite "*-fasttrack"]
	distro = debian-fasttrack

together with this in ~/.dput.cf:

[fasttrack]
fqdn = fasttrack.debian.net
incoming = /pub/UploadQueue/
login = anonymous
allow_dcut = 1
method = ftp
allowed_distributions = (?:bookworm|trixie)-fasttrack

but attempting to upload here failed with:

$ dgit push-built -C /path/to/openjk_*_source+amd64.changes
dgit: invalid configuration: bad syntax for (nominal) distro `ARRAY(0x55f9655a93e8)' (does not match /^[0-9a-zA-Z][-+.0-9a-zA-Z]*

Would it be possible to either support fasttrack by default, or document
it in the man page as an example of an overlay suite?

(Normally I would use dgit push-source, but fasttrack doesn't currently
have buildds or any other sort of autobuilder, so maintainer-built
binaries are the only option; and as a result it would have to be
out-of-scope for tag2upload.)

Thanks,
    smcv

Simon McVittie writes ("Bug#1107111: dgit: support for uploading to fasttrack.debian.net"):

TIL.

dgit ought to be able to support this but I think I need to know more
about it to decide how.

Some questions I didn't find answered elsewhere:

Does it run on DSA infrastructure?  Do packages migrate between it
and the main archive at all?  Is there any official recognition
of these suite names from a namespace point of view?

That sounds plausible but I think I need to think about it.

The aptget archive query method is very bad.  It may suffice here.  I
can't remember all the things that are wrong with it.  It may be
inadequate for a read/write suite.  I'll have to look into this.

Maybe the madison method would work better.

I notice that both the madison and aptget methods have
`file_in_archive` and `package_not_wholly_new` stubbed out, but there
seems to be cdoe to cope with this situation.

I think we might have to make a change on the dgit git server to allow
pushing to -fasttrack suites.

This error message suggests a bug in the perl code.

I don't think I will have time to investigate this very soon - I'm
abou to go away for a week.  Feel free to ping if nothing happens
after several weeks...

Thanks,
Ian.