Ludo,
As you observed, the majority of my problems were due to building guix on a
network mount having some odd nfs4_facl setting that was making all the files
be executable, which is explicitly tested against in many tests, and thus they
were all failing.
Moving off that file system, and buil
Alex Kost skribis:
> So I'm attaching 2 patches: for lines with leading parenthesis and for
> fixing multiple "typos" (in a general meaning). Changing
> synopses/descriptions according to "guix lint" (so no problems with
> 'gnu-description') and reorganizing lists are not included.
OK. These t
Alex Kost skribis:
> Ludovic Courtès (2015-07-16 22:08 +0300) wrote:
[...]
>> The problem is that this rule sometimes conflicts with the
>> ‘gnu-description’ checker (aka. ‘make sync-descriptions’), which checks
>> upstream GNU descriptions.
>>
>> When such conflicts happen, we should give prec
Mathieu Lirzin skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> What are your concerns and what would you prefer? (I was left with the
>> impression that there was a rough consensus in the other thread, but
>> surely there’s a bias.)
>>
>> In Emacs it’s quite easily typed (C-x 8 RET etc.),
Alex Kost writes:
> So I'm attaching 2 patches: for lines with leading parenthesis and for
> fixing multiple "typos" (in a general meaning). Changing
> synopses/descriptions according to "guix lint" (so no problems with
> 'gnu-description') and reorganizing lists are not included.
These 2 patch
Can this patch go in? I sent it 4 days ago. It allows building
extensions for Ruby gems, by passing in flags to gem, as shown in the
Nokogiri patch. Even without accepting Nokogiri, this is valuable for
building and installing gems.
Pj.
On Mon, Jul 13, 2015 at 03:44:51PM +0200, Pjotr Prins wrote
Ludovic Courtès writes:
> Christopher Allan Webber skribis:
>
>> From 32fe80103c1cef93f1608d5c09e4edf7cd005a5e Mon Sep 17 00:00:00 2001
>> From: Christopher Allan Webber
>> Date: Fri, 10 Jul 2015 15:49:07 -0500
>> Subject: [PATCH 1/3] gnu: Add python-feedgenerator
>>
>> * gnu/packages/python.scm
Hi!
l...@gnu.org (Ludovic Courtès) skribis:
> I think we should release 0.8.3 for mid to end July.
I would like to target Wednesday, 22nd, which means the release must be
tagged on Tuesday. That sounds doable.
Mark: will you be around to produce the armhf tarball?
By then we’ll have to merge
Hello!
When switching from 4.0.5 to 4.1.2, I noticed that my ath9k-based
ThinkPenguin WiFi dongle would no longer work (“Resource unavailable”
when running ‘iwlist xxx scan’, etc.)
For a while, I suspected a firmware miscompilation but then noticed that
using the previous, known-good firmware did
I move 'itstool' to 'native-inputs', and pushed.
Thanks!
Ludovic Courtès (2015-07-16 22:08 +0300) wrote:
> Alex Kost skribis:
>
>> Eric Bavier (2015-07-16 12:40 +0300) wrote:
>>
>>> On Thu, 16 Jul 2015 14:17:22 +0300
>>> Alex Kost wrote:
>>>
--- a/gnu/packages/base.scm
+++ b/gnu/packages/base.scm
@@ -58,7 +58,7 @@
(sha
Ludovic Courtès (2015-07-16 18:50 +0300) wrote:
> Mathieu Lirzin skribis:
>
>> For the typos and polishing fixes, I would prefer that the commits were
>> done in a module related way. So IMO It would be better to have one
>> commit per-file.
>
> I think one per file would be overkill (and not rea
Hi,
'git rebase' kept failing after a pull, so I squashed my 8 commits
into one. That got the rebase to work. Sorry for the giant patch...
Ludo: the tests for syscalls.scm are included in the patch as well.
Thank you,
Rohan
On 16 July 2015 at 21:08, Ludovic Courtès wrote:
> Rohan Prinja skrib
13 matches
Mail list logo
