On 10/17/2014 10:56 AM, Sylvestre Ledru wrote:
> On 17/10/2014 18:55, Jim Garrison wrote:
>> On 10/17/2014 12:49 AM, Gilles Filippini wrote:
>>> Could you please gite a try at the not yet uploaded release
>>> 1.8.13+docs-15 I've just pushed into the git repo (branch master)?
>>> Thanks in advance, _g.
>> Thanks so much for looking into this and integrating a patch into the
>> git repository.
>> Is there a set of step-by-step instructions somewhere for trying it?
>> After reading https://wiki.debian.org/PackagingWithGit I tried running
>> git-buildpackage from the cloned repository, but it fails eventually
>> because I don't have your GPG secret key on my machine.
>> Now signing changes and any dsc files...
>> signfile hdf5_1.8.13+docs-15.dsc Gilles Filippini <p...@debian.org>
>> gpg: skipped "Gilles Filippini <p...@debian.org>": secret key not
>> gpg: /tmp/debsign.DpcZISY5/hdf5_1.8.13+docs-15.dsc: clearsign failed:
>> secret key not available
>> debsign: gpg error occurred! Aborting....
>> debuild: fatal error at line 1283:
>> running debsign failed
>> gbp:error: 'debuild -i -I' failed: it exited with 29
> The packages are still generated.
> You can ignore this error! You will still find the deb (../*deb)
Thanks, I had looked recursively in each subdirectory but had not
thought to look in the parent directory! :)
At this point every one of my failing tests has been running for 30
minutes (much longer than before), and not one of them has failed. So,
I think it is very likely that the bug has been fixed.
Pkg-grass-devel mailing list