GSoC proposal last-minute double-check

I realize this is very last-minute indeed, but thought I'd see if I could get some feedback before I submit. I'm looking at working on the Guile Scheme guix-daemon - it seems much more concrete in scope than the build tool. I wrote my proposal based on https://www.gnu.org/software/soc-projects/guid

Re: Planning for the next release

Marius Bakke skribis: > Ludovic Courtès writes: > >>3. UEFI support documented and possibly improved. >> >> We can certainly document the UEFI setup and add the /boot/efi >> partition in some of the ‘operating-system’ examples. >> >> The more difficult part is the installat

Re: Planning for the next release

Hi! Leo Famulari skribis: > On Thu, Mar 30, 2017 at 02:37:47PM +0200, Ludovic Courtès wrote: >> Hello Guix! >> >> It’s time to plan for the next release! Here’s what we maintainers >> think should be done for the next release, which would hopefully happen >> within less than a month: >> >> Pl

Re: [PATCH 1/5] gnu: Add python-mando-0.3.1

Muriithi Frederick Muriuki skribis: > * gnu/packages/python.scm (python-mando-0.3.1): New variable. Applied, thanks! Ludo’.

Re: [PATCH] qjackctl

Hi Mark, Thanks for the patches! They look all right, except a couple of minor details: Mark Meyer skribis: > From 93bdb3c4f6b8d74584ec29ea4f6733c373c44ab2 Mon Sep 17 00:00:00 2001 > From: Mark Meyer > Date: Wed, 29 Mar 2017 10:35:46 +0200 > Subject: [PATCH 1/2] Add qjackctl to the audio pack

Re: Non-graphical GRUB configuration

myglc2 skribis: > On 04/02/2017 at 22:13 Leo Famulari writes: > >> On Sun, Apr 02, 2017 at 05:06:20PM -0400, Leo Famulari wrote: >>> Based on the GRUB manual [0], how about this plan? >>> >>> We'd add these fields to (grub-configuration): >> >> [...] >> >> NixOS has the user provide a string: >>

Re: 'guix build' and garbage collection

Hi Chris, Chris Marusich skribis: > My understanding is that Nix builds derivations in a temporary > directory. My understanding is that eventually, we copy the results of > the build into the final, content-addressed store path. Since we don't > know the final, content-addressed store path un

Re: GSoC proposal last-minute double-check

Hi Caleb, Thank you for your proposal. Caleb Ristvedt skribis: > * Plan > (I can't find any mention of mid-term evaluations in the 2017 GSoC timeline, > so I'm guessing that https://www.gnu.org/software/soc-projects/guidelines.html > is outdated?) > > The missing pieces according to the suggest

at HEAD, vim fails its tests

Hi, I just updated my system after the core-update branch merge. Vim doesn't pass its testsuite: Executed 287 tests >From test_system.vim: Found errors in Test_system_exmode(): function RunTheTest[24]..Test_system_exmode line 7: Expected '0' but got '/' Test results: >From test_system.vim:

website question

Most initial texts for pragmatique's website are now done. As I don't want to introduce it with a plain white one-page site, I thought about what I want to use. Jinja (taler.net) or Guile (guix, guile). The software part of the project is based on and into Guix, so it would be good to make use of G

Re: Getting rid of "source file .. newer than compiled" messages

Hi Ricardo, Am 02.01.2017 um 16:08 schrieb Ricardo Wurmus: > If you want to keep a stable branch of Guix around you can use “git > worktree”. Then you can have a worktree on master and another worktree > where your WIP branches are being edited. Editing or switching branches > in one worktree wo

Re: [PATCH] profiles: Generate database file for manpages

Hi Ludovic! Sorry I couldn't reply before! l...@gnu.org (Ludovic Courtès) writes: > Hi Maxim, > > Maxim Cournoyer skribis: > >> Unfortunately some of the simplifications you made appear to break it >> :). I've tried your reworked patch and got the same result as you (no >> result found except w

Re: 'guix build' and garbage collection

l...@gnu.org (Ludovic Courtès) writes: > Hi Chris, > > Chris Marusich skribis: > >> My understanding is that Nix builds derivations in a temporary >> directory. My understanding is that eventually, we copy the results of >> the build into the final, content-addressed store path. Since we don't

packages which are broken after core-updates merge

neomutt no longer works with kyotocabinet correctly: Apr 3 13:52:29 localhost vmunix: [ 426.159873] traps: mutt[937] trap invalid opcode ip:7f15d1356008 sp:7fffe89d9070 error:0 Apr 3 13:52:29 localhost vmunix: [ 426.159876] in libkyotocabinet.so.16.13.0[7f15d12e9000+ee000] icecat is failing,

Re: Planning for the next release

On Mon, Apr 03, 2017 at 10:26:54AM +0200, Ludovic Courtès wrote: > Leo Famulari skribis: > > I just pushed a tzdata update to a new staging branch. Let's build and > > merge this branch before the next release. > > We can do that, but should it be a blocker? Anyway, let’s try and we’ll > see. >

Re: [PATCH] qjackctl

> "LC" == Ludovic Courtès writes: LC> Could you try to come up with a ChangeLog-style commit message LC> that follows our convention? You can see ‘git log’ for examples LC> of what to type, and LC> . I

Add OggVorbis support to moc

Hi list, please consider the attached patch, it adds OggVorbis support to moc. Cheers, Mark >From 9517f2beea0ab4199ad5d558bfcab82a5df713bd Mon Sep 17 00:00:00 2001 From: Mark Meyer Date: Mon, 3 Apr 2017 21:29:25 +0200 Subject: [PATCH] 2017-04-03 Mark Meyer * gnu/packages/music.scm (moc): Add O

[PATCH] guix hash: -g hashes a git repository

* guix/scripts/hash.scm (show-help, %options): Add -g option. (guix-hash): Support hashing of Git URLs. * doc/guix.texi (Invoking guix hash): Document guix hash --git. --- doc/guix.texi | 18 ++ guix/scripts/hash.scm | 37 + 2 files chang

Re: packages which are broken after core-updates merge

> icecat is failing, with new profiles, with old profiles. This can be > reproduced in a new profile by selecting 'Preferences > Applications'. > It should immediately crash. It doesn't crash when "--with-system-icu" is removed.

Re: "guix potluck", a moveable feast

l...@gnu.org (Ludovic Courtès) writes: >>> To work around that, I think the server should resolve package >>> specifications when the potluck.scm file is submitted, and insert each >>> package in the Guix package graph of the moment. Does that make sense? >>> Maybe that’s what you were describing