Bug#541538: duplicates and age of this bug

2018-03-09 Thread draeath
Hello, it seems that there are several older bugs about this configuration: #674935 and #674936 (duplicate submission) #697119 These go back to *early 2012* Can we maybe get this default configuration value adjusted? We're not talking about a code patch, here. Thanks.

Bug#866026: volunteer for pygpgme to python[3]-gpg pivot

2017-07-12 Thread draeath
Sigh, that last instance there should be "python-gpg." These names are all too similar. On Wed, Jul 12, 2017 at 6:55 PM, draeath wrote: > let me know if you'd prefer me to use python-gnupg instead

Bug#866026: volunteer for pygpgme to python[3]-gpg pivot

2017-07-12 Thread draeath
Patch tested on stretch, seems to do the job. Can't imagine it wouldn't work on testing, too. Unfortunately, by the time I realized that "python-gpg" and "python-gnupg" are not the same thing, I was done. Please do let me know if you'd prefer me to use python-gnupg instead, and I'll be happy to. Th

Bug#866026: volunteer for pygpgme to python[3]-gpg pivot

2017-07-12 Thread draeath
lt; mike.gabr...@das-netzwerkteam.de> wrote: > Hi, > > On Do 06 Jul 2017 06:41:08 CEST, draeath wrote: > > One month does not seem like a lot of turnaround time for this. Does this >> package have an active maintainer? I'm willing to look into updating this >> a

Bug#866026: volunteer for pygpgme to python[3]-gpg pivot

2017-07-05 Thread draeath
One month does not seem like a lot of turnaround time for this. Does this package have an active maintainer? I'm willing to look into updating this and providing a patch, but I might need some handholding on the process side. (I'm familiar with casual site-local usage of debuild, but I do not curre