On 2021-11-17, Vagrant Cascadian wrote:
> On 2021-11-17, Ludovic Courtès wrote:
>> Vagrant Cascadian skribis:
>>
>>> Ideally, "guix lint" would be run and issues fixed before applying
>>> patches ... !
...
>>> Is it worth adding an inexpensive check to etc/git/pre-push that also
>>> checks for
On 2021-11-17, Ludovic Courtès wrote:
> Vagrant Cascadian skribis:
>
>> Ideally, "guix lint" would be run and issues fixed before applying
>> patches ... !
>
> On the bright side, that there’s just a dozen of issues on 20K packages
> suggests it’s usually run. :-)
>
> I think we’re used to
Ludovic Courtès writes:
I hereby declare tomorrow, Thursday Nov. 18th, day of the
on-line
‘core-updates-frozen’ sprint!
The idea is that you join #guix on IRC, you try to build your
system or
profile from ‘core-updates-frozen’, and you report (and fix!)
any issues
you may have, in the
Hello Guix!
I hereby declare tomorrow, Thursday Nov. 18th, day of the on-line
‘core-updates-frozen’ sprint!
The idea is that you join #guix on IRC, you try to build your system or
profile from ‘core-updates-frozen’, and you report (and fix!) any issues
you may have, in the warmth of a collective
Hi,
On Wed, 17 Nov 2021 at 12:18, Ludovic Courtès wrote:
> I don’t think so; examples in the manual, ‘guix import’, etc. are
> already mostly consistent.
>From my point of view, an explicit recommendation is always better
than an implicit one. If it is already consistent and defacto
ordering,
Hi,
Katherine Cox-Buday skribis:
> In the manual, SS10.8.3, it says:
>
>> (usually, services that produce log files already take care of that)
>
> I found an excellent example in =hpcguix-web-service-type=. It looks like you
> can achieve this by extending the =rottlog-service-type=?
Yes
Vagrant Cascadian skribis:
> Ideally, "guix lint" would be run and issues fixed before applying
> patches ... !
On the bright side, that there’s just a dozen of issues on 20K packages
suggests it’s usually run. :-)
I think we’re used to running it for new packages but not when modifying
an
Hi,
zimoun skribis:
> On Sun, 07 Nov 2021 at 13:40, Tobias Geerinckx-Rice via Guix-patches via
> wrote:
>
>> So the de-facto ordering of common fields is something like:
>>
>> name
>> version
>> source
>> build-system
>> outputs ; a bit inconsistent, yes, and sometimes put after *inputs
>>
Hi,
Katherine Cox-Buday skribis:
> zimoun writes:
>
>> And obviously, it could be nice to have an automatic tool for formatting; >
>> something similar as etc/indent-code.el for ordering packages. ;-)
>
> And cleaning up unused imports too! Does such a thing exist for Guile in
> general?
Hi!
Vagrant Cascadian skribis:
> I've now pushed to core-updates-frozen:
>
>
> https://git.savannah.gnu.org/cgit/guix.git/commit/?h=core-updates-frozen=6cdf4e5bf230fdbe17e592c2ec74fb34dba70eb5
Thanks!
>> I'll also make a plea to create a "make dist" job on ci.guix.gnu.org
>> soon, to catch
Hi,
Thiago Jung Bauermann skribis:
> Em quinta-feira, 11 de novembro de 2021, às 15:23:37 -03, Maxim Cournoyer
> escreveu:
>> Hello Guix!
>>
>> I've finally merged the core-updates-frozen-batched-changes to
>> core-updates-frozen.
>
> Hooray!
>
>> One thing we could do in the meantime is to
Hi,
Jacob Hrbek skribis:
> Doesn't seem to work on `busybox sh` for me (I am not aware of better way to
> replicate POSIX environment on GNU Guix):
Note that you’re running /usr/bin/env, which has nothing to do with
Busybox.
> kreyren@leonid ~$ guix shell busybox -- busybox sh
> ...
> ~ $
Hi Samuel, Sergey, & all,
Samuel Thibault skribis:
> Ludovic Courtès, le mar. 09 nov. 2021 18:19:03 +0100, a ecrit:
>> Am I right that the fixes have not been applied yet in the upstream
>> repository?
>
> That's right. That's still waiting for the copyright assignment.
How about making it the
13 matches
Mail list logo
