> ---------- Forwarded message ---------- > From: Adam Borowski <kilob...@angband.pl> > To: 901584-d...@bugs.debian.org > Cc: > Bcc: > Date: Fri, 15 Jun 2018 15:37:07 +0200 > Subject: Re: Bug#901584: RFS: flameshot/0.5.1+git20180601-1~bpo9+1 > On Fri, Jun 15, 2018 at 11:04:31AM +0800, Boyuan Yang wrote: > > I am looking for a sponsor for my package "flameshot" into > > stretch-backports. > > > > * Package name : flameshot > > Version : 0.5.1+git20180601-1~bpo9+1 > > It's an update, so it doesn't need to go through NEW, and you got DM rights. > So you should be able to upload it yourself... > I've done it this time, though.
According to https://backports.debian.org/Contribute/ : "All Debian Developers (DD) can get their uid into the backports ACL. If you want to get include please open a ticket in the debian request tracker - please use the backports queue for the ticket." [...] "Debian Maintainers (DM) can also get their uid into the backports ACL. Please follow the instructions for Debian Developers." "The Debian Maintainer needs to have upload rights for the specific package they want to upload to backports (the same right they need for uploading that package to unstable), otherwise the upload will not succeed." That essentially means that a DM can only directly upload onto Debian's backports repositories if: 1. That Debian Maintainer is granted DM upload right for the package; 2. and that Debian Maintainer asks another Debian Developer to open an RT ticket to get the uid into the backports ACL and wait till the ticket is finished. Note that non-DDs have no access to RT system thus a sponsorship of RT ticket from other DDs is needed. I'm not proposing an alternative procedure, but it is a fact that many contributors are not familiar with the requirement and that this procedure has limited the contributions from DMs to upload their packages into backports repositories. -- Regards, Boyuan Yang