The reason for the cascading errors is bash-minimal.
Trying to build `./pre-inst-env guix build bash-minimal'
on core-updates ends up with :
The following derivation will be built:
/gnu/store/1r0fpfcik796g2b5v9ns163sgan1rkmz-bash-minimal-4.4.12.drv
@ build-started
/gnu/store/1r0fpfcik796g2b5v9
Le Fri, 28 Apr 2017 11:46:43 -0500,
Christopher Allan Webber a écrit :
> Andy Wingo writes:
>
> > On Fri 28 Apr 2017 14:42, Hartmut Goebel
> > writes:
> >
> >> Am 28.04.2017 um 14:05 schrieb Andy Wingo:
> >>> 5.15 Invoking ‘guix potluck’
> >>
> >> Please think about an other name for t
Andy Wingo writes:
> On Fri 28 Apr 2017 14:42, Hartmut Goebel
> writes:
>
>> Am 28.04.2017 um 14:05 schrieb Andy Wingo:
>>> 5.15 Invoking ‘guix potluck’
>>
>> Please think about an other name for this command. "potlouk" may be
>> common to native speakers but I never heard this word. Thanks.
Hi,
> Agreed. A ‘guix user’ tool (or similar) could talk to the user’s
> Shepherd instance to upgrade user services like
> ‘upgrade-shepherd-services’ does in (guix scripts system).
With the attached patch, it is possibe to use (gnu services herd) to
interact with a user shepherd instance.
For
Leo Famulari transcribed 0.7K bytes:
> On Wed, Jan 04, 2017 at 06:50:14PM +, ng0 wrote:
> > Do I read this correctly that they include some kind of
> > anti-military license in there? I mean I am very much welcoming
> > such an exclusion but with all the past discussions I had it lead
> > to th
ng0 writes:
> Recently, with the last release, neomutt introduced lua-scripting
> for neomutt. It's not enabled by default because it's in a phase
> where neomutt wants people to enable it, test it, and receive feedback
> to improve it.
[…]
> Should we just wait until neomutt enables lua-scripti
Hi :)
On Fri 28 Apr 2017 15:41, Katherine Cox-Buday
writes:
> Andy Wingo writes:
>
>> With that I think I'd like to move to a "use" phase where I just sit
>> back and see how people use the thing :) WDYT?
>
> I am very excited about this functionality for all of the reasons you
> enumerated.
I am personally happy with potluck, however collab has a similar group feeling
to it.
-H
Sent from ProtonMail mobile Original Message On 28 Apr 2017,
14:46, Katherine Cox-Buday wrote: I don't hold any strong opinions on the name,
but in the interest of ideas: - guix quorum -
I don't hold any strong opinions on the name, but in the interest of
ideas:
- guix quorum
- guix collab
- guix confer
- guix conjoin
That's all I have for now :)
--
Katherine
Andy Wingo writes:
> With that I think I'd like to move to a "use" phase where I just sit
> back and see how people use the thing :) WDYT?
I am very excited about this functionality for all of the reasons you
enumerated. I don't have any time at the moment, but I was (and still
am) interested i
In the UK,
We do potluck dinners, I also had one in Canada.
Though I agree it's quite colloquial term, does one have to understand the
reference to understand how to use the command on the CLI?
-H
Sent from ProtonMail mobile
Original Message
On 28 Apr 2017, 13:58, Jan Nieuwen
Hartmut Goebel writes:
> Please think about an other name for this command. "potlouk" may be
> common to native speakers but I never heard this word. Thanks.
Potluck dish --even though it's English--- is a common word even in the
Netherlands...possibly this is a European thing.
I like the name,
On Fri 28 Apr 2017 14:42, Hartmut Goebel writes:
> Am 28.04.2017 um 14:05 schrieb Andy Wingo:
>> 5.15 Invoking ‘guix potluck’
>
> Please think about an other name for this command. "potlouk" may be
> common to native speakers but I never heard this word. Thanks.
I thought about many things :)
Hi,
Am 28.04.2017 um 14:05 schrieb Andy Wingo:
> 5.15 Invoking ‘guix potluck’
Please think about an other name for this command. "potlouk" may be
common to native speakers but I never heard this word. Thanks.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goe...@crazy-compilers.com
On Thu, 27 Apr 2017 20:47:54 -0500
Eric Bavier wrote:
> > > > +(inputs
> > > > + `(("qt" ,qt)))
> > >
> > > Does this package need all of qt, or could we use the component
> > > packages instead?
> >
> > I don't know. I'll do some experiments and see.
>
> OK, great.
Fixed!
Hi!
To recall, "guix potluck" is a packaging facility that is a decoupled
from mainline Guix development. The latest patches are in wip-potluck,
and a recent copy of the patches is here:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26645
Here is part of the documentation in that branch:
5
ng0 transcribed 0.7K bytes:
> Recently, with the last release, neomutt introduced lua-scripting
> for neomutt. It's not enabled by default because it's in a phase
> where neomutt wants people to enable it, test it, and receive feedback
> to improve it.
And because not everyone is subscribed everyw
Recently, with the last release, neomutt introduced lua-scripting
for neomutt. It's not enabled by default because it's in a phase
where neomutt wants people to enable it, test it, and receive feedback
to improve it.
As the announcement of it points out, this can be used to write the
neomutt config
Hello!
The GNU Hackers Meeting is looking for presentations for this years
programme!
Find out all you need to know, and/or submit your proposal at
https://www.gnu.org/ghm/programme.html .
The deadline for submissions is 4 June 2017.
The meeting will take place 24 - 27 August in Germany. The m
Ricardo Wurmus writes:
> Roel Janssen writes:
>
>>> I’d be happy if you could take care of the mass update. I should note
>>> that sometimes new inputs are required. To find them I usually run the
>>> update in a separate branch where I’ve applied changes to import anew
>>> and compare with th
Small fix below
On Thu, 27 Apr 2017 22:00:09 +0200
Danny Milosavljevic wrote:
> Something like this (totally untested):
>
> diff --git a/gnu/build/file-systems.scm b/gnu/build/file-systems.scm
> index 0cb84b8aa..be512d59c 100644
> --- a/gnu/build/file-systems.scm
> +++ b/gnu/build/file-systems.
Arne Babenhauserheide writes:
> Wow! Congratulation on full bootstrapping of mes!
Thanks, Arne!
> So we can now build mes.c with mescc driven by Guile and then use mes to
> run mescc again to build mes.c?
Yes, that's correcct. mes.c can be compiled with either gcc
make out/mes
or with [3
Jan Nieuwenhuizen writes:
> I am pleased to announce the release of Mes 0.5, representing 249
> commits over 4 months. Mes is now self-hosting, or rather it features
> a mutual self-hosting Scheme interpreter and C compiler: mes.c and
> mescc; a Nyacc-based C compiler backend that also works sep
23 matches
Mail list logo
