Hello,

On Tue 16 Dec 2025 at 09:43am +01, Philip Hands wrote:

> Finally: what is this bug actually about:
>
>   a) It would be nice if there were some way of uploading to backports in a 
> way
>      that would put the upload on hold until the migration to testing happens 
> --
>      I've no idea if tag2upload can help with that.
>
>   b) Failing that, it would be nice if git-debpush and/or dgit would check if
>      there there is a more up-to-date version in testing before allowing an
>      upload to backports.

It would have to be opt-in, because sometimes it is legitimate to skip
waiting for migration, such as in the case of a security fix.

If we thought it was worth it we could have an additional piece of tag
metadata to implement some kind of DELAYED queue for tag2upload.
That would mean Debian having two separate DELAYED queues, though, which
could be confusing.

>   c) If it is the case that there is something about tag2upload uploads that 
> is
>      preventing one being informed that an upload has been rejected on this
>      basis (or any other basis for that matter), that should probably be 
> fixed.

This is the "os-autoinst debian/5.1764330105.c5cfd48b-1_bpo13+1" upload,
right?

It looks like dak decided to silently reject that, because I don't see
any mail from dak to <[email protected]>.  I would guess that
it is a bug in dak's handling of tag2upload uploads.  I don't think
there is any reason to think there is a bug at the tag2upload end.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature

Reply via email to