Re: Binary upload required, messed it up.
Nicholas D Steeves <[email protected]>
| Newsgroups | gmane.linux.debian.backports.general |
|---|---|
| Message-ID | <[email protected]> |
Alec Leamas <[email protected]> writes: > On 21/06/2023 11:16, Alec Leamas wrote: > >> I'm trying to maintain the opencpn package. Last release missed the >> freeze, so I need to get it into the bullseye-backports and >> bookworm-backports list. A package currently in testing/trixie? That will need to go into bullseye-backports-sloppy, not bullseye-backports. >> - What is happening to my uploads to bookworm-backports? Does this >> branch actually exist today? It is obviously missing in a lot of places. Alexander Wirt's addressed this, on list, minutes after your email. > No. I actually get a "ACL dm: NEW uploads are not allowed" REJECT > message. What does this mean? That I need help to get my package > uploaded and/or updating my DM permissions somehow? > >> Anyone who can shed some light on this? I seem to remember that uploading a NEW package to backports is just like uploading a NEW package to the normal ftp-master queue. Also, I seem to remember that DMs need to ask for the backports ACL for every stable-backports release. Is this still the case? Regards, Nicholas
signature.asc
(application/pgp-signature, 857 B)
-----BEGIN PGP SIGNATURE----- iQJEBAEBCgAuFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmSThpAQHHN0ZW5AZGVi aWFuLm9yZwAKCRBaiDBHX30QYamWEACQdFXSXnjE8AkKzW4tOZqs+x9z2qnQTJ04 d5cdFhxRveWj3COz7jk9ilDbz/FnQjFN1eubwLKuTnc9VrM9VrZf10WUzaZduao+ eng6IsN+uGcUU8Ap1nvXIjWhtiYtKQPgv+JF09xTNLGBxT3oN6maZgBcQJv2nvk/ CDV/MPHlxXIxVTjx+FevFwvD/NvXYnBAbEnjU+gJ9NzKetmiu7CZpqq6bMzs3Oql EYg7zgXu9l4Fkoy9WDpeLFonB88P5dv7CDQLWIYSTQXAKKaoaCuG9CXV9lXIOw9r ZpNO+I07kIZm7gelyRG4l6nWCDCTDf5WdWCBGCyw2/GCFcyQwTXMTMJzuQZbEP4u qNX5/XX5abc09wTpkSRuBo7bzAsx3vbJZXiwgCRI69Ay8+PsXrZNYUryU5XA1wJb cTXYLst0XpyfqEwXb8n3/yox4vkpxW3uURoGJ/RloAcr4ryNmD1oExa2fYL4jmKL ZrvmCVn0jj5BbnGQSo27NVb0nAXIeKPdW9tyrVpBYb38VQzaJ/hzQrXYiDQZCofc lLAYaccD5dS9PnNQ71XGCtlwXw8MCwmqqNoHmAyOfmz5CLQ+ASWL1oFTa0IR7iZf NAnMnncI5MnkUR2D6GGmVV/gGb5ycc/rQFohlGMKrhRspoonjJNz45PD2pWFh6uq RGeCPNwf1w== =ZbmK -----END PGP SIGNATURE-----