Bug#649769: Info received (Bug#649769: obnam: "obnam --encrypt-with" fails with "can't query passphrase in batch mode")

2012-05-05 Thread Lars Wirzenius
On Tue, Jan 03, 2012 at 06:03:32PM +, Dafydd Harries wrote: > Setting use-agent means that obnam asks for my passphrase correctly. I'll consider that part solved. > However, now I get a different error. > > 2012-01-03 12:59:40 INFO Obnam 0.24 starts > 2012-01-03 12:59:40 INFO Backup starts >

Bug#649769: Info received (Bug#649769: obnam: "obnam --encrypt-with" fails with "can't query passphrase in batch mode")

2012-01-03 Thread Dafydd Harries
Ar 01/01/2012 am 15:29, ysgrifennodd Lars Wirzenius: > On Sun, Dec 25, 2011 at 09:55:46PM +, Dafydd Harries wrote: > > Strane that you get a passphrase dialog, though. That suggests that > > there's something that's different in my environment. It would be good > > to find out what that is. >

Bug#649769: Info received (Bug#649769: obnam: "obnam --encrypt-with" fails with "can't query passphrase in batch mode")

2012-01-01 Thread Lars Wirzenius
On Sun, Dec 25, 2011 at 09:55:46PM +, Dafydd Harries wrote: > Strane that you get a passphrase dialog, though. That suggests that > there's something that's different in my environment. It would be good > to find out what that is. I can reproduce this by having "use-agent" in my gpg.conf, and

Bug#649769: Info received (Bug#649769: obnam: "obnam --encrypt-with" fails with "can't query passphrase in batch mode")

2011-12-25 Thread Dafydd Harries
Ar 22/12/2011 am 13:19, ysgrifennodd Lars Wirzenius: > On Tue, Dec 20, 2011 at 05:59:11AM +, Dafydd Harries wrote: > > One additional annoyance is that when it crashes, it leaves the "root.lock" > > file in place, which means I need to manually remove it before trying again. > > You can use th

Bug#649769: Info received (Bug#649769: obnam: "obnam --encrypt-with" fails with "can't query passphrase in batch mode")

2011-12-22 Thread Lars Wirzenius
On Tue, Dec 20, 2011 at 05:59:11AM +, Dafydd Harries wrote: > One additional annoyance is that when it crashes, it leaves the "root.lock" > file in place, which means I need to manually remove it before trying again. You can use the force-lock command with obnam to do that, but it's a bug that

Bug#649769: Info received (Bug#649769: obnam: "obnam --encrypt-with" fails with "can't query passphrase in batch mode")

2011-12-19 Thread Dafydd Harries
Now that #649767 is fixed, obnam always fails with this error for me, regardless of whether I'm ussing sshfs or an sftp:// URL. One additional annoyance is that when it crashes, it leaves the "root.lock" file in place, which means I need to manually remove it before trying again. I do have a GPG