Re: RISC-V is giving away developer boards

On Sat, May 01, 2021 at 06:14:14AM +0200, Bengt Richter wrote: > Could some riscv-model-version.scm be written to use qemu to create > an exact virtual metal RISC-V board (of the kind being sampled, for starters) > for use on our laptops and PCs? > > I think that might get more people involved,

GNU Guix 1.3.0rc1 available for testing!

Hello Guix! A first RC for the upcoming 1.3.0 release is now available for testing: source: https://alpha.gnu.org/gnu/guix/guix-1.3.0rc1.tar.gz binary tarball (to install on a “foreign distro”): https://alpha.gnu.org/gnu/guix/guix-binary-1.3.0rc1.aarch64-linux.tar.xz

Re: Leaving the GNU Guix community

Hi Léo, I'm sorry to hear that you feel that you need to leave the community. I can understand why you feel that way, but I hope you'll remember that (to my knowledge) nobody has said that they don't want you here. I realize that in this moment, it must sting terribly to have your commit rights

Re: RISC-V is giving away developer boards

Hi all, On +2021-04-30 21:35:22 +0200, Pjotr Prins wrote: > It is probably a good idea to apply from an academic institution to > increase chances of getting a free board. I am happy to help with the > application. > > We already have the 2GB RAM polarfire which we mostly use for toy > stuff

Re: Leaving the GNU Guix community

Léo, Leo Le Bouter 写道： I feel like what has happened is really a disaster, I'm relieved that we share, at least, this. I think everyone does. I don't feel like contributing to GNU Guix anymore in the future. That's a great pity. I hope to welcome you back some day. Guix is better

Re: Outreachy: Timeline tasks

On Fri, 30 Apr 2021 18:05:15 +0100 Christopher Baines wrote: > > > > Task 1: Add instrumentation to identify the slow parts of processing > > new revisions: > > > > - Implementing a chart over time to identify slow parts: > > - The chart should consider two aspects, the time took by > >

Unfortunate statefulness of Guix Install image

Hello Guix. This may or may not be a "bug", but thought I'd report something I run into. I found that GUI install never worked for me but booting off Guix Install USB and then following https://guix.gnu.org/manual/en/html_node/Manual-Installation.html worked perfectly fine. Except, when you try

Re: New blog post on the Guix Build Coordinator: Building derivations, how complicated can it be?

Thanks Christopher, Mathieu & Ludo to help us understand what's going on -- Vincent Legoll

Re: A "cosmetic changes" commit that removes security fixes

On Fri, Apr 30, 2021 at 07:40:36PM +0200, Pierre Neidhardt wrote: > I trust that it is the case, but being the devil's advocate, I could > argue that from reading this thread does not make it obvious. Maybe the > decision process should be made more transparent? Let's not make this a big thing.

Re: RISC-V is giving away developer boards

It is probably a good idea to apply from an academic institution to increase chances of getting a free board. I am happy to help with the application. We already have the 2GB RAM polarfire which we mostly use for toy stuff right now:

Re: RISC-V is giving away developer boards

Ludovic Courtès writes: > Could interested developers raise their hands? :-) I'd be glad to help with development of the port, but I do not have enough spare cycles at present to help with the process of applying to get the hardware. Mark -- Disinformation flourishes because many

Re: Leaving the GNU Guix community

Hi, Ludovic Courtès writes: > You write that “the difference between the beginner and the experienced > is a construction”. I sympathize with your rejection of the > student-professor domination. However, I think newcomers can and should > benefit from guidance by the experienced; that’s the

Re: RISC-V is giving away developer boards

Hello, On Fri, Apr 30, 2021 at 7:08 PM Ludovic Courtès wrote: > Mark H Weaver skribis: > > > This might be of interest: > > > > https://riscv.org/blog/2021/04/risc-v-is-giving-away-developer-boards/ > > > > Perhaps the Guix project would like to apply to get one of these? > > What do you

Re: wip-ungrafting builds stuck

On Fri, Apr 30, 2021 at 06:32:54PM +0200, Ludovic Courtès wrote: > I’ve just merged ‘wip-ungrafting’ in master! It was at 76% according to > , with mostly ARM builds missing compared to > ‘master’. Now we have fresh binaries to download (or build)! Hooray! > Thanks Leo

Re: RISC-V is giving away developer boards

On Fri, Apr 30, 2021 at 06:36:29PM +0200, Ludovic Courtès wrote: > Could interested developers raise their hands? :-) I previously applied for early access to the BeagleV: https://beagleboard.org/beaglev I wasn't selected and I decided to focus on aarch64 for now. Hopefully some other people

Re: Outreachy: Timeline tasks

Luciana Lima Brito writes: > Hi, > > On Thu, 29 Apr 2021 21:14:10 +0100 > Christopher Baines wrote: > >> Great, can you add more detail to this bit? Given the instrumentation >> is a really important part, it would be good to have some working >> ideas for what this chart might look like, and

Re: RISC-V is giving away developer boards

Hello Mark, Am Fri, Apr 30, 2021 at 11:29:59AM -0400 schrieb Mark H Weaver: > This might be of interest: > https://riscv.org/blog/2021/04/risc-v-is-giving-away-developer-boards/ > Perhaps the Guix project would like to apply to get one of these? > What do you think? interesting offer, thanks

Re: RISC-V is giving away developer boards

Hi, Mark H Weaver skribis: > This might be of interest: > > https://riscv.org/blog/2021/04/risc-v-is-giving-away-developer-boards/ > > Perhaps the Guix project would like to apply to get one of these? > What do you think? That’d be great; a few people were interested in a port to RISC-V.

Re: wip-ungrafting builds stuck

Hey there! I’ve just merged ‘wip-ungrafting’ in master! It was at 76% according to , with mostly ARM builds missing compared to ‘master’. Now we have fresh binaries to download (or build)! For the record, ‘wip-ungrafting’ was merged in ‘version-1.3.0’ a few days ago

Re: Leaving the GNU Guix community

On Thursday, April 29th, 2021 at 11:43 PM, Leo Le Bouter wrote: > I feel like what has happened is really a disaster, I don't feel like > contributing to GNU Guix anymore in the future. Hey Léo, thank you for writing & for all your contributions. As a security professional I feel you deeply

Re: Outreachy: Timeline tasks

Hi, On Thu, 29 Apr 2021 21:14:10 +0100 Christopher Baines wrote: > Great, can you add more detail to this bit? Given the instrumentation > is a really important part, it would be good to have some working > ideas for what this chart might look like, and what goes in to making > it (like where

RISC-V is giving away developer boards

Hello Guix, This might be of interest: https://riscv.org/blog/2021/04/risc-v-is-giving-away-developer-boards/ Perhaps the Guix project would like to apply to get one of these? What do you think? Mark -- Disinformation flourishes because many people care deeply about injustice but

Re: New blog post on the Guix Build Coordinator: Building derivations, how complicated can it be?

Hello! Mathieu Othacehe skribis: > We have already discussed the Cuirass vs Build coordinator situation in > the past. I haven't changed by mind on that subject. The Guix Build > Coordinator is more or less the equivalent of the Cuirass remote build > mechanism[2]. Yes. So to answer Vincent’s

Re: Guix Home upstreaming plan

Hi Andrew, Andrew Tropin skribis: > There is a goal[0] to make Guix Home[1] a part of GNU Guix. It will reduce > the duplications between projects, increase integrity and will provide > Guix users with a missing tool for declarative configuration of home > environments improving out of the box

Re: Neovim plugin/addon packaging

On Fri, Apr 30, 2021 at 01:03:23AM -0400, Jack Hill wrote: > Greetings Guix, > > I'd like to improve the experience of installing Neovim plugins/add-ons with > Guix. I've submitted #48112 [0] which adds an XDG_DATA_DIRS search path so > nvim (the Neovim executable name) will be able to find

Re: Leaving the GNU Guix community

Hello, Am Freitag, den 30.04.2021, 01:43 +0200 schrieb Leo Le Bouter: > I think that the GNU Guix maintainers justify unacceptable behavior 1. What makes you think that? 2. How do you justify your own behaviour, specifically the kind of behaviour, that others have asked you to justify? > [The

Re: Leaving the GNU Guix community

Hi Léo, I’m sad you reached the conclusion that our inability to understand each other cannot be overcome; perhaps you’re right, though I like to believe there’s always a way forward. I hope we can meet each other again, in Guix or other spaces in more favorable conditions, under less stress.

Re: #:cargo-inputs don't honor --with-input

Hi Hartmut, Hartmut Goebel skribis: > FYI: yet another rust issue: #:cargo-inputs don't honor --with-input. Uh. More generally, Rust packages kinda create a “shadow dependency graph” via #:cargo-inputs & co., which breaks all the tools that are unaware of it. It was discussed several times