Bug#758826: [patch] fix if $HOME is not writable

2014-08-22 Thread Michael Vogt
On Fri, Aug 22, 2014 at 05:12:53PM +0200, Guillem Jover wrote: > Hi! Hi, > On Thu, 2014-08-21 at 21:12:20 +0200, Michael Vogt wrote: > > Package: debsig-verify > > Version: 0.10 > > > I ran into a issue today that debsig-verify would fail if $HOME was > > not writable to the debsig-verify progre

Bug#758826: [patch] fix if $HOME is not writable

2014-08-22 Thread Guillem Jover
Hi! On Thu, 2014-08-21 at 21:12:20 +0200, Michael Vogt wrote: > Package: debsig-verify > Version: 0.10 > I ran into a issue today that debsig-verify would fail if $HOME was > not writable to the debsig-verify progress. The reason is that gpg > tries to create/read a ~/.gnupg/{pubring,secring}.gpg

Bug#758826: [patch] fix if $HOME is not writable

2014-08-21 Thread Michael Vogt
Package: debsig-verify Version: 0.10 Hi, I ran into a issue today that debsig-verify would fail if $HOME was not writable to the debsig-verify progress. The reason is that gpg tries to create/read a ~/.gnupg/{pubring,secring}.gpg. Attached is a patch that run gpg with its own GNUPGHOME instead o