A major milestone in bootstrapping

2018-08-26 Thread Jeremiah
Today I am proud to announce a combo of releases with major milestones. First stage0, reached Release version 0.2.0; which includes the following: A 250byte hex0 bootstrap binary that is self-hosting and builds hex1, which builds hex2, which bootstraps M0 macro assembly which has been used to make

Re: guix download and GitHub

2018-08-26 Thread HiPhish
Thank you, no idea how I missed that :( On Mittwoch, 22. August 2018 00:02:14 CEST you wrote: > Hello, > > Looking at the manual entry for guix download [0], we can see: > > guix download verifies HTTPS server certificates by loading > the certificates of X.509 authorities from the direc

Re: Guix on aarch64

2018-08-26 Thread Leo Famulari
On Sun, Aug 26, 2018 at 12:13:44PM -0400, Mark H Weaver wrote: > Regardless, I think we should seriously consider moving the Aarch64 > build slave(s) to Hydra for now, until Cuirass is more mature. I agree with your points about why berlin.guixsd.org makes it harder to maintain the aarch64 port. I

Re: Guix on aarch64

2018-08-26 Thread Mark H Weaver
Hi Ludovic, l...@gnu.org (Ludovic Courtès) writes: > Mark H Weaver skribis: > >> If I'm not mistaken, I believe I have confirmed with the test below that >> a substitute for binutils from early commencement on aarch64 is not >> available on berlin. > > [...] > >> It occurs to me that on Hydra, I

Re: Help needed: Updating GHC to 8.4.3

2018-08-26 Thread Timothy Sample
Hello, Timothy Sample writes: > Hi Again, > > I’ve attached an updated patch that builds a working GHC 8.4.3 (that is, > it compiles “hello.hs” in a pure environment). It might need a bit more > work yet. See notes below. It turns out that it wasn’t a pure environment. I was running Guix on

Re: Should *.fr.texi be committed in git?

2018-08-26 Thread Nils Gillmann
Christopher Lemmer Webber transcribed 302 bytes: > I frequently find that my git repo says: > > Unstaged changes (2) > modified doc/contributing.fr.texi > modified doc/guix.fr.texi > > And then I need to revert them before doing a pull. > > These files are autogenerated from translations, ri

Re: Should *.fr.texi be committed in git?

2018-08-26 Thread Julien Lepiller
Also I just remembered: if we don't commit guix.*.texi, configure complains about their non-existence and fails. Le 26 août 2018 13:07:31 GMT+02:00, Julien Lepiller a écrit : >Le Sun, 26 Aug 2018 06:59:53 -0400, >Christopher Lemmer Webber a écrit : > >> I frequently find that my git repo says:

Re: Should *.fr.texi be committed in git?

2018-08-26 Thread Julien Lepiller
Le Sun, 26 Aug 2018 06:59:53 -0400, Christopher Lemmer Webber a écrit : > I frequently find that my git repo says: > > Unstaged changes (2) > modified doc/contributing.fr.texi > modified doc/guix.fr.texi > > And then I need to revert them before doing a pull. > > These files are autogenera

Should *.fr.texi be committed in git?

2018-08-26 Thread Christopher Lemmer Webber
I frequently find that my git repo says: Unstaged changes (2) modified doc/contributing.fr.texi modified doc/guix.fr.texi And then I need to revert them before doing a pull. These files are autogenerated from translations, right? Shouldn't they be gitignore'd and not committed to git at all

New French PO file for 'guix-manual' (version 0.15.0)

2018-08-26 Thread Translation Project Robot
Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'guix-manual' has been submitted by the French team of translators. The file is available at: http://translationproject.org/latest/guix-manual/fr.po (We can arrange things s