Bug#837188: [buildd-tools-devel] Bug#837188: sbuild: Signing the dummy release file and SBUILD_BUILD_DEPENDS_{SECRET|PUBLIC}_KEY seem deprecated

2016-09-10 Thread Johannes Schauer
Hi Guilhem, Quoting Guilhem Moulin (2016-09-10 01:53:56) > Fair enough, I shouldn't have rushed this due to the train arriving at > destination, sorry :-P The actual bug I was trying to fix was #834898, but > you released 0.71.0-1 meanwhile. Since your fix is a lot more complicated > than

Bug#837188: [buildd-tools-devel] Bug#837188: sbuild: Signing the dummy release file and SBUILD_BUILD_DEPENDS_{SECRET|PUBLIC}_KEY seem deprecated

2016-09-09 Thread Guilhem Moulin
Control: severity -1 wishlist On Sat, 10 Sep 2016 at 00:19:02 +0200, Johannes Schauer wrote: > I do not see any bug here. You are just describing the current situation. > Please describe the problem you are experiencing. Fair enough, I shouldn't have rushed this due to the train arriving at

Bug#837188: [buildd-tools-devel] Bug#837188: sbuild: Signing the dummy release file and SBUILD_BUILD_DEPENDS_{SECRET|PUBLIC}_KEY seem deprecated

2016-09-09 Thread Johannes Schauer
Hi, Quoting Guilhem Moulin (2016-09-10 00:04:19) > #833547/#834898 have been fixed by adding a call to ‘gpgconf --kill > gpg-agent’. I was wondering whether access to private key material from > inside the chroot is required at all? Sbuild::ResolverBase reads > > # Sign the release file >

Bug#837188: sbuild: Signing the dummy release file and SBUILD_BUILD_DEPENDS_{SECRET|PUBLIC}_KEY seem deprecated

2016-09-09 Thread Guilhem Moulin
Package: sbuild Version: 0.71.0-2 Severity: normal Dear Maintainer, #833547/#834898 have been fixed by adding a call to ‘gpgconf --kill gpg-agent’. I was wondering whether access to private key material from inside the chroot is required at all? Sbuild::ResolverBase reads # Sign the