Re: Status of Submitted Patches

Hi Sahithi, >> When you’re done with these changes, please make a local commit and send >> the output of “git format-patch -1”. > the following is the output of “git format-patch -1” > > */0001-Added-Colorize-module-to-Guix-ui.scm.patch/* > > Can you please check and guide to proceed further.

Re: About GCC-5.5.0

In this new execution, I have set CFLAGS='-fno-stack-protector', but the variable stack_protector still with null value (stack_protector='' ). Attached log files. This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It

Re: Status of Submitted Patches

Hi Ricardo, Done with changes and local commit > When you’re done with these changes, please make a local commit and send > the output of “git format-patch -1”. the following is the output of  “git format-patch -1” */0001-Added-Colorize-module-to-Guix-ui.scm.patch/* Can you please check and

Re: About GCC-5.5.0

Hello Samuel, yes, I attach the log file. ​Thank you Rene > > > > Any idea of how we can approach it? > > Getting the config.log would allow to have more ideas :) > This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake.

Re: About GCC-5.5.0

Hello, Rene, le mer. 23 mai 2018 22:57:21 -0400, a ecrit: > I am updating my Guix repository on Debian/Hurd and I have the following error > in the 'configure' phase of glibc(glibc-intermediate-2.23). > We have tried to add the flag '-fno-stack-protector' to glibc, however the > error remains. >

Re: next browser (was: Packaging a free Firefox)

Pierre Neidhardt writes: > Ricardo Wurmus writes: > >> It is sometimes possible to patch the sources by replacing the library >> name with the full path of the library. Have you tried that? > > You are right. I think what we need here is to patch all

Re: Status of Submitted Patches

Hi Sahithi, >> Another note about style: I think it would be better to use >> “alist->hash-table” instead of “make-hash-table” followed by repeated >> modifications to the hash table with “hashq-set!”. We prefer to avoid >> mutation of values when possible. > > I have made all necessary

Re: Updating udisks: New dependencies (libblockdev, volume-key, dmraid, libbytesize, ndctl...)

Pierre Neidhardt transcribed 1.3K bytes: > > I'm working on updating udisks from the "old legacy" version (which is > currently packaged in Guix) to version 2.7.6. > > https://github.com/storaged-project/udisks > > It turns out to be much harder than expected! Recent versions of udisks >

Updating udisks: New dependencies (libblockdev, volume-key, dmraid, libbytesize, ndctl...)

I'm working on updating udisks from the "old legacy" version (which is currently packaged in Guix) to version 2.7.6. https://github.com/storaged-project/udisks It turns out to be much harder than expected! Recent versions of udisks depend on libblockdev, which in turn depends on the

Re: Code of Conduct and Diversity Statement

Leo Famulari wrote: > On Wed, May 16, 2018 at 11:26:07PM -0700, Chris Marusich wrote: >> These all seem like good improvements to me. I think we should upgrade >> to 1.4! > > +1 Oh, is this still under review? +1! Kind regards, T G-R

Re: Status of Submitted Patches

Hi Ricardo, > Another note about style: I think it would be better to use > “alist->hash-table” instead of “make-hash-table” followed by repeated > modifications to the hash table with “hashq-set!”. We prefer to avoid > mutation of values when possible. I have made all necessary modifications.

Re: next browser (was: Packaging a free Firefox)

Ricardo Wurmus writes: > It is sometimes possible to patch the sources by replacing the library > name with the full path of the library. Have you tried that? You are right. I think what we need here is to patch all the cffi packages. For instance, sqlite3-lib contains

Re: Code of Conduct and Diversity Statement

On Wed, May 16, 2018 at 11:26:07PM -0700, Chris Marusich wrote: > These all seem like good improvements to me. I think we should upgrade > to 1.4! +1 signature.asc Description: PGP signature

Re: next browser (was: Packaging a free Firefox)

Hi Pierre, > Ricardo Wurmus writes: > >>> The main issue is with cffi: it does not find the libraries installed by >>> Guix. >> […] >> >> I don’t understand this. Should it load any libraries that the user may >> have installed? Or do you only refer to a specific set of

Re: next browser (was: Packaging a free Firefox)

Ricardo Wurmus writes: >> The main issue is with cffi: it does not find the libraries installed by >> Guix. > […] > > I don’t understand this. Should it load any libraries that the user may > have installed? Or do you only refer to a specific set of libraries > that is

RE: Mes 0.14 released

> I am pleased to announce the release of Mes 0.14, representing 98 commits > over 4 weeks. Mes+MesCC now compiles a self-hosting TinyCC that has only > been slightly patched. > This means that we can now build a tcc that depends only on a 1MB ASCII M1 > seed. GuixSD currently uses a ~250MB

Re: GSoC: Adding a web interface similar to the Hydra web interface

Hi Tatiana, > I have committed the first HTML template page (with table of specifications > stored in the database) to web-interface branch. Can you please review it? That’s great! Congratulations on your first commit! I’ll make a couple of extra comments on style and conventions because this

Re: next browser (was: Packaging a free Firefox)

Hi Pierre, > Hooray, I've managed to run Next Browser on GuixSD! Excellent! I’m looking forward to playing with it. > The main issue is with cffi: it does not find the libraries installed by Guix. […] I don’t understand this. Should it load any libraries that the user may have installed?

Re: [rb-general] Mes 0.14 released

On Thu, May 24, 2018 at 08:00:17AM +0200, Jan Nieuwenhuizen wrote: > I am pleased to announce the release of Mes 0.14, representing 98 > commits over 4 weeks. Mes+MesCC now compiles a self-hosting TinyCC > that has only been slightly patched. > > This means that we can now build a tcc that

Mes 0.14 released

I am pleased to announce the release of Mes 0.14, representing 98 commits over 4 weeks. Mes+MesCC now compiles a self-hosting TinyCC that has only been slightly patched. This means that we can now build a tcc that depends only on a 1MB ASCII M1 seed. GuixSD currently uses a ~250MB binary seed