ACL based reject for bullseye-backports upload
Hi,
I've got this ACL based reject message for a package I was trying to upload yesterday.
I'm pretty sure that I had been added to the ACL several months back, and even backported a few packages[1].
However one thing to note is that I had changed my (pgp) keys a few months back. Is it because of this reason? Does the list not pull those changes in automatically?
(I couldn't find anything relevant to this in the faq)
[1]: https://tracker.debian.org/news/1292734/accepted-amfora-192-2bpo111-source-amd64-into-bullseye-backports/
-------- Original Message --------
From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
Sent: 26 February 2023 4:04:50 am IST
To: Nilesh Patra <nilesh@debian.org>, Debian Ruby Team <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
Subject: ruby-selenium-webdriver_4.4.0-1~bpo11+1_amd64.changes REJECTED
Not accepted by any per-suite acl (suite=bullseye-backports)
binary:ruby-selenium-webdriver is NEW.
binary:ruby-selenium-webdriver is NEW.
source:ruby-selenium-webdriver is NEW.
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
Reply to: