On Wed, Jul 11, 2018 at 16:11:37 +0200, Ludovic Courtès wrote:
> Hello Mike,
>
> Mike Gerwitz skribis:
[...]
>> pkgblurbs.txt has also been replaced by rec/pkgblurbs.rec.
>
> Commit daf76c7cd54df428abc28d490747c7f83a844df0 changes
> gnu-maintenance.scm to use the .rec files. Thanks for the
Hi Guix,
after reviewing the current state of the project “Improve the user
experience for the "guix package" command line tool”, for which Gábor
and I mentored an Outreachy intern, we have decided to terminate the
internship at the midterm evaluations.
The remainder of the funds that have been
U.Mutlu writes:
>> Thanks! I'm very grateful for your help. I succeeded in building
>> gcc-4.7.4 from almost no binary seeds[0] for GuixSD!
>
> Congrats! :-)
Thanks!
> Can you give us some info on your project? (mes?)
Mes[0] aims to help create full source bootstrapping for GNU/Linux
On Mon, Jun 04, 2018 at 10:18:53AM +0200, Pierre-Antoine Rouby wrote:
> Attached an update of importer.
Thanks! I'm sorry my response is so late.
> From 3e9b4fa12811432fdd7a4d6330f9093dcc72d25a Mon Sep 17 00:00:00 2001
> From: Rouby Pierre-Antoine
> Date: Thu, 26 Apr 2018 15:05:23 +0200
>
Jan Nieuwenhuizen wrote on 07/11/2018 07:01 PM:
U.Mutlu writes:
Just a tip: you can build the compiler much faster if you use
--disable-bootstrap
(here it reduces the compile time from 111 minutes down to 12 minutes).
After it's ok, then you can build w/o it to also test the
bootstrapping.
Clément Lassieur skribis:
> Ludovic Courtès writes:
>
>>> 1. Adding support for multiple inputs. Currently Cuirass only supports
>>> one input per specification, which has to be the Guix git repository.
>>> But one might want inputs for:
>>> - a repository containing the 'proc' that returns
U.Mutlu writes:
> Just a tip: you can build the compiler much faster if you use
> --disable-bootstrap
> (here it reduces the compile time from 111 minutes down to 12 minutes).
> After it's ok, then you can build w/o it to also test the
> bootstrapping.
Thanks! I'm very grateful for your help.
Hello,
On Wed, Jul 11, 2018 at 5:50 PM, Danny Milosavljevic
wrote:
> http://soc.yonsei.ac.kr/Abstract/International_journal/pdf/106_Data%20Randomization%20Scheme%20for%20Endurance%20Enhancement%20and%20Interference%20Mitigation%20of%20Multilevel%20Flash%20Memory%20Devices.pdf
Thanks a lot
I
On Wed, Jul 11, 2018 at 02:55:45PM +0200, Ludovic Courtès wrote:
> Now the question is, will it always be possible to run ‘guix pull’ from
> an arbitrary-old Guix? Maybe it will still be impossible sometimes if
> the old Guix is really too old. However, I suspect such issues will be
> much more
Hi Vincent,
On Wed, 11 Jul 2018 17:07:02 +0200
Vincent Legoll wrote:
> On Wed, Jul 11, 2018 at 4:17 PM, Danny Milosavljevic
> wrote:
> > the randomness is necessary for NAND wear levelling,
>
> Any pointers about that subject ?
Of course, I forgot the CC.
Forwarded Message
Subject:Re: /dev/urandom
Date: Wed, 11 Jul 2018 09:58:14 +0100
From: Steffen Schulz
To: Leo Famulari
I probably got it wrong.
but it seems the programs purpose is to build images (boot loaders). I
then wonder
Of course, I forgot the CC here too.
Forwarded Message
Subject:Re: /dev/urandom
Date: Wed, 11 Jul 2018 17:38:52 +0200
From: doncatnip
To: Vincent Legoll
I'd guess this is about the distribution of blocks within the image, so
that the load of each sector
On Wed, Jul 11, 2018 at 4:17 PM, Danny Milosavljevic
wrote:
> the randomness is necessary for NAND wear levelling,
Any pointers about that subject ?
This looks strange as I'd have thought that less writes => less wear.
--
Vincent Legoll
Hi Ludovic,
Ludovic Courtès writes:
>> 1. Adding support for multiple inputs. Currently Cuirass only supports
>> one input per specification, which has to be the Guix git repository.
>> But one might want inputs for:
>> - a repository containing the 'proc' that returns the jobs,
>> - a
2018-07-11 0:40 GMT+02:00 Ludovic Courtès :
> Hi Ioannis,
>
> Ioannis Panagiotis Koutsidis skribis:
>
> > This patch adds initial support for .socket unit files. It does not
> > currently work but is near completion.
>
> Could you expound a bit? That’s a very short summary for all the sweat
>
Hi Ricardo,
Ricardo Wurmus writes:
> Hi Clément,
>
> Ludovic Courtès writes:
>
>> Lots of exciting stuff in this message!
>
> Indeed!
Thank you :-)
> I’m supportive of all of the proposed changes. My only concern is about
> potential conflicts with Tatiana’s work on the web interface. Do
Greetings.
Just getting started. Don't know enough to properly post bugs yet, but hope
this is useful.
I really want to try out aarch64 with various (raspi3,LePotato) but decided to
start simple with power hungry ol' x86_64.
Used:
Hi Mark,
those are all good points.
In this specific case the randomness is necessary for NAND wear levelling,
so getting rid of it isn't good anyhow.
I'll investigate whether there is a way to defer invocation of
the randomizer so that the user can invoke it in the installed package.
Hello Mike,
Mike Gerwitz skribis:
> On Wed, Jun 27, 2018 at 21:40:19 -0400, Mike Gerwitz wrote:
>> I'll have to look at what guix/gnu-maintenance.scm does, but:
>
> [...]
>
>> Rather than get rid of gnupackages.txt completely, I wrote a script last
>> week to generate it from
Hello Jan!
Jan Nieuwenhuizen skribis:
> With Mes 0.16 released I felt that after two years of straight hacking
> I was pretty much done. Hmm...
>
> On the wip-bootstrap branch we have these packages
>
> binutils-2.20.1, gcc-2.95.3, and glibc-2.2.5
>
> built without using any of these 3
Hi Pjotr,
Pjotr Prins skribis:
> Is it an idea to also have a current Guix archive on the download
> page? Or at least a link to one?
>
>https://www.gnu.org/software/guix/download/
>
> Ever so often I need to rescue a running Guix system which won't run
> guix pull and even a
Hello,
Mark H Weaver skribis:
> l...@gnu.org (Ludovic Courtès) writes:
[...]
>> Currently if test fails, the whole derivation fails, and you can’t
>> install your package. If tests were run separately, this would no
>> longer hold: you could get your package regardless of whether tests
>>
Hi Clément,
Ludovic Courtès writes:
> Lots of exciting stuff in this message!
Indeed!
I’m supportive of all of the proposed changes. My only concern is about
potential conflicts with Tatiana’s work on the web interface. Do you
think we could merge Tatiana’s patches first?
--
Ricardo
On Thu, Jul 05, 2018 at 11:13:49AM -0400, Julian Graham wrote:
> Hi Guix folk,
>
> Find attached a patch that bumps the version of gzochi, a game
> development framework I maintain. I've done a `guix build' test run
> for amd64. Let me know if anything looks untoward.
>
Patch pushed. Next time
Hi Julian,
Julian Graham skribis:
> From d09752ea47bea9ef0a769e4356ffef5cf08242f8 Mon Sep 17 00:00:00 2001
> From: Julian Graham
> Date: Thu, 5 Jul 2018 11:06:02 -0400
> Subject: [PATCH] gnu: gzochi: Update to 0.12.
>
> * gnu/packages/game-development.scm (gzochi): Update to 0.12.
Applied,
Hello,
Marius Bakke skribis:
> It looks useful for those who don't want to or can't publish their own
> substitutes. And `guix challenge` makes it easy to verify the builds
> coming from a particular "channel".
I agree that it can be useful.
I would very much like it if we had a solution
Hi Roel,
Roel Janssen skribis:
> I'd like to change the way the symlinks to custom profiles are created.
> Here's what currently happens:
>
> $ guixr package -i hello -p guix-profiles/test
> $ ls -l guix-profiles
> lrwxrwxrwx. 1 user group 25 Jul 3 19:53 test -> guix-profiles/test-1-link
>
Hi Clément,
Sorry for the delay. Lots of exciting stuff in this message!
Clément Lassieur skribis:
> 1. Adding support for multiple inputs. Currently Cuirass only supports
> one input per specification, which has to be the Guix git repository.
> But one might want inputs for:
> - a
George Clemmer transcribed 733 bytes:
> Hi Nils,
>
> Nils Gillmann writes:
>
> > 4) before each profile kind is used for the first time,
> > make use of something like this for the brief introduction
> > of it again (our manual is not very long, but it is still
> > long):
>
>
29 matches
Mail list logo
