Hi Alex,
> I have read through the documentation and I believe I would be able to
> commit to the duties of being a mentor / co-mentor.
Wonderful!
> I would be happy to send more details of where I believe my relative
> strengths and weaknesses in this project would be. I couldn't see an
> app
Hello!
Before FOSDEM I decided to take another look at this.
I have really good news, gcc 4.7.4 ddc on x86_64 is now reproducible using
clang.
Code can be found at: https://github.com/Boskovits/guix/tree/gcc-ddc.
How could we go on with this?
Now it is very experimental, and not conforming to po
Hi!
Great to hear from you jao :)
On Sat 27 Jan 2018 17:41, "Jose A. Ortega Ruiz" writes:
> hmmm, i was investigating this. the cause geiser fails is that, in the
> process of looking for other things, it's not able to find
> `program-arities', exported by (system vm program). i am not sure w
Hi Mark,
thanks for the heads-up.
I've fixed it now. Sorry.
On Sun 28 Jan 2018 22:47, l...@gnu.org (Ludovic Courtès) writes:
> interned symbols are potentially not GC’d (though I think with Guile
> 2.2 and its weak sets they may be subject to GC.)
Symbols are collectable. They are collectable in 2.0 as well.
Depending on the context, it may be worth con
Hey,
Ricardo Wurmus writes:
> Hi Alex,
>
>> I have read through the documentation and I believe I would be able to
>> commit to the duties of being a mentor / co-mentor.
>
> Wonderful!
>
>> I would be happy to send more details of where I believe my relative
>> strengths and weaknesses in this pr
Hi,
as we've long talked and not really taken action on hardening builds
I've started working on an opt-in way as last discussed in
september 2016, modifying the gnu-build-system with a
#:hardening-flags keyword.
For my testing purposes I will use
> CFLAGS="-fPIE -fstack-protector-all -D_FORTIFY
Hi Danny,
dan...@scratchpost.org (Danny Milosavljevic) skribis:
> commit ebd6a6445fa7d3db64795840a607815abbd56880
> Author: Danny Milosavljevic
> Date: Mon Jan 29 13:23:07 2018 +0100
>
> hydra: Work around import problem.
>
> * build-aux/hydra/gnu-system.scm: qemu-jobs: Work aroun
Hi Ludo,
On Mon, 29 Jan 2018 14:53:03 +0100
l...@gnu.org (Ludovic Courtès) wrote:
> dan...@scratchpost.org (Danny Milosavljevic) skribis:
>
> > commit ebd6a6445fa7d3db64795840a607815abbd56880
> > Author: Danny Milosavljevic
> > Date: Mon Jan 29 13:23:07 2018 +0100
> >
> > hydra: Work arou
Hello!
Gábor Boskovits skribis:
> Before FOSDEM I decided to take another look at this.
> I have really good news, gcc 4.7.4 ddc on x86_64 is now reproducible using
> clang.
> Code can be found at: https://github.com/Boskovits/guix/tree/gcc-ddc.
Woow, quite an achievement!
To be clear, this pr
Hello Guix,
I've pushed a new 'kernel-updates' branch that includes the update to
linux-libre-4.15, and asked Hydra to build it. However, I haven't yet
pushed this to 'master' because of a complication.
At present, all of our kernel configurations have CONFIG_BLK_DEV_NVME=m
which results in an "
Ludovic Courtès writes:
> Did you choose 4.7 due to the fact that it’s the last C-only version?
At the reproducible builds summit we talked about “checkpoints” that we
want to achieve, i.e. points in the build graph that one can arrive at
one way or another (in this case via clang or via GCC) b
Hi Danny,
Danny Milosavljevic writes:
> On Mon, 29 Jan 2018 14:53:03 +0100
> l...@gnu.org (Ludovic Courtès) wrote:
>
>> dan...@scratchpost.org (Danny Milosavljevic) skribis:
>>
>> > commit ebd6a6445fa7d3db64795840a607815abbd56880
>> > Author: Danny Milosavljevic
>> > Date: Mon Jan 29 13:23:0
Dear,
Thank you for all your explanations.
Concerning the point about the 'lisppy' syntax.
Thank you Ricardo to point out the WISP initiative. Even if I watched
all the previous guile/guix FOSDEM videos, I have not realized that it
should be an elegant path to reduce the gap.
As Christopher Le
Hi,
On Mon, 29 Jan 2018, Mark H Weaver wrote:
> Hello Guix,
>
> I've pushed a new 'kernel-updates' branch that includes the update to
> linux-libre-4.15, and asked Hydra to build it. However, I haven't yet
> pushed this to 'master' because of a complication.
>
> At present, all of our kernel con
Heya,
Danny Milosavljevic skribis:
> First version of Cuirass status frontend is attached (renamed from
> "index.html").
>
> It displays, for a given project and jobset, a list of the latest finished
> builds
> and the latest queued builds. It also updates this list from time to time
> (ever
On Mon, Jan 29 2018, Andy Wingo wrote:
> Hi!
>
> Great to hear from you jao :)
likewise :)
> On Sat 27 Jan 2018 17:41, "Jose A. Ortega Ruiz" writes:
>
>> hmmm, i was investigating this. the cause geiser fails is that, in the
>> process of looking for other things, it's not able to find
>> `pro
Fis Trivial writes:
>> What do you mean by disable? You could invoke it at any time with a
>> clean Bash session. Also I would recommend to search for a Fedora's
>> Bash feature for installing programms if a command is missing and
>> disable/remove it.
>> Fedora's folks probably could help t
Is this something anyone can start using now? Like I can modify my config.scm
file somehow and start enjoying a hardened guix?
On Mon, Jan 29, 2018, at 4:44 AM, n...@n0.is wrote:
> Hi,
>
> as we've long talked and not really taken action on hardening builds
> I've started working on an opt-in w
Hi,
On Mon, 29 Jan 2018, Joshua Branson wrote:
> Is this something anyone can start using now? Like I can modify my
> config.scm file somehow and start enjoying a hardened guix?
Sorry to disappoint you, I'd like to have it usable also right
now :) But: no. This takes some time and testing. I'l
I'm keen to do some work on shepherd. Partially this is driven by
me using it to manage my user session and having it not always
work right, and partially this is driven by me grepping the code
for "FIXME" (which was slightly overwhelming). If anyone is keen
to chat about it on Friday, please f
Pjotr, that was excellently put!
I entirely agree that with the right educational materials you are going to see
have the possibility of appealing to other groups/cultures/biases.
Having a section for each of the 2**3 type of user might be the perfect
compromise.
Perhaps try to appeal to each
Hi Malcolm,
> I entirely agree that with the right educational materials you are
> going to see have the possibility of appealing to other
> groups/cultures/biases.
Yes, I think that does make sense.
> Having a section for each of the 2**3 type of user might be the
> perfect compromise.
>
> Per
Ricardo,
Sorry for the MisCaPITaliZAtion
Sorry if I lost the flow of the discussion. I entirely trust your
understanding of the focus of the discussion.
Cheers,
~malcolm_c...@stowers.org
> -Original Message-
> From: Ricardo Wurmus [mailto:rek...@elephly.net]
> Sent: Monday, Janu
* Problem
The exported environment variables can cause various problems in foreign
distribution(1)(2). And besides, The long list of environment variables(4)
injected into user's login shell makes the user's environment impure.
So, I believe that if I want to run guix safely on a foreign distribut
2018-01-29 22:14 GMT+01:00 Carlo Zancanaro :
> I'm keen to do some work on shepherd. Partially this is driven by me using
> it to manage my user session and having it not always work right, and
> partially this is driven by me grepping the code for "FIXME" (which was
> slightly overwhelming). If a
>
>> I will post the profile files in another thread latter if its helpful.
>
> It maybe be helpful. Thank you!
>
I don't think it's needed. Please check
https://lists.gnu.org/archive/html/guix-devel/2018-01/msg00507.html
Hi ng0,
> commit 57f9671d22bb4ee37962c31b9eed0ae50859398a
> Author: ng0
> Date: Wed Jan 17 22:42:55 2018 +
>
> gnu: Add badass.
[...]
> + (package
> +(name "badass")
> +(version (git-version "0.0" revision commit))
[...]
> +(synopsis "Hacking contribution graphs in git")
>
Hi Malcolm,
> Sorry for the MisCaPITaliZAtion
No WoRRieS! It seems to be very common :)
> Sorry if I lost the flow of the discussion. I entirely trust your
> understanding of the focus of the discussion.
No, your comments were spot on and very helpful. I’m just trying to
understand if your
On 01/29/2018 at 22:24 Cook writes:
> Ricardo,
>
> Sorry for the MisCaPITaliZAtion
Hey Malcolm, in sales and marketing we are thrilled if anybody remembers
our name, nevermind capitalization ;-)
> Sorry if I lost the flow of the discussion. I entirely trust your
> understanding of the focus of
zimoun writes:
> Currently, GWL is the strongest available about env/deps management.
> However, Lisp is not mainstream, especially with Bio* and few
> pieces/workflow are already available.
Well, things can change. Did you know that Ross Ihaka of GNU R fame has
been thinking out loud about a
George myglc2 Clemmer writes:
> Your comments are, IMO, right on
> the money WRT making the case for Guix/GuixSD.
I agree.
> Ricardo, do you have a suggestion of where/how to relocate this
> discussion?
Let’s keep it right here :) I only meant to get additional input on the
original question
On Mon, Jan 29, 2018 at 06:09:16PM -0500, Mark H Weaver wrote:
> Hi ng0,
>
> > commit 57f9671d22bb4ee37962c31b9eed0ae50859398a
> > Author: ng0
> > Date: Wed Jan 17 22:42:55 2018 +
> >
> > gnu: Add badass.
> [...]
> > + (package
> > +(name "badass")
> > +(version (git-version "0
ng0 writes:
> 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
On Mon, Jan 29, 2018 at 11:20:17PM +0100, Ricardo Wurmus wrote:
> I like these testimonial style descriptions, and I think it makes sense
> to add separate sections for different archetypical users. (We already
> have a related section entitled “GuixSD and GNU Guix in your field”,
> which I found
On Mon, Jan 29, 2018 at 11:20:17PM +0100, Ricardo Wurmus wrote:
> However, I think that this is tangential to the question of whether to
> move the GuixSD description and intro to a separate page. If we added
> those sections they’d be only about Guix, not about GuixSD, no?
I am convinced that Gu
36 matches
Mail list logo
