Bug#971015: RFS: vim-ultisnips/3.1-3.1 [NMU] [RC] -- snippet solution for Vim
On Wed, 30 Sep 2020 08:17:15 +0200 Tobias Frost wrote: > Did you talk with the maintainer about that change and he ACKED it? > > Otherwise it is inappropiate. For once, it was collab-maint before, so it > should > be the Debian namespace. Also, Michael is not member of the new > repo, so he would loose access. > > If you want to have it in the vim team, you need to either an ACK by Michael > or > do an ITS. I have no permission to create new projects under "debian" namespace. Can you please move or reimport the repository? Does it still matter since Michael Fladischer, current maintainer, does not mind adopting the package? While I was trying to keep changes as little as possible, things get harder without active VCS. So I had to modify link to Git in the d/control file. Former repository on alioth was deleted and not functioning anymore. So I think at Michael point of view, access rights do not change. Sorry for late response, I did not receive your message in my inbox and just now saw it at bugs.d.o site. signature.asc Description: This is a digitally signed message part
Bug#971015: RFS: vim-ultisnips/3.1-3.1 [NMU] [RC] -- snippet solution for Vim
Hi Nicholas, sorry it took me a while to respond .. kids starting kindergarten and so on ... Am 26.09.2020 um 10:38 schrieb Nicholas Guriev: I was trying to keep the changes as little as possible. I only replaced python2 string with python3 where found, and I excluded ".pyc" files related to second Python. The plugin itself works okay with Python 3.8 from buster. Any other warnings reported by lintian still left untouched. If Michael Fladischer does not mind, I could adopt the package and bring to a fresh form, switching to a modern "packadd" feature and dh-vim-addon instead of obsoleted vim-addon-manager. I'm totally OK with you adopting the package, I'm not that active in the vim space anymore (my setup is complete) and I want to focus on Python/Django. So feel free to change the maintainer field and remove me from d/control. Regards, Michael
Bug#971015: RFS: vim-ultisnips/3.1-3.1 [NMU] [RC] -- snippet solution for Vim
Control: tags -1 moreinfo On Sat, 26 Sep 2020 11:38:49 +0300 Nicholas Guriev wrote: > Package: sponsorship-requests > Severity: important > Control: block 938777 by -1 > X-Debbugs-CC: Debian Vim Maintainers > X-Debbugs-CC: Michael Fladischer > > Dear mentors, > > I am looking for a sponsor for my package "vim-ultisnips": > > * Package name: vim-ultisnips >Version : 3.1-3.1 >Upstream Author : Holger Rapp > * URL : https://github.com/SirVer/ultisnips > * License : GPL-3+ > * Vcs : https://salsa.debian.org/vim-team/vim-ultisnips >Section : editors > > It builds those binary packages: > > vim-ultisnips - snippet solution for Vim > > To access further information about this package, please visit the following URL: > > https://mentors.debian.net/package/vim-ultisnips/ > > Alternatively, one can download the package with dget using this command: > > dget -x https://mentors.debian.net/debian/pool/main/v/vim-ultisnips/vim-ultisnips_3.1-3.1.dsc > > Or you can see diff in recently imported Git project at salsa.d.o: > > https://salsa.debian.org/vim-team/vim-ultisnips/-/commit/01d9924e156a02d3d43d1997055a53b7405fed93 > > Changes since the last upload: > > vim-ultisnips (3.1-3.1) unstable; urgency=medium > . (...) >* Move packaging repository to a new GitLab instance at salsa.debian.org. Did you talk with the maintainer about that change and he ACKED it? Otherwise it is inappropiate. For once, it was collab-maint before, so it should be the Debian namespace. Also, Michael is not member of the new repo, so he would loose access. If you want to have it in the vim team, you need to either an ACK by Michael or do an ITS. -- tobi
Bug#971015: RFS: vim-ultisnips/3.1-3.1 [NMU] [RC] -- snippet solution for Vim
Package: sponsorship-requests Severity: important Control: block 938777 by -1 X-Debbugs-CC: Debian Vim Maintainers X-Debbugs-CC: Michael Fladischer Dear mentors, I am looking for a sponsor for my package "vim-ultisnips": * Package name: vim-ultisnips Version : 3.1-3.1 Upstream Author : Holger Rapp * URL : https://github.com/SirVer/ultisnips * License : GPL-3+ * Vcs : https://salsa.debian.org/vim-team/vim-ultisnips Section : editors It builds those binary packages: vim-ultisnips - snippet solution for Vim To access further information about this package, please visit the following URL: https://mentors.debian.net/package/vim-ultisnips/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/v/vim-ultisnips/vim-ultisnips_3.1-3.1.dsc Or you can see diff in recently imported Git project at salsa.d.o: https://salsa.debian.org/vim-team/vim-ultisnips/-/commit/01d9924e156a02d3d43d1997055a53b7405fed93 Changes since the last upload: vim-ultisnips (3.1-3.1) unstable; urgency=medium . * Non-maintainer upload. * Shift to Python 3 already supported by the plugin. (Closes: #938777) * Move packaging repository to a new GitLab instance at salsa.debian.org. I was trying to keep the changes as little as possible. I only replaced python2 string with python3 where found, and I excluded ".pyc" files related to second Python. The plugin itself works okay with Python 3.8 from buster. Any other warnings reported by lintian still left untouched. If Michael Fladischer does not mind, I could adopt the package and bring to a fresh form, switching to a modern "packadd" feature and dh-vim-addon instead of obsoleted vim-addon-manager. Regards, signature.asc Description: This is a digitally signed message part
