On Thu, Dec 29, 2016 at 01:44:59AM -0500, Leo Famulari wrote:
> Here's a pre-push Git hook that should prevent unsigned commits from
> being pushed to any remote. I'd like to improve it to be applied
> selectively per-remote.
The hook will only apply when pushing to Savannah if you put this test
a
On Thu, Dec 29, 2016 at 07:08:18AM +0100, John Darrington wrote:
> How did these commits get into the repository? Our repository is
> configured to reject unsigned commits. Can it be that it doesn't
> actually check that the signature matches? !!!
Here's a pre-push Git hook that should prevent
On Thu, Dec 29, 2016 at 07:08:18AM +0100, John Darrington wrote:
> On Thu, Dec 29, 2016 at 03:49:51AM +0100, Tobias Geerinckx-Rice wrote:
> Leo,
>
> On 29/12/16 03:10, Leo Famulari wrote:
> > gpg: BAD signature from "Tobias Geerinckx-Rice "
>
> Oh dear.
>
>
On Thu, Dec 29, 2016 at 03:49:51AM +0100, Tobias Geerinckx-Rice wrote:
Leo,
On 29/12/16 03:10, Leo Famulari wrote:
> gpg: BAD signature from "Tobias Geerinckx-Rice "
Oh dear.
> Does anyone else get the same result? Any ideas?
I do, so it's a rea
On Wed, Dec 21, 2016 at 11:47:08AM +, ng0 wrote:
> [PATCH 01/11] gnu: Add python-flask-wtf.
>
> > Danny Milosavljevic:
> > Subject: Re: [PATCH 01/11] gnu: Add python-flask-wtf.
> >
> > Date: Wed, 21 Dec 2016 00:10:39 +0100
Leo,
On 29/12/16 03:47, Leo Famulari wrote:
> I'm also unable to verify the signature of two more commits, as below.
Signing seems to fail both seldom and pseudo-randomly. Oh, and
silently[1]. My favourite kind of bug.
I'm guessing this is what happens:
$
$ git commit, am or cherry-pick &&
Leo,
On 29/12/16 03:10, Leo Famulari wrote:
> gpg: BAD signature from "Tobias Geerinckx-Rice "
Oh dear.
> Does anyone else get the same result? Any ideas?
I do, so it's a real® corrupted signature.
Looking back, it turns out that this isn't the first time this has
happened: another commit of m
On Wed, Dec 28, 2016 at 09:10:15PM -0500, Leo Famulari wrote:
> I see this in the log:
>
> $ git log --show-signature 6a34f4ccc8a5d4a48e25ad3c9c512f8634928b91
> commit 6a34f4ccc8a5d4a48e25ad3c9c512f8634928b91
> gpg: Signature made Wed 28 Dec 2016 08:38:21 PM EST
> gpg:using RSA key
I see this in the log:
$ git log --show-signature 6a34f4ccc8a5d4a48e25ad3c9c512f8634928b91
commit 6a34f4ccc8a5d4a48e25ad3c9c512f8634928b91
gpg: Signature made Wed 28 Dec 2016 08:38:21 PM EST
gpg:using RSA key 91CCDB9B48541B99
gpg: BAD signature from "Tobias Geerinckx-Rice " [unknow
Kei Kebreau writes:
> Kei Kebreau writes:
>
>> Leo Famulari writes:
>>
>>> On Sat, Dec 24, 2016 at 02:23:43PM -0500, Kei Kebreau wrote:
Leo Famulari writes:
> On Thu, Dec 22, 2016 at 02:20:37PM -0500, Kei Kebreau wrote:
>> Subject: [PATCH] gnu: chicken: Fix CVE-2016-{6830,6831}.
Django is failing its test suite on the staging branch:
https://hydra.gnu.org/job/gnu/staging/python-django-1.10.3.x86_64-linux
https://hydra.gnu.org/job/gnu/staging/python-django-1.10.3.i686-linux
I can reproduce this on my own machine, but I'm not sure what the
problem is.
Does anyone have any
* gnu/packages/rust.scm (rustc): Update to 1.14.0.
%rust-bootstrap-binaries: Update to 1.13.0.
---
gnu/packages/rust.scm | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/rust.scm b/gnu/packages/rust.scm
index acc555e75..8aa867317 100644
--- a/gnu/packages/rus
[PATCH] gnu: rustc: Update to 1.14.0.
This updates rust to 1.14.0 ... Build succesfully, I'll see wether building
crate libc now succeeds.
I might have found the new repository of our recipe for abbaye, and I
have contacted the developers of abbaye (David Lara, also known as nevat) and he
told me that the repository I found is the successor of the one in
Google Code.
Now, what is left to do is test the noew source files to see if the
I posted about it in my blog[1]: d4n1.org/guixsd.html
[1] Developed with Haunt (thanks David) :)
---
Daniel Pimentel (d4n1)
On 2016-12-27 21:50, Daniel Pimentel wrote:
Guixs,
I'm trying use StumpWM in my config.scm but there's code for module:
guix system: error: failed to load '/etc/config.
Hi, here is a one level list of (almost) all packages I am
working on in the next few weeks. If you see a package you want
to work on or already work on, plan to work on, or whatever "what
if" case, please respond or post to the list. I'm more than happy
for any work and find duplicate work sad. I
Hi,
I'm trying Rust out for a bit and for that I added some Crates. (using David's
v2 patches as a base)
Right now I'm stuck at rust-c-vec which I tried to add myself. I get:
starting phase `unpack'
c_vec-1.1.0/.travis.yml
c_vec-1.1.0/Cargo.toml
c_vec-1.1.0/LICENSE-APACHE
c_vec-1.1.0/LICENSE-MI
Hi Ben,
reading the comments from https://github.com/ewels/MultiQC/issues/376
it seems that in the upcoming release they will solve the problem.
Are we going to wait for the next v. 1.0 or include it now and update later
?
--
Ra
On Mon, Dec 26, 2016 at 1:18 PM Ben Woodcroft wrote:
> Hi Raoul,
>
Ricardo Wurmus writes:
> Chris Marusich writes:
>
>> * gnu/packages/libusb.scm (libmtp): Set udev group to "audio".
>> ---
>
> I just checked how it’s done on Debian and Fedora. Neither pass this
> configuration flag. On a Fedora system I can access I see that the udev
> rules that come with l
> Of course I meant Cargo.lock, not Cargo.toml ... so I know what I
> have to search for, and this makes it a bit easier than the
> previous search.
See cargo workspaces:
https://github.com/rust-lang/libc/blob/master/Cargo.toml
https://github.com/rust-lang/rfcs/blob/master/text/1525-cargo-workspac
Hi Ricardo,
there was an issue with the r-shiny patch, the license was wrong. So this
is the new set of patches.
On Tue, Dec 27, 2016 at 10:25 PM Ra wrote:
> Dear Ricardo,
> I try to satisfy all the requirements. What do you think ?
> In attachment the patches.
>
> Shiny now is in web.scm
>
>
ng0 writes:
> David Craven writes:
>
>>> We run (or this is the default) cargo with `--bin`, which is
>>> necessary for everything which needs to be compiled and features
>>> a Cargo.toml.
>>
>> All crates have a Cargo.toml file. The interesting crates are the ones with
>> a Cargo.lock file.
>>
David Craven writes:
>> We run (or this is the default) cargo with `--bin`, which is
>> necessary for everything which needs to be compiled and features
>> a Cargo.toml.
>
> All crates have a Cargo.toml file. The interesting crates are the ones with
> a Cargo.lock file.
>
>> To "build" libraries,
On Tue, Dec 27, 2016 at 11:13:05PM -0500, Leo Famulari wrote:
On Tue, Dec 27, 2016 at 06:56:44PM -0500, Leo Famulari wrote:
> On Fri, Dec 23, 2016 at 12:23:39AM -0500, Leo Famulari wrote:
> > The last staging branch was merged into the master branch on December
> > 11.
> >
24 matches
Mail list logo
