Re: Staging

On Tue, Feb 20, 2018 at 11:45:58AM +0200, Efraim Flashner wrote: > Java currently only affects x86_64, so I'm not sure that it would need > to be staging specifically. In any case if we can get it merged within > the next week or so that'd be amazing. I know our cmake is in need of an > upgrade,

Staging

There are some patches on the staging branch, including an update to the time zone database. What are the plans for the next week or so? Should we try merging the staging branch in that timeframe? signature.asc Description: PGP signature

Re: heads-up: Haskell updates

On Thu, Feb 15, 2018 at 06:03:56PM +0100, Danny Milosavljevic wrote: > Hi Ricardo, > > > Danny, could you please do this on master and core-updates? > > I've done it on master now. > > Maybe it's me being used to SVN, but can I git am the commit to core-updates? > > Wouldn't that cause a

Re: proposal: with-file-writeable

On Wed, Feb 14, 2018 at 02:51:08PM +0100, Ludovic Courtès wrote: > Gábor Boskovits skribis: > > > the make-file-writeable function seems a bit too imperative to me, it would > > look better if we could have a with-file-writeable function, so that we can > > constrain the

Re: [PATCH] Add SELinux policy for guix-daemon.

On Tue, Feb 13, 2018 at 09:46:53PM +0200, Efraim Flashner wrote: > Should etc/guix-daemon.cil be added to .gitignore? Yes, rekado confirmed this to me yesterday on #guix. Can you do it? :) signature.asc Description: PGP signature

Re: bug#30394: ARM compilation via qemu binfmt - Assertion failure

On Sun, Feb 11, 2018 at 12:45:18AM +0100, Chris Marusich wrote: > Danny Milosavljevic writes: > > > This is only fixed in glibc 2.27 (not in core-updates). > > Should we upgrade glibc in core-updates, then? Or is it better to do it > in the next core-updates cycle, to

Re: Re: [PATCH] gnu: Add python2-gyp

On Mon, Feb 05, 2018 at 05:39:50PM -0500, dpg wrote: > Sending a new patch, this will apply cleaner and has an actually good commit > message :-) Thanks! But it still didn't apply :) > From 300c37a8d9818cfc1a6315d2113cf58b110e1664 Mon Sep 17 00:00:00 2001 > From: DoublePlusGood

Re: 01/01: gnu: Add badass.

On Mon, Jan 29, 2018 at 06:09:16PM -0500, Mark H Weaver wrote: > Hi ng0, > > > commit 57f9671d22bb4ee37962c31b9eed0ae50859398a > > Author: ng0 > > Date: Wed Jan 17 22:42:55 2018 + > > > > gnu: Add badass. > [...] > > + (package > > +(name "badass") > > +(version

Re: 01/01: gnu: gource: Fix the hashes of mutated GitHub archives.

On Sun, Jan 28, 2018 at 08:36:42PM +0300, Oleg Pykhalov wrote: > Leo Famulari <l...@famulari.name> writes: > > Additionally, if a packager uses `guix download` to check the hash of > > some file, but uses an incorrect URL in the package definition, Guix > > will

Re: 01/01: gnu: gource: Fix the hashes of mutated GitHub archives.

On Thu, Jan 25, 2018 at 09:17:38AM -0500, Oleg Pykhalov wrote: > wigust pushed a commit to branch master > in repository guix. > > commit 45b486984d8ab092cf002cd0b500df4dc62e186b > Author: Oleg Pykhalov > Date: Thu Jan 25 16:58:35 2018 +0300 > > gnu: gource: Fix the

Re: [PATCHES] gnu: linux-libre: Full retpoline support on x86 [spectre mitigation]

On Sat, Jan 20, 2018 at 03:34:08PM -0500, Mark H Weaver wrote: > Here are two patches that: > > * Add gcc-7.3.0-RC-20180117, which includes support for retpoline. > * Use gcc-7.3 to build linux-libre on x86 systems. > > I'm currently running linux-libre-4.14.14 with full retpoline support: > >

Re: [PATCHES] gnu: linux-libre: Full retpoline support on x86 [spectre mitigation]

On Sun, Jan 21, 2018 at 10:09:41PM -0800, Chris Marusich wrote: > Mark H Weaver writes: > > > Here are two patches that: > > > > * Add gcc-7.3.0-RC-20180117, which includes support for retpoline. > > * Use gcc-7.3 to build linux-libre on x86 systems. > > Awesome! Thank you for

Re: Logging in with a prebuilt VM

On Sat, Jan 20, 2018 at 02:57:22AM +, Matthew Rennekamp wrote: > Hello all. > I've tried (albeit with little effort) a couple times to install v12 and v14 > from the USB images. However, neither times worked, so I'm taking care of > school in the meantime. > I found out while looking through

Re: 03/15: gnu: wxwidgets: Use webkitgtk-2.4.

On Mon, Jan 22, 2018 at 02:00:57PM -0500, Danny Milosavljevic wrote: > dannym pushed a commit to branch master > in repository guix. > > commit 8a58182c12193ae27359591c92febfdd602411f4 > Author: Danny Milosavljevic > Date: Mon Jan 22 17:34:13 2018 +0100 > > gnu:

Re: Prevent native-inputs references ending up in the final binary

On Sat, Jan 20, 2018 at 04:47:14PM +0100, Tobias Geerinckx-Rice wrote: > Danny, > > Danny Milosavljevic wrote on 20/01/18 at 11:40: > > We should change that in core-updates-next, if possible. > > > > I think that native-inputs shouldn't end up in the final binary as a > > reference [...] >

core-updates: SELinux

On Wed, Jan 17, 2018 at 07:50:28PM -0800, Leo Famulari wrote: > The latest core-updates evaluation is coming together [0], but there are > still a few notable issues: Some of the SELinux packages are also failing to build: https://hydra.gnu.org/build/2414231 I tried updating libsepol

Re: Meltdown / Spectre

On Fri, Jan 19, 2018 at 05:06:25PM -0500, Mark H Weaver wrote: > l...@gnu.org (Ludovic Courtès) writes: > > Leo Famulari <l...@famulari.name> skribis: > >> Something we can do very easily, even on the master branch, is to build > >> specific packages with GCC 7,

Re: Is it necessary to download the native inputs while installing packages?

On Thu, Jan 18, 2018 at 08:54:32PM +, Fis Trivial wrote: > Sorry about the mess in the original question. > > > > > ‘Installing’ is too ambiguous to answer. > > > > - When *substituting* (installing a binary), native-inputs are not > > required and should never be downloaded. > > This

Re: Is it necessary to download the native inputs while installing packages?

Sorry for the top-posting. I need to clarify what --fallback does. Guix will always build locally if the substitute servers say they lack something Guix needs. --fallback works when the substitute servers say they have something, and then the substitution fails unexpectedly. For example, the

Re: core-updates, let’s go!

On Mon, Jan 01, 2018 at 06:12:49PM +0100, Ludovic Courtès wrote: > We’ll have to stay focused in the coming days to fix everything as > quickly as we can. The latest core-updates evaluation is coming together [0], but there are still a few notable issues: * Pandas is failing to build:

Re: diffoscope

On Sat, Jan 13, 2018 at 06:44:02PM +0100, Gábor Boskovits wrote: > Hello guix, > > I think we should consider moving some diffoscope inputs to propagated > inputs. > It would be nice to test it with a plain profile, to check what should be > propagated. Help wanted :) > I don't know if

Re: LanguageKit (targets llvm)

On Sat, Jan 13, 2018 at 03:47:21PM +0100, Catonano wrote: > This project > > http://etoileos.com/etoile/features/languagekit/ > > targets llvm > > As far as I understand it doesn't target llvm too. It targets llvm _only_ > > If I understand correctly, it aims to make dinamic languages wrap the

Re: invoke instead of (system* ...

On Fri, Jan 12, 2018 at 08:16:40PM +0100, Catonano wrote: > recently I read that we should move to using this invoke procedure instead > of the (system* some-script) in defining little scripts in packages and > services definitions > > But I can't remember where exactly > > Where is this invoke

Re: core-updates warning: Not ready for GuixSD deployment

On Wed, Jan 10, 2018 at 10:13:51AM +0100, Ludovic Courtès wrote: > Leo Famulari <l...@famulari.name> skribis: > > > After rebooting, I found that my user's numerical ID had changed, so I > > no longer owned any of my files. Not being able to read ~/.ssh means you &

Re: Meltdown / Spectre

On Wed, Jan 10, 2018 at 11:46:46AM +0100, Tobias Platen wrote: > The Talos II is a free-er system. And its processor (the POWER9) does not > seem to be affected by Meltdown/Sprectre [1]. > > [1] https://mobile.twitter.com/RaptorCompSys?p=s The Talos teams says that their POWER8 and POWER9

Re: Meltdown / Spectre

On Tue, Jan 09, 2018 at 06:10:02PM -0500, Mark H Weaver wrote: > Marius Bakke writes: > > Katherine Cox-Buday writes: > >> I am also interested -- more from a philisophical perspective -- how > >> GuixSD and GNU squares with these kinds of security

Re: Meltdown / Spectre

On Wed, Jan 10, 2018 at 05:39:59AM +0800, Alex Vong wrote: > I have an idea. Should we add a news entry to Guix blog[0] summarizing > all the above? For example, we can advice users to install noscript and > turn off javascript by default and only enable it on trusted site when > necessary. I

Re: 01/01: gnu: python-pygpgme: Use GnuPG 1 for the test suite.

On Sun, Jan 07, 2018 at 06:57:43PM -0800, Chris Marusich wrote: > That's good to know. However, when I tried accessing the link > > https://hydra.gnu.org/jobset/gnu/master > > I get a 504 (gateway timeout). I feel like I often get this while > trying to browse Hydra. Does it load reliably for

Meltdown / Spectre

On Sat, Jan 06, 2018 at 09:20:50PM +0800, Alex Vong wrote: > I hope this is on topic. Recently, 2 critical vulnerabilities (see > https://meltdownattack.com/) affecting virtually all intel cpus are > discovered. I am running libreboot x200 (see > https://www.fsf.org/ryf). > What should I do right

core-updates warning: Not ready for GuixSD deployment

I recommend you do not reconfigure any systems that are important based on the current core-updates branch. After applying the proposed fix for GPM [0], I reconfigured my headless GuixSD system using core-updates. After rebooting, I found that my user's numerical ID had changed, so I no longer

Re: libmagic license

On Wed, Jan 03, 2018 at 11:21:02PM +0100, Catonano wrote: > Libmagic has a weird license > > Is it suitable for Guix ? > > Here it is > https://github.com/threatstack/libmagic/blob/master/COPYING Here is the license text: -- $File: COPYING,v 1.1 2008/02/05 19:08:11 christos Exp $ Copyright

Re: core-updates, let’s go!

On Wed, Jan 03, 2018 at 01:35:31PM -0500, Leo Famulari wrote: > Libtiff failed the first build attempt when the upstream FTP server > timed out. It has succeeded since then, but this will have caused a lot > of dependent packages to fail. > > Should I "Restart all dependenc

Re: 01/01: gnu: python-pygpgme: Use GnuPG 1 for the test suite.

On Wed, Dec 27, 2017 at 07:57:17PM -0500, Mark H Weaver wrote: > Alas, your most recent changes seem to have now broken qgpgme: > > https://hydra.gnu.org/eval/109869#tabs-now-fail > https://hydra.gnu.org/job/gnu/master/qgpgme-1.9.0.x86_64-linux >

Re: 01/01: gnu: python-pygpgme: Use GnuPG 1 for the test suite.

On Wed, Dec 27, 2017 at 07:57:17PM -0500, Mark H Weaver wrote: > Alas, your most recent changes seem to have now broken qgpgme: > > https://hydra.gnu.org/eval/109869#tabs-now-fail > https://hydra.gnu.org/job/gnu/master/qgpgme-1.9.0.x86_64-linux >

Re: [rhell...@mykolab.com: 02/02: gnu: mpv: Update to 0.28.0.]

On Wed, Dec 27, 2017 at 08:52:12PM +0100, Rutger Helling wrote: > Hi Leo, > > You can find the new features at: > https://github.com/mpv-player/mpv/blob/master/RELEASE_NOTES > > There are two reasons for me personally why I wanted to update: > 1. The mpv developers only support the latest

[rhell...@mykolab.com: 02/02: gnu: mpv: Update to 0.28.0.]

Hi Rutger, - Forwarded message from Rutger Helling - Date: Wed, 27 Dec 2017 04:52:26 -0500 (EST) From: Rutger Helling To: guix-comm...@gnu.org Subject: 02/02: gnu: mpv: Update to 0.28.0. rhelling pushed a commit to branch master in

Re: 01/01: gnu: python-pygpgme: Use GnuPG 1 for the test suite.

On Tue, Dec 26, 2017 at 07:11:13PM -0500, Mark H Weaver wrote: > > Author: Leo Famulari <l...@famulari.name> > > Date: Wed Dec 20 03:20:01 2017 -0500 > > > > gnu: gpgme: Build with the latest GnuPG. > > > > * gnu/packages/gnupg.scm (gp

Re: 02/02: gnu: python-pillow: Update to 4.3.0.

On Sun, Dec 24, 2017 at 06:16:29PM -0500, Kei Kebreau wrote: > I've attempted to use the upstream patch, but it involves some GIT > binaries which aren't supported by GNU patch. Among other hackish > options, temporarily upgrading to the appropriate upstream commit may > fix this for now. Does it

Re: Removing configure option for Gnuastro 0.5

On Sun, Dec 24, 2017 at 08:53:28PM +0100, Mohammad Akhlaghi wrote: > Hi Leo, > > Thanks a lot of applying the configuration change. > > > On December 24, 2017 8:28:43 PM GMT+01:00, Leo Famulari <l...@famulari.name> > wrote: > > >I notice our package is

Re: Removing configure option for Gnuastro 0.5

On Sat, Dec 23, 2017 at 04:37:51PM +0100, Mohammad Akhlaghi wrote: > Dear Guix developers, > > This is Mohammad Akhlaghi, the maintainer of GNU Astronomy Utilities. > > Gnuastro 0.5 was just released and since it is also packaged in Guix, I > wanted to let you know that the

Re: Seeding the Linux RNG at first boot

On Mon, Dec 11, 2017 at 10:16:42AM +0100, Ludovic Courtès wrote: > Leo Famulari <l...@famulari.name> skribis: > > At the same time we handle the random seed, we could also try reading > > from /dev/hwrng and, if the read is successful, copy some bytes into > > /de

Re: Seeding the Linux RNG at first boot

On Thu, Dec 07, 2017 at 10:07:38PM +0100, Ludovic Courtès wrote: > Leo Famulari <l...@famulari.name> skribis: > > On the guest side, we would extend urandom-seed-service to also draw on > > /dev/hwrng, which is where virtio-rng-pci makes the data from the host >

Seeding the Linux RNG at first boot

On Wed, Dec 06, 2017 at 12:11:36AM +0100, Marius Bakke wrote: > FWIW if you control the hypervisor, you can send something along the > lines of: > > qemu -device virtio-rng-pci,bus=pci.0,addr=0x1e,max-bytes=1024,period=1000 > > to feed the guest with entropy from the host through virtio, up to

Re: native-inputs ending up as run-time references [was: ISO image available for testing!]

On Wed, Dec 06, 2017 at 03:16:45AM +0100, Tobias Geerinckx-Rice wrote: > Hold on. I thought this happened *all the actual time*. > > To me, the output of ‘guix graph’ implies that ghc[*] refers directly to > perl, and ghc-haddock-library to hspec-discover, and that both of those > are native

Re: Reducing default verbosity

On Tue, Dec 05, 2017 at 02:33:01PM +0100, Ricardo Wurmus wrote: > * Redirect all build output to log files; as we can’t generally estimate > progress I’d use a spinner and maybe display the name of the current > build phase and the number of build phases that are left. > > Building

Re: java: switch to icedtea-8 as default JDK

On Mon, Dec 04, 2017 at 04:44:00PM +0100, Gábor Boskovits wrote: > Now that this problem around glibc is resolved, I think I will do some > history rewrite, so that these reverts, reverting the revert does not > show up. > I 'm also willing to rename the branch to have wip in the name, as this

Re: A few thing we might consider hosting

On Sun, Dec 03, 2017 at 08:21:35AM +0100, Gábor Boskovits wrote: > I was aware of the discussion thread, however I could not find out what the > current state is? Do we plan to modify this behaviour in the next release? I think the current state is "awaiting feedback" :)

Re: A few thing we might consider hosting

On Sat, Dec 02, 2017 at 05:28:51PM +0100, Gábor Boskovits wrote: > Sometimes while working in guix I run into problems because: > 1. a tarball was removed or modified upstream > > It would be great to have the ability to install the latest release in all > the supported ways on all supported

Re: Release!

On Thu, Nov 30, 2017 at 11:40:16AM +0100, Ludovic Courtès wrote: > 1. Do we pre-register berlin’s key on GuixSD? I vote yes. > 2. Do we add berlin.guixsd.org to the list of substitute servers on > GuixSD? On Guix? The drawback is that ‘guix’ sometimes talks to > both servers when

Re: Idea: Install script to better support improving contributor-friendliness of projects

On Tue, Nov 28, 2017 at 10:43:49PM +0300, lamefun@gmail.com wrote: > Another question, is Guix ever going to ship NVIDIA OpenGL libraries, > considering that this is a GNU project? Flatpak for example ships them > to support NVIDIA GPUs. The project I want to make contributor-friendly > with

Re: [PATCH] scripts: hash: Add --git option. WIP

On Tue, Nov 28, 2017 at 07:57:32PM +0100, Jan Nieuwenhuizen wrote: > Andy Wingo writes: > > Weird that we have done the same thing :) > > > > https://git.savannah.gnu.org/gitweb/?p=guix.git;a=commit;h=572907daff98a77a4215861a88b81d2f30542c09 > > :-) Nice!...on what branch is that? You did see

Re: 01/02: gnu: openssl@1.0: Replace with 1.0.2m [fixes CVE-2017-3735, CVE-2017-2736].

On Thu, Nov 02, 2017 at 05:22:34PM -0400, Marius Bakke wrote: > commit 1df4f5c919937b60bfb21ac2a60d8f0a6737c421 > Author: Marius Bakke > Date: Thu Nov 2 22:11:25 2017 +0100 > > gnu: openssl@1.0: Replace with 1.0.2m [fixes CVE-2017-3735, > CVE-2017-2736]. > >

Re: Problems with setting up prosody with IPv6 and certbot

On Sun, Nov 26, 2017 at 04:26:08PM +0100, nee wrote: > Hello, I've been trying to setup the prosody xmpp service a few weeks > ago, but a some things are not working out of the box. This is a great write-up! Can I ask you to send each problem to separately? It seems like the

SECURITY: Exim CVE-2017-16943

Hello! -- commit 5b327a2d6192adbabb5b98bc3a78eb8402bd6d1d Author: Leo Famulari <l...@famulari.name> Date: Sun Nov 26 15:23:13 2017 -0500 gnu: exim: Fix CVE-2017-16943. * gnu/packages/patches/exim-CVE-2017-16943.patch: New file. * gnu/local.mk (dist_patch_DATA

Re: Please write "Update to " instead of "Update snapshot"

On Sat, Nov 25, 2017 at 07:43:11PM -0500, Mark H Weaver wrote: > In my opinion, the version number is a very useful piece of information > to see for update commits when browsing the commit history. I regard > the practice of omitting the version number to be a slowly creeping > regression in our

Re: 01/01: gnu: audacity: Update to 2.2.0.

On Sat, Nov 18, 2017 at 08:38:54PM +0100, Pjotr Prins wrote: > On Sat, Nov 18, 2017 at 10:42:48AM -0500, Leo Famulari wrote: > > On Debian, the graphical user interface is broken for me (overlapping > > and blank elements), and it crashes when opening a file, with > > "

Re: 01/01: gnu: audacity: Update to 2.2.0.

On Sat, Nov 18, 2017 at 10:08:20AM -0500, Ricardo Wurmus wrote: > rekado pushed a commit to branch master > in repository guix. > > commit 3182a1d2f1f63bcc0840bf0c98e54a7037281163 > Author: Ricardo Wurmus > Date: Sat Nov 18 14:49:29 2017 +0100 > > gnu: audacity: Update

Re: Is anyone opposed to GnuTLS with DANE by default?

On Tue, Nov 14, 2017 at 08:22:54PM +0100, Tobias Geerinckx-Rice wrote: > ng0, > > What a coincidence! I was slogging through some very old mail, had just > read your original gnutls/dane message, and was about to post the very > same question. Then I ran ‘guix size’. > > ng0 wrote on 14/11/17 at

Re: Let's build 'core-updates'!

7 6:05:19 AM EST To: l...@gnu.org Cc: Leo Famulari <l...@famulari.name>, guix-devel@gnu.org Subject: Re: Let's build 'core-updates'! No one else mentioned it after the acl tests were enabled On November 7, 2017 11:54:47 AM GMT+02:00, l...@gnu.org wrote: >Efraim Flashner <efr...@flash

Re: The usability of Guix configurations

On Mon, Nov 06, 2017 at 03:12:11PM -0500, myglc2 wrote: > My system recently broke when I did an upgrade. I reported what I > thought was a bug (bug#29072) but it turned out that, because qemu > package code had been moved, my system configuration had become broken > ;-( > > Confronted with my

Re: Can't download signing key for Guix 0.13.0

On Mon, Nov 06, 2017 at 10:26:40AM +0100, oge wrote: > Hi all, > > I'm starting out with Guix but for some reason I can't download the public > key to verify the Guix 0.13.0 download. > > The following command (from > https://www.gnu.org/software/guix/manual/html_node/Binary-Installation.html) >

Re: Let's build 'core-updates'!

On Thu, Nov 02, 2017 at 11:29:17PM +0200, Efraim Flashner wrote: > On Thu, Nov 02, 2017 at 09:33:02PM +0100, Marius Bakke wrote: > > We are still missing the "binutils" update. Efraim, do you remember > > what the issue with 2.29 was? > > binutils-boot0 built fine, I don't remember what the next

Removing a store reference from a file

I noticed that Go executables built with the go-build-system keep an unnecessary reference to Go itself: $ guix gc --references $(realpath $(which syncthing)) /gnu/store/3h31zsqxjjg52da5gp3qmhkh4x8klhah-glibc-2.25 /gnu/store/bqlmgk6ngyi4pivnqpxma2wr5pj5mhkk-gcc-5.4.0-lib

Re: POWER Support

On Wed, Oct 25, 2017 at 03:47:19PM +0200, oury.dus...@tutanota.com wrote: > Are there plans to support POWER 8-9 systems for the GUIX package > manager and GUIXSD? I had read about TALOS and was just curious about > that support being worked on. I haven't heard of anyone working on it, but we

Re: Expat in GuixSD, please update

On Wed, Oct 25, 2017 at 07:29:28PM +0200, Tobias Geerinckx-Rice wrote: > Leo Famulari wrote on 25/10/17 at 19:22: > > Expat 2.2.3's release notes only mentioned CVE-2017-11742, which is a > > Windows vulnerability and out of scope for Guix. And I didn't see > > secu

Re: Expat in GuixSD, please update

On Wed, Oct 25, 2017 at 02:58:13PM +0200, Sebastian Pipping wrote: > Hi GuixSD team, > > > from looking at [1] and [2] my impression is that GuixSD is still at > version 2.2.2 with Expat, while there is version 2.2.4 with bugfixes > upstream. Is there anything blocking an update on your side

Re: speed of qemu vms

On Tue, Oct 24, 2017 at 09:30:06PM +0200, Hartmut Goebel wrote: > Hello, > > for testing I used to build VM using "guix system vm …" and the machines > are, well, reacting slowly: > > Plasma start up: 80 sec. > > Menu: 36 sec > > When I tried a Vm created with "guix system vm-image …" the

Re: Our package names should not include "github-com"

On Mon, Oct 16, 2017 at 05:38:43PM -0400, Leo Famulari wrote: > Using the domain name as part of the *upstream* library name is useful > for upstream authors because of how Go's built-in dependency management > tools work. Go integrates dependency management into the language and > t

Re: 01/04: gnu: mesa: Disable imx driver for armhf-linux.

On Mon, Oct 16, 2017 at 02:56:38PM +0200, Ludovic Courtès wrote: > From the maintainer’s viewpoint, it just stresses that we must keep > going with the efforts to improve our build infrastructure. Currently > that has only benefited x86, but perhaps now is a good time to plug our > ARM boxes

Re: 01/04: gnu: mesa: Disable imx driver for armhf-linux.

On Fri, Oct 13, 2017 at 08:38:13PM -0400, Mark H Weaver wrote: > Do you think it should be acceptable to merge a major branch into > 'master' where *all* graphical packages are broken on armhf? I think we all agree that we should not do this. As somebody who also works on merging these branches,

Re: Our package names should not include "github-com"

On Fri, Oct 13, 2017 at 01:12:32PM -0400, Mark H Weaver wrote: > l...@famulari.name (Leo Famulari) writes: > > gnu: Add go-github-com-templexxx-reedsolomon. > > On this, and a great many other packages, you've included "github-com-" > in the package names. I t

Re: 01/01: gnu: red-eclipse: Add store "data" package path as default.

On Tue, Oct 10, 2017 at 08:26:31AM -0400, Kei Kebreau wrote: > kkebreau pushed a commit to branch master > in repository guix. > > commit 42abb842f64f5dd7834cabd445a5f4d01f1e68a4 > Author: Adonay Felipe Nogueira > Date: Sun Aug 20 15:28:20 2017 -0300 > > gnu:

Re: Wrong hashes for libgit2 archives

On Sun, Oct 08, 2017 at 06:46:04PM +0200, Hartmut Goebel wrote: > Hi, > > I'm currently stuck with building kde-frameworks due to mismatching > hashes for libgit2: > > @ build-failed > /gnu/store/mgh4yjxkxfyqmc7c61vwq4vs8v837602-libgit2-0.26.0.tar.gz.drv - > 1 sha256 hash mismatch for output

Re: Go packaging

On Tue, Oct 03, 2017 at 11:15:04AM -0400, Leo Famulari wrote: > Based on my work creating a go-build-system and packaging a non-trivial > Go application [0], I want to start a discussion on how we can > efficiently package Go software in Guix. Another question, which is bikesheddy, is ho

Re: Go packaging

On Wed, Oct 04, 2017 at 06:19:18AM +0200, Pjotr Prins wrote: Thanks for your comments, Pjotr! > Thanks Leo for the explanation. Now I understand why Go programs, such > as the IPFS implementation, have so many dependencies... Yes, so many. As for transitive dependencies... well, I probably

Go packaging

Based on my work creating a go-build-system and packaging a non-trivial Go application [0], I want to start a discussion on how we can efficiently package Go software in Guix. Go software is developed rather differently from most of what we package, and I think our package abstraction does not

Re: [go-build-system]

On Thu, Aug 31, 2017 at 08:17:15AM -0400, Leo Famulari wrote: > I have a work-in-progress of a go-build-system with packages for > Syncthing up here: > > https://github.com/lfam/guix/tree/wip-syncthing > > It seems to work until the Syncthing build fails like this: I'm *ver

Re: Fetching patches as origins instead of copying them into the Guix Git repo

On Thu, Aug 31, 2017 at 11:52:25PM +0200, Marius Bakke wrote: > Leo Famulari <l...@famulari.name> writes: > > > On Thu, Aug 31, 2017 at 09:52:49PM +0200, Marius Bakke wrote: > >> Side note: I think we should start adding patches as origins instead of > >> cop

Re: [go-build-system] How to access properties or keys of a package on the build side?

On Mon, Aug 28, 2017 at 10:32:41PM +0200, Ricardo Wurmus wrote: > > Ricardo Wurmus writes: > > > You could also access the arguments of another package with > > “package-arguments”. Using the “properties” field isn’t pretty because > > it is a free form alist. > > > > You

Fetching patches as origins instead of copying them into the Guix Git repo

On Thu, Aug 31, 2017 at 09:52:49PM +0200, Marius Bakke wrote: > Side note: I think we should start adding patches as origins instead of > copying them wholesale, to try and keep the git repository slim. We should make a git-minimal package for things like this, or use guile-git / libgit2. Git

Re: [go-build-system]

On Tue, Aug 29, 2017 at 03:54:40PM +0300, Frederick Muriithi wrote: > Maybe the following will help clarify the issue: > > The package being built needs the sources of the dependenc(y/ies) to > be available in its GOPATH. > > The build system needs to set the GOPATH such that the Go build system

Re: [go-build-system] How to access properties or keys of a package on the build side?

On Mon, Aug 28, 2017 at 10:32:41PM +0200, Ricardo Wurmus wrote: > > Ricardo Wurmus writes: > > > You could also access the arguments of another package with > > “package-arguments”. Using the “properties” field isn’t pretty because > > it is a free form alist. > > > > You

Re: The future of 'guix environment'

On Wed, Aug 30, 2017 at 11:11:33PM +0800, 宋文武 wrote: > > 1) Add a caching mechanism. The environment profile should get built > > once, and then a symlink to it should be created in $PWD and > > registered as a GC root. This will, of course, require re-using some > > 'guix package' code to

Re: GSoC final update

(off-list) Hey Caleb, On Tue, Aug 29, 2017 at 02:44:56AM -0500, Caleb Ristvedt wrote: > I found myself checking the guile reference quite > frequently. One time I happened upon a part describing the ECMAScript > implementation (curiosity and all that), and noticed that several times > it was

[go-build-system] How to access properties or keys of a package on the build side?

Recently I made some progress on finishing the prototype go-build-system from Petter [0], and I need some advice. AFAICT, building a Go program requires the program's Go dependencies to have a particular filesystem layout, which corresponds to the way these dependencies are imported by the

Re: 'core-updates' status

On Fri, Aug 25, 2017 at 10:57:12PM +0300, Manolis Ragkousis wrote: > On 08/25/17 21:34, Marius Bakke wrote: > > Hello! > > > > 'core-updates' has finished building on x86_64 on i686, and the grafting > > failures should now be fixed. Are we ready to merge this branch? :-) > > > > Does

Re: 'core-updates' status

On Fri, Aug 25, 2017 at 08:34:21PM +0200, Marius Bakke wrote: > 'core-updates' has finished building on x86_64 on i686, and the grafting > failures should now be fixed. Are we ready to merge this branch? :-) I think it's ready. There are a handful of failing packages left, but I assume they will

Re: Grafting fails for latest Go release candidate

I saw this problem on the master branch. Original Message From: l...@gnu.org Sent: August 21, 2017 10:32:01 AM CDT To: Andy Wingo Cc: guix-devel@gnu.org Subject: Re: Grafting fails for latest Go release candidate Hi, Andy Wingo skribis:

Re: openssl is now a dependency of guix: possible license conflict?

On Fri, Aug 18, 2017 at 10:44:04PM +0800, Alex Vong wrote: > It seems julia had merge the mbedtls patches, so they should be working: > > https://github.com/JuliaLang/julia/pull/22614 > > Should we also adopt the patches? Personally, I think it depends on the advice of the libgit2 team. We

Re: git cannot be built

On Wed, Aug 09, 2017 at 03:44:23PM -0400, Mark H Weaver wrote: > Ricardo Wurmus writes: > > > Mark H Weaver writes: > > > >> Ricardo Wurmus writes: > >> > >>> Commit 7f171fdaadb15bb1b313b25e9be3d1988b0f650f broke git for me. I > >>>

Re: core-updates: biber

On Mon, Aug 07, 2017 at 08:47:53PM +0200, Ricardo Wurmus wrote: > For some reason even the updated patches didn’t apply correctly, so I > applied them manually (maybe it’s a problem on my end). I’ve tested > biber on one of my old projects and it works as expected: > > --8<---cut

Re: Small documentation improvements

On Mon, Aug 07, 2017 at 01:37:16AM +0200, Martin H. wrote: > Actually, it seems this change was totally wrong and broke my system. At > least that's what happened: I didn't really realize it immediately, but > after this change and the first successful package compile inside my guix > checkout I

Re: core-updates: biber

On Sun, Aug 06, 2017 at 11:44:41AM +0200, Ricardo Wurmus wrote: > Leo Famulari <l...@famulari.name> writes: > > The attached patches update texlive to 2017 and remove biber-2.5. > > Ricardo, can you check if biber@2.7 works with these patches? > > These patches don’t ap

Re: core-updates: biber

On Sun, Aug 06, 2017 at 12:14:47PM +0200, Andreas Enge wrote: > Hello, > > On Sat, Aug 05, 2017 at 06:38:48PM -0400, Leo Famulari wrote: > > The attached patches update texlive to 2017 and remove biber-2.5. > > I did not follow the new modular texlive packages, but it look

Re: core-updates: biber

On Sat, Aug 05, 2017 at 03:26:07PM -0400, Leo Famulari wrote: > On Mon, Jul 31, 2017 at 09:26:56AM +0200, Ricardo Wurmus wrote: > > If we upgrade those two, I’m pretty sure we won’t need Biber 2.5 any > > more and can replace it with what is currently biber-next. > >

Re: core-updates: biber

On Mon, Jul 31, 2017 at 09:26:56AM +0200, Ricardo Wurmus wrote: > If we upgrade those two, I’m pretty sure we won’t need Biber 2.5 any > more and can replace it with what is currently biber-next. > > I would suggest not to spend too much time on Biber 2.5 as it is on its > way out — it just needs

Re: [PATCH 001/303] gnu: Add opencolorio.

On Fri, Aug 04, 2017 at 11:02:07AM -0500, Christopher Allan Webber wrote: > ng0 writes: > > > Christopher Allan Webber transcribed 9.3K bytes: > >> I have a friend who's a Blender user who said they'd like to see > >> opencolorio support in the Blender package... this is an old patch, > >> but

Difficulty starting with Cuirass

Hi, I'm trying to set up Cuirass to build some manifests on a foreign distro. I decided to start by adapting Mathieu O's examples from March 2017: https://lists.gnu.org/archive/html/guix-devel/2017-03/msg00222.html However, when I try to use it with the files copied below, it fails: -- $

Re: core-updates: biber

On Mon, Jul 31, 2017 at 09:26:56AM +0200, Ricardo Wurmus wrote: > We haven’t yet updated the big texlive and texlive-bin packages to the > 2017 versions. (Actually, I have tested an update for the texlive-bin > package, but not for “texlive-texmf”.) > > If we upgrade those two, I’m pretty sure

Re: adwaita-icon-theme issue, cannot install GuixSD

On Wed, Aug 02, 2017 at 02:48:28PM +, Joshua Branson wrote: > This is probably a question that should be asked on help-g...@gnu.org. > guix-devel is really more for development quesitions, not trouble shooting. Yes, but it's okay :) We can answer it here, too. > On 08/02/2017 07:27 AM,

<    2   3   4   5   6   7   8   9   10   11   >