On Tue 2016-11-08 01:58:42 -0600, Cyril Brulebois wrote:
> Daniel Kahn Gillmor (2016-11-07):
>> On Thu 2016-11-03 06:56:21 -0600, Luca Falavigna wrote:
>> > 2016-11-03 13:41 GMT+01:00 Thomas Goirand :
>> >> dkg, you had the intention to upload gnupg 2.1 to
Hi,
Daniel Kahn Gillmor (2016-11-07):
> On Thu 2016-11-03 06:56:21 -0600, Luca Falavigna wrote:
> > 2016-11-03 13:41 GMT+01:00 Thomas Goirand :
> >> dkg, you had the intention to upload gnupg 2.1 to backports. Is there
> >> anything that's holding it?
>
On Thu 2016-11-03 06:56:21 -0600, Luca Falavigna wrote:
> 2016-11-03 13:41 GMT+01:00 Thomas Goirand :
>> dkg, you had the intention to upload gnupg 2.1 to backports. Is there
>> anything that's holding it?
>>
>> Lucas, could you upload a version of sbuild to BPO without this hard
2016-11-03 13:41 GMT+01:00 Thomas Goirand :
> Indeed, sbuild in backports is not not installable.
Indeed, I normally test all my packages, and I did this time too...
but I didn't realize I already had gnupg2 installed on stable (private
copy) and I trusted the last line of
On 11/03/2016 11:10 AM, Wouter Verhelst wrote:
> The following packages have unmet dependencies:
> sbuild : Depends: libsbuild-perl (= 0.72.0-2~bpo8+1) but 0.70.0-1~bpo8+1 is
> to be installed
> E: Unable to correct problems, you have held broken packages.
> root@debian-sbuild:~# apt install -t
On Fri, Oct 14, 2016 at 07:36:56AM +0200, Johannes Schauer wrote:
> Hi,
>
> Quoting Daniel Kahn Gillmor (2016-10-13 00:31:28)
> > > On Wed, Oct 12, 2016 at 11:42:15PM +0200, Thomas Goirand wrote:
> > >> gpg: Invalid option "--pinentry-mode"
> >
> > … it sounds like sbuild should at least have
Hi,
2016-10-14 7:36 GMT+02:00 Johannes Schauer :
> don't know if our current sbuild backporter Luca (in CC) would be willing to
> write such a patch, especially considering that
>
> - it is a feature of sbuild since version 0.67.0 (I corrected the wiki page
>accordingly) to
On Fri 2016-10-14 01:36:56 -0400, Johannes Schauer wrote:
> - it is a feature of sbuild since version 0.67.0 (I corrected the wiki page
>accordingly) to *not* require signing of the internal dummy repository (and
>thus you don't need to run sbuild-update --keygen anymore) and that
Hi,
Quoting Daniel Kahn Gillmor (2016-10-13 00:31:28)
> > On Wed, Oct 12, 2016 at 11:42:15PM +0200, Thomas Goirand wrote:
> >> gpg: Invalid option "--pinentry-mode"
>
> … it sounds like sbuild should at least have declared a versioned
> dependency on gnupg (>= 2.1), when --pinentry-mode was
On 10/13/2016 12:58 PM, Johannes Schauer wrote:
> Hi,
>
> Quoting Thomas Goirand (2016-10-12 23:42:15)
>> Dear backport maintainer,
>>
>> Since the upload of sbuild 0.71.0-2~bpo8+1 to stable backport, running
>> sbuild-update --keygen leads to this error message:
>>
>> gpg: Invalid option
Hi,
Quoting Thomas Goirand (2016-10-12 23:42:15)
> Dear backport maintainer,
>
> Since the upload of sbuild 0.71.0-2~bpo8+1 to stable backport, running
> sbuild-update --keygen leads to this error message:
>
> gpg: Invalid option "--pinentry-mode"
>
> Indeed, it looks like --pinentry-mode
11 matches
Mail list logo