ITP: schleuder3, schleuder-conf, mail-gpg and some questions

Hello ruby people, Some weeks ago I was in the need of setting up a gpg-enabled mailinglist, so I wanted to install schleuder [1], but got to know that this exists only in wheezy. Nowadays there is a complete rewrite of the old codebase, named schleuder3. The description [2] reads: "Schleuder is

RFS: ruby-mail-gpg 0.2.6-1

Hi, The following package is ready to be reviewed / uploaded: ruby-mail-gpg 0.2.6-1 As this is my first package, I would be happy to get some pointers in case there is anything not in shape. Thanks in advance, Georg signature.asc Description: Digital signature

Re: RFS: ruby-mail-gpg 0.2.6-1

On 16-05-11 09:53:06, Jérémy Bobbio wrote: > The only mistake I could find by looking at the source is in > `debian/copyright`: > > “MIT” is an ambiguous term for the licence, see > . > The term most often refers to the Expat license: > <

Re: RFS: ruby-mail-gpg 0.2.6-1

On 16-05-11 11:28:03, Christian Hofstaedtler wrote: > Georg and me discussed this a bit on IRC [...] While chatting, zeha recommended to speak with dkg about this, which I just did. He gave me some pointers. I'm now trying to implement these and will send a follow-up. All the best, Georg signat

Re: RFS: ruby-mail-gpg 0.2.6-1

On 16-05-11 23:19:23, Jérémy Bobbio wrote: > Anyway, if upsteam license matches Expat, please use Expat in the > copyright file, as documented in the spec. Fixed in git. > > I didn't set up autopkgtest, because I disabled the tests. > > There are two kinds of tests: build time tests and “runtime

Re: RFS: ruby-mail-gpg 0.2.6-1

On 16-05-11 23:00:40, ge...@riseup.net wrote: > While chatting, zeha recommended to speak with dkg about this, which I > just did. He gave me some pointers. I'm now trying to implement these > and will send a follow-up. Finally some success: I've pushed some code [1] which s

Re: RFS: ruby-mail-gpg 0.2.6-1

On 16-05-12 01:34:17, ge...@riseup.net wrote: > Finally some success: I've pushed some code [1] which serves as a proof > of concept to run the tests in a gpg2 environment. One caveat left: One > of the tests uses a bad passphrase and asserts "Bad Passphrase". This > on

Re: RFS: ruby-mixlib-versioning, ruby-mixlib-shellout

On 16-05-13 16:51:41, Hleb Valoshka wrote: > I suppose it was 3.9.7 when I prepared these packages (or my lintian > is outdated). In case you're running jessie: There is 2.5.44~bpo8+1 in jessie-backports. signature.asc Description: Digital signature

Re: RFS: ruby-mail-gpg 0.2.6-1

On 16-05-13 13:54:25, Antonio Terceiro wrote: > On Thu, May 12, 2016 at 08:16:50PM +0200, ge...@riseup.net wrote: > > - Because I'll re-enable the tests, I had a look at the dependencies > > (again): mail-gpg depends on pry-nav [1], which depends on pry-remote > >

Re: RFS: ruby-mail-gpg 0.2.6-1

On 16-05-11 09:53:06, Jérémy Bobbio wrote: > For this reason, I think you should find a way to restore > `debian/ruby-tests.rake` and make it work with gpg2 as gpg1 is likely > to go away in some near future… - I've made some progress: - I've added a patch which injects gpg.conf and gpg-agent.c

Re: RFS: ruby-mail-gpg 0.2.6-1

On 16-05-16 12:04:38, Jérémy Bobbio wrote: > ge...@riseup.net: > > - I've made some progress: […] > > Great! :) Thanks for your input! > I'm surprised you need to both launch and reload gpg-agent. I think it > would also be much better to kill the agent once the

Re: RFS: ruby-mail-gpg 0.2.6-1

On 16-05-16 12:32:48, ge...@riseup.net wrote: > On 16-05-16 12:04:38, Jérémy Bobbio wrote: > > Both the hardcoded path and the binary files have the same root cause: > > this should all be generated on the fly as part of the test setup > > process. I really don't think

Re: RFS: ruby-mail-gpg 0.2.6-1

On 16-05-16 15:38:31, Jérémy Bobbio wrote: > Please do not generate the keys on the fly. Generating keys takes time > and can be flacky if entropy is low. I suggest having them stored in > ASCII-armored form and importing them in a freshly created GNUPGHOME > before running the tests. Alright. >

ruby-mail-gpg: Questions regarding 'dpkg-source: Local changes detected' and debian/control

Hi all, After quite some time, I was finally able to work again on the package, and I've got some questions: - I'm not sure why, but I guess when I've imported 0.2.9 into git, I forgot to do 'git push --all', instead I did 'git push', if I remember correctly. If I'm now building the packag

Re: ruby-mail-gpg: Questions regarding 'dpkg-source: Local changes detected' and debian/control

Hi, On 16-11-22 19:04:02, ge...@riseup.net wrote: > - I'm not sure why, but I guess when I've imported 0.2.9 into git, I > forgot to do 'git push --all', instead I did 'git push', if I remember > correctly. > > If I'm now building the pa

RFS: ruby-mail-gpg 0.2.9-1

Hi, The following packages are ready to be uploaded: ruby-mail-gpg 0.2.9-1 I've tested the package with lintian and piuparts, both pass. Additionally, I've enabled autopkgtest, the upstream provided tests work, and it builds fine in a chroot. Right now I'm not sure if debian/control is correct

Re: RFS: ruby-mail-gpg 0.2.9-1

Hi, On 16-11-22 20:01:08, ge...@riseup.net wrote: > The following packages are ready to be uploaded: > > ruby-mail-gpg 0.2.9-1 Holger Levsen did the upload, so this is done. Cheers, Georg signature.asc Description: Digital signature

schleuder packaging: Searching for input to run the tests

Hi all, As announced a while ago, I'm currently packaging schleuder, a GPG enabled mailing list manager. I'm nearly finished, and worked a lot with upstream these last days to fix various issues. For the moment I'm facing one last showstopper: There is one last hardcoded path inside the upstream

Re: schleuder packaging: Searching for input to run the tests

Hi Antonio, all, Sorry for me late reply, quite busy: On 16-12-08 16:03:14, Antonio Terceiro wrote: > On Thu, Dec 08, 2016 at 04:09:31PM +0100, ge...@riseup.net wrote: > > One idea we came up with is the following: > > > > Patch the upstream src: > > > >