Re: ccrypt 1.11-1
On Fri, 10 Aug 2018, Raphael Hertzog wrote: On Fri, 10 Aug 2018, Alexander Kulak wrote: Is there any problems with this release? I don't think so. It's just that some of us (like me) are in vacation and not doing their usual workflows. If nobody else shows up, I will take care of this when I come back (after the 20th). Maybe you should try to get the Debian Maintainer status so that you can upload your own package in the future? Thanks for the suggestion, I need to compare my workflow with implied responsibility. For ccrypt 1.11, I believe upload after 20th is ok. It would be nice if you had time before the buster froze. -- Alexander Kulak
Re: ccrypt 1.11-1
On Sat, 28 Jul 2018, Alexander Kulak wrote: please consider uploading ccrypt 1.11-1. Changes: new upstream version, autotools and man formatting patches are no longer necessary, updated to latest standards. Is there any problems with this release? -- Alexander Kulak
ccrypt 1.11-1
Hello, please consider uploading ccrypt 1.11-1. Changes: new upstream version, autotools and man formatting patches are no longer necessary, updated to latest standards. -- Alexander Kulak
ccrypt 1.10-7
Hello, please consider uploading ccrypt 1.10-7. Change: fix removing obsoleted conffile (closes: #893687). -- Alexander Kulak
ccrypt 1.10-6
Hello, please consider uploading ccrypt 1.10-6. Changes: remove obsoleted conffile (closes: #893687), warn users in README about separation of emacs stuff. -- Alexander Kulak
Re: Please review ccrypt 1.10-5
On Tue, 13 Mar 2018, Raphael Hertzog wrote: I also wanted to ask you why you have a Build-Depends on "autopoint". It's not a common build dependency and I don't see a good reason for this. I believe it's not required anymore, removed. -- Alexander Kulak
Re: Please review ccrypt 1.10-5
On Tue, 13 Mar 2018, Raphael Hertzog wrote: On Tue, 13 Mar 2018, Alexander Kulak wrote: It sets new maintainer and fixes non-critical error and a bunch of warnings on install. If it's enough for publishing, please consider sponsoring it. I looked at your package but I'm not familiar with the emacs integration thing. I saw that you have a lintian warning about this: W: ccrypt: emacsen-common-without-dh-elpa Is there a reason for you to not use dh-elpa? If yes, then please override the lintian tag and document the reason as a comment in the lintian override file. If there is no reason, please consider using it. I saw a bunch of other minor problems reported by lintian (with -I to have informational tags too): I: ccrypt source: testsuite-autopkgtest-missing It's OK to not have such tests but here it would likely be not too hard to write a few tests and I invite you to consider writing some. I: ccrypt: hardening-no-bindnow usr/bin/ccguess I: ccrypt: hardening-no-bindnow usr/bin/ccrypt This can be fixed with "export DEB_BUILD_MAINT_OPTIONS = hardening=+all" in debian/rules. I: ccrypt: spelling-error-in-manpage usr/share/man/man1/ccrypt.1.gz contructed constructed Simple typo. Thank you for review. I tried to avoid dh-elpa because it requires creating a separate binary package, but after digging deeper (e86381a1 commit message) I have indeed created it. All informational lintian warning are fixed too, with distinct commit message where appropriate. -- Alexander Kulak
Re: Please review ccrypt 1.10-5
On Tue, 13 Mar 2018, Alexander Kulak wrote: Please review the ccrypt 1.10-5 prepared in HEAD (should I push version tags on my own decision before review?) https://salsa.debian.org/pkg-security-team/ccrypt It sets new maintainer and fixes non-critical error and a bunch of warnings on install. It also didn't build with recent autotools, fixed in https://salsa.debian.org/pkg-security-team/ccrypt/commit/7d19c73580c7b28f9eb64c064e326aa5f6c8a464 -- Alexander Kulak
Please review ccrypt 1.10-5
Hello. Please review the ccrypt 1.10-5 prepared in HEAD (should I push version tags on my own decision before review?) https://salsa.debian.org/pkg-security-team/ccrypt It sets new maintainer and fixes non-critical error and a bunch of warnings on install. If it's enough for publishing, please consider sponsoring it. -- Alexander Kulak
Re: New member
Hello, I can't check hooks, but debian/master is default now, thank you. On Mon, 12 Mar 2018, Gianfranco Costamagna wrote: hello, it might be ok now, please confirm! G. Il Lunedì 12 Marzo 2018 19:48, Alexander Kulak ha scritto: On Mon, 12 Mar 2018, Gianfranco Costamagna wrote: I was invited to the team to maintain ccrypt (ITA #879649, RFS #892483). Could you please create a repository for ccrypt and give my salsa account 'sa-guest' full team rights, if appropriate. I think I did it (sorry, this is my first time) please confirm I did it correctly! Gitlab shows me as a member and I'm able to push to ccrypt repo. Thank you! Sorry, I spotted that repository settings in Gitlab are unavailable for me. If it's as supposed, then please: set default branch to debian/master, setup automation hooks mentioned in wiki. -- Alexander Kulak
Re: New member
On Mon, 12 Mar 2018, Alexander Kulak wrote: On Mon, 12 Mar 2018, Gianfranco Costamagna wrote: I was invited to the team to maintain ccrypt (ITA #879649, RFS #892483). Could you please create a repository for ccrypt and give my salsa account 'sa-guest' full team rights, if appropriate. I think I did it (sorry, this is my first time) please confirm I did it correctly! Gitlab shows me as a member and I'm able to push to ccrypt repo. Thank you! Sorry, I spotted that repository settings in Gitlab are unavailable for me. If it's as supposed, then please: set default branch to debian/master, setup automation hooks mentioned in wiki. -- Alexander Kulak
Re: New member
On Mon, 12 Mar 2018, Gianfranco Costamagna wrote: I was invited to the team to maintain ccrypt (ITA #879649, RFS #892483). Could you please create a repository for ccrypt and give my salsa account 'sa-guest' full team rights, if appropriate. I think I did it (sorry, this is my first time) please confirm I did it correctly! Gitlab shows me as a member and I'm able to push to ccrypt repo. Thank you! -- Alexander Kulak
New member
Hello, I was invited to the team to maintain ccrypt (ITA #879649, RFS #892483). Could you please create a repository for ccrypt and give my salsa account 'sa-guest' full team rights, if appropriate. -- Alexander Kulak
