Bug#516395: reprepro: removes Release.new when needed by gpgme with SignWith: set

2009-03-02 Thread Bernhard R. Link
* simon raven [090302 06:46]: > It would list 3 keys, one dead one that expired, my gmail one, and my > k.o one. apt and such were probably seeing the expired one and trying to > parse that, perhaps. I've tried to make the manpage more explicit. Do you think the following change is sufficient o

Bug#516395: reprepro: removes Release.new when needed by gpgme with SignWith: set

2009-02-28 Thread Bernhard R. Link
* Simon Raven [090228 00:43]: > BTW, seems that reprepro chokes on a GPG key if it has more than one > key in it. I have a gmail.com and a .org one in the key used to sign the > packages, > and I substituted the fingerprint ID for the email address I was using in the > distributions > file,

Bug#516395: reprepro: removes Release.new when needed by gpgme with SignWith: set

2009-02-27 Thread Simon Raven
hi, BTW, seems that reprepro chokes on a GPG key if it has more than one key in it. I have a gmail.com and a .org one in the key used to sign the packages, and I substituted the fingerprint ID for the email address I was using in the distributions file, and not only does reprepro NOT choke,

Bug#516395: reprepro: removes Release.new when needed by gpgme with SignWith: set

2009-02-20 Thread Simon Raven
Package: reprepro Version: 3.5.2-6 Severity: important hi, I'm seeing some odd behaviour. When I'm trying to run 'export', it fails miserably when SignWith: is set. Check this out: Exporting sid... exporting 'sid|main|powerpc'... replacing './dists/sid/main/binary-powerpc/Packages' (uncompre