On Friday, December 29 2017, Gabriel F. T. Gomes wrote: > On 29 Dec 2017, Sergio Durigan Junior wrote: >>On Friday, December 29 2017, Gabriel F. T. Gomes wrote: >>> On 22 Dec 2017, Sergio Durigan Junior wrote: >>> >>Yeah, that's right. I'm still using git.debian.org for my packages, >>but I should change that as well. > > I changed to the new server and fixed the Vcs-* fields accordingly: > > https://salsa.debian.org/gabrielftg-guest/bash-completion-debian/commit/f2140c2633a8849d423d475a91db9ba40ff840c9 > >>Cool. As I said, I consider this to be a matter of preference; I >>personally wouldn't bother to see /etc/bash_completion.d/ still there >>in the next release. But thanks for doing that. > > Also fixed: > > https://salsa.debian.org/gabrielftg-guest/bash-completion-debian/commit/e4185da001ceafbc713806faa4315cb8443471be > >>>>It's also a good idea to bump the Standards-Version to 4.1.2 now. >>> >>> OK. >> >>4.1.3 now :-). > > Also fixed: > > https://salsa.debian.org/gabrielftg-guest/bash-completion-debian/commits/unstable
Thanks for doing that. So, unfortunately salsa doesn't provide a good way for non-DDs to create projects under the Debian group, which is the equivalent of the "collab-maint" namespace on Alioth. For that reason, the best approach in this case would be to ask a DD to create the "bash-completion" project under the Debian group, and put you as the responsible for it. This is the best way because it guarantees that other developers will have access to the repository if you go AWOL. I am not yet a DD (waiting on my process to advance), so I can't do it for you :-(. > Thanks for the reviews, so far. :) <3 > > If and when you can, could you review these last changes? > If so, would you also be willing to sponsor the package? > (it's on mentors: https://mentors.debian.net/package/bash-completion) After the project is created under the Debian group and you update the Vcs-* fields accordingly, I consider this package as ready for upload. As I'm not yet a DD, I can't really sponsor your changes, but I can certainly put you in touch with someone who can if you need. Cheers, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/
