Hi Micha,sorry for that. I did not get any mail about the rejection of my uploaded package. It just vanished silently from the NEW-queue after some hours.
Only yesterday evening I found the documentation where the reason, you just mentioned in your mail, was documented. To verify that this was the problem with ntirpc, I uploaded ntirpc/6.3-3 to trixie-backports.
It would really help, if the uploader gets a mail about the reason of the rejection of the upload.
Sorry again for my tries and not having the rule in mind.
Backports tracks testing and only package versions included in testing are allowed in it, subject to a few expedient exceptions.
BTW. This seems only to be enforced for the NEW-queue and not for later uploads.
Regards Christoph Am 09.01.26 um 15:35 schrieb Micha Lenk:
I've now rejected ntirpc/6.3-4 from BACKPORTS-NEW three times in a row for the same reason: Am 8. Januar 2026 22:11:10 MEZ schrieb Micha Lenk <debian-backports@lists.debian.org>:No upgrade path from trixie+trixie-backports to forky (backported version 6.3-4~bpo13+1 >= 6.3-3) ... in other words: ntirpc/6.3-4 hasn't reached testing yet. It is too early to backport it.Would you please mind to explain why uploading the very same version a fourth time before 6.3-4 migrated to testing would be acceptable? Why do you believe the rules outlined on <https://backports.debian.org/Contribute/>, namely:Backports tracks testing and only package versions included in testing are allowed in it, subject to a few expedient exceptions.... do not apply to this upload?
Attachment:
OpenPGP_0x04EE131AE6D621BE.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature