On Fri, Jan 22, 2016 at 05:13:02AM +0100, Pjotr Prins wrote:
> On Thu, Jan 21, 2016 at 09:55:32PM +0100, Ludovic Courtès wrote:
> > > I wonder how this could be implemented, any ideas?
> >
> > Roughly, we could generate a Scheme file containing the list of phases
> > (the generated build script co
On Thu, Jan 21, 2016 at 09:55:32PM +0100, Ludovic Courtès wrote:
> > I wonder how this could be implemented, any ideas?
>
> Roughly, we could generate a Scheme file containing the list of phases
> (the generated build script contains them, but it immediately passes
> them to ‘gnu-build’ or similar
Ludovic Courtès writes:
> Roel Janssen skribis:
>
>> Ludovic Courtès writes:
>
> [...]
>
>>> Good! I applied the patch and deployed the new web page:
>>>
>>> https://www.gnu.org/software/guix/packages/
>>>
>>> However, it’s still failing:
>>>
>>> 17:00:49.802 Cross-Origin Request Blocked: T
To ignore specifics, there are a lot of current methods people are using
to debug, as well as a few proposed methods.
Regardless, maybe it would be nice to copy useful techniques into the
manual. It seems like good information/history to capture.
- Chris
On Thu, Jan 21, 2016 at 04:08:24PM -0600, Eric Bavier wrote:
> On 2016-01-21 15:25, l...@gnu.org wrote:
>
> My only issue with the attached patch is that the commit identifier in the
> example is not 7 digits (characters?) as recommended.
Maybe it'd be better to just round it up to 8 and keep the
On Thu, Jan 21, 2016 at 09:58:38PM +0100, Ludovic Courtès wrote:
> Jookia <166...@gmail.com> skribis:
>
> > This could be good enough for now but again this doesn't work with this like
> > builds that don't fail. My concrete example is wanting to patch software
> > but not
> > knowing how to get
Ludovic Courtès writes:
> "Thompson, David" skribis:
>
>> On Wed, Jan 20, 2016 at 5:13 PM, Ludovic Courtès wrote:
>>
>>> To me, the question is more about choosing between writing configuration
>>> file bindings and exposing upstream’s configuration file syntax, as was
>>> discussed when Andy po
On 2016-01-21 15:25, l...@gnu.org wrote:
Ricardo Wurmus skribis:
Ben Woodcroft writes:
On 12/01/16 19:26, Ludovic Courtès wrote:
[...]
So, a Git snapshot’s version number could be:
2.0.11-3.deadbeef
^^^
||`— upstream commit ID
||
|`—— 3rd
* guix/import/pypi.scm (latest-wheel-release): New function.
---
guix/import/pypi.scm | 112 ++-
1 file changed, 85 insertions(+), 27 deletions(-)
diff --git a/guix/import/pypi.scm b/guix/import/pypi.scm
index d54bb9f..2614ab5 100644
--- a/guix/impo
Ludovic Courtès writes:
> +
> +It is a good idea to strip commit identifiers to, say, 7 digits so that
> +they do not become aesthetically disturbing (assuming aesthetics have a
> +role to play here.) It is best to use the full commit identifiers in
> +@code{origin}s, though, to avoid ambiguiti
Leo Famulari skribis:
> * gnu/packages/admin.scm (iftop): New variable.
> +(description "Iftop does for network usage what top(1) does for CPU
> usage.
I would s/top(1)/@command{top}/.
Otherwise LGTM, thanks!
Ludo’.
"Thompson, David" skribis:
> On Wed, Jan 20, 2016 at 5:13 PM, Ludovic Courtès wrote:
>
>> To me, the question is more about choosing between writing configuration
>> file bindings and exposing upstream’s configuration file syntax, as was
>> discussed when Andy posted the Dovecot service. (To wh
Ricardo Wurmus skribis:
> Ben Woodcroft writes:
>
>> On 12/01/16 19:26, Ludovic Courtès wrote:
[...]
>>> So, a Git snapshot’s version number could be:
>>>
>>>2.0.11-3.deadbeef
>>> ^^^
>>> ||`— upstream commit ID
>>> ||
>>> |`—— 3rd Guix package r
On Thu, Jan 21, 2016 at 09:48:58PM +0100, Ludovic Courtès wrote:
> Could be. OTOH, there’s a risk of Doxygen being effectively “broken by
> default” if, as I presume, many programs expect it to be able to
> generate PNGs for class diagrams.
Okay. As propagated inputs are a somewhat dirty affair,
Leo Famulari skribis:
> On Thu, Jan 21, 2016 at 10:40:41AM +0100, Ricardo Wurmus wrote:
>>
>> Leo Famulari writes:
>>
>> > That sounds good to me. There was some discussion of how much of the
>> > hash to keep here:
>> > http://lists.gnu.org/archive/html/guix-devel/2015-12/msg00136.html
>> >
>
Jookia <166...@gmail.com> skribis:
> This could be good enough for now but again this doesn't work with this like
> builds that don't fail. My concrete example is wanting to patch software but
> not
> knowing how to get to the pre-patch state so I can then work from that in
> testing which patche
Jookia <166...@gmail.com> skribis:
> On Wed, Jan 20, 2016 at 11:26:14PM +0100, Ludovic Courtès wrote:
>> Yes, I agree that this would be nice.
>
> I wonder how this could be implemented, any ideas?
Vague ideas. :-)
Roughly, we could generate a Scheme file containing the list of phases
(the gene
Andreas Enge skribis:
> On Wed, Jan 20, 2016 at 11:15:04PM +0100, Ludovic Courtès wrote:
>> I guess Graphviz was propagated so that ‘doxygen’ can produce class
>> diagrams out-of-the-box (it probably looks for ‘dot’ in $PATH.) So I
>> would probably keep it propagated.
>
> I do not remember anym
On Wed, Jan 20, 2016 at 11:15:04PM +0100, Ludovic Courtès wrote:
> I guess Graphviz was propagated so that ‘doxygen’ can produce class
> diagrams out-of-the-box (it probably looks for ‘dot’ in $PATH.) So I
> would probably keep it propagated.
I do not remember anymore, although it was me to do it
Hello,
and sorry for taking my time in replying around the Christmas holidays.
On Wed, Dec 30, 2015 at 08:45:04PM +0100, Andi Kleen wrote:
> I guess he wants to build on that platform.
Indeed. However, my situation is a bit special: I am doing QA work on the Guix
GNU/Linux distribution and notic
On Thu, Jan 21, 2016 at 10:40:41AM +0100, Ricardo Wurmus wrote:
>
> Leo Famulari writes:
>
> > That sounds good to me. There was some discussion of how much of the
> > hash to keep here:
> > http://lists.gnu.org/archive/html/guix-devel/2015-12/msg00136.html
> >
> > I like this method that I've s
>From 546a8651db1c420fee841a2da6474593e4c9aa93 Mon Sep 17 00:00:00 2001
From: Ricardo Wurmus
Date: Thu, 21 Jan 2016 16:03:26 +0100
Subject: [PATCH] gnu: Add Augeas.
* gnu/packages/augeas.scm: New file.
* gnu-system.am (GNU_SYSTEM_MODULES): Add it.
---
gnu-system.am | 1 +
gnu/packages
Mathieu Lirzin writes:
> Ricardo Wurmus writes:
>
>> Okay. Attached are three new patches. I thought I should better split
>> this up into separate commits for clarity.
>
> Splitting thoses changes is a good idea. Thanks for taking the time to
> do it.
>
>>>From b276ca4c3940663137e4449144b22
On Wed, Jan 20, 2016 at 5:13 PM, Ludovic Courtès wrote:
> To me, the question is more about choosing between writing configuration
> file bindings and exposing upstream’s configuration file syntax, as was
> discussed when Andy posted the Dovecot service. (To which I don’t have
> a better answer
Ricardo Wurmus writes:
> Okay. Attached are three new patches. I thought I should better split
> this up into separate commits for clarity.
Splitting thoses changes is a good idea. Thanks for taking the time to
do it.
>>From b276ca4c3940663137e4449144b2256f03e47d27 Mon Sep 17 00:00:00 2001
>
Mathieu Lirzin writes:
> Ricardo Wurmus writes:
>
>> I agree, this looks nicer. Would you like to push this change? There
>> isn’t much left of my original patch ;)
>
> IIUC the main feature of this patch is adding the “nsupdate” thing
> (which should be described in the commit log by the way
Roel Janssen skribis:
> Ludovic Courtès writes:
[...]
>> Good! I applied the patch and deployed the new web page:
>>
>> https://www.gnu.org/software/guix/packages/
>>
>> However, it’s still failing:
>>
>> 17:00:49.802 Cross-Origin Request Blocked: The Same Origin Policy
>> disallows readi
Ben Woodcroft writes:
> On 12/01/16 19:26, Ludovic Courtès wrote:
>> Ricardo Wurmus skribis:
>>
>>> Would it make sense to separate our version identifier from the actual
>>> release version with a different character than “.”? Or should this be
>>> discussed elsewhere as it hasn’t anything to
Leo Famulari writes:
> That sounds good to me. There was some discussion of how much of the
> hash to keep here:
> http://lists.gnu.org/archive/html/guix-devel/2015-12/msg00136.html
>
> I like this method that I've seen in some of the packages, because it
> keeps the version tidy while preservin
I've been holding on to these for a bit, waiting to integrate them before
submitting them.
cmocka: This is supposed to be used by mpv for running the tests, but the
tests fail. Since mpv works I wasn't super motivated to try to get it to
work, but I'm guessing other programs might also use it.
py
Ben Woodcroft skribis:
> Can I ask a question though, does the bug system track the contents of
> commit messages on master or did the bug need to be closed manually (I
> did this already mind)?
Unfortunately there’s no connection between the two, so the bug indeed
has to be closed manually.
Lu
31 matches
Mail list logo
