Re: GNU Guix Video Documentation

Hi Larissa, welcome to Guix! I'm putting the other Mentors/Coordinators and the developer list on CC. Please answer to the mailing list, so others can help you out too. On Wed, 24 Oct 2018 17:51:56 +0100 Larissa Leite wrote: > Hello, > > My name is Larissa and I would love to contribute to th

Re: Package variation

Hi Brett, Brett Gilio writes: > Hi chris! Thank you for your feedback, and your insight. I appreciate it > greatly. I have applied your changes (Both variations) and neither one > seems to be working and nautilus remains on the system. I am honestly at > a loss of what is wrong with the approach

Re: [outreachy] Further steps

Hi Laura, >> > If you have any other favourite packages, you can give them also a try. >> > It could just get more difficult, with more manual steps, other build >> > systems, dependencies to be packed first, code to be patched, etc. >> > >> >> Yes, this would also be good. Please tell us if you

Re: [outreachy] Further steps

On Wed, Oct 24, 2018 at 4:01 AM Gábor Boskovits wrote: > > Hello Laura, > > Congratulations! > > Björn Höfling ezt írta (időpont: > 2018. okt. 24., Sze, 7:17): > > > > On Tue, 23 Oct 2018 22:48:30 -0300 > > Laura Lazzati wrote: > > > > > Hi all! > > > > > > I'm really happy that the patch worked

Re: Package variation

Ludovic Courtès writes: > Hi! > > Brett Gilio skribis: > >> I am trying to customize my the default gnome-package which gets >> installed with the gnome-desktop-service. > > On this topic, don’t miss Chris’s excellent tutorial: > > > https://gnu.org/software/guix/blog/2018/customize-guixsd-u

Re: Mono and .NET Core

Adam Van Ymeren writes: > I tried to package .NET Core a while ago but didn't produce anything useful. > Their GNU/Linux story was rapidly changing at the time. > > .NET Core was a pain to package partly because it bootstraps from a binary > version of .NET Core similar to Rust. Although it

Re: Mono and .NET Core

Ludovic Courtès writes: Hello! > AFAIK nobody worked in this area yet, so you’ll probably have the > privilege to be a pioneer! :-) > > Mono was added by janneke (Cc’d), who might have something to add? Nothing more than: yes, please go ahead and update it! I created it for a client of mine an

Re: Promoting the GNU Kind Communication Guidelines?

Hello Ludo, l...@gnu.org (Ludovic Courtès) writes: > Mathieu Lirzin skribis: > >> Following the announcement made by RMS regarding the new GNU Kind >> Communication Guidelines (GKCG) [1], I would like to know if the Guix >> developpers in particular its maintainers would agree to adopt it in >>

Re: Promoting the GNU Kind Communication Guidelines?

Jack Hill skribis: > > Interesting. I too am eager understand your thinking on this. I am skeptical of codes of conduct in FLOSS projects because they often come bundled with a certain (non-software-related) political orthodoxy. The Contributor Covenant is the worst offender in this regard, hav

Re: Guix & IPFS

> To be precise, builders of fixed-output derivations (derivations for > which the hash of the result is known in advance) have network access. Oh, I did not know this detail. Thanks for pointing it out! > How did you define ‘gx-fetch’? It's on the wip-ipfs2 branch. Find the (broken) patch at

Re: Packaging gx (for IPFS): Need to update default Go to 1.11?

On Wed, Oct 24, 2018 at 04:02:46PM +0200, Pierre Neidhardt wrote: > > > First, the implementation of go-build-system is really inefficient for > > Go 1.11, especially since things compiled with Go 1.11 keep a huge > > run-time dependency graph: > > Is it _only_ inefficient because of issue 32949

Re: Packaging gx (for IPFS): Need to update default Go to 1.11?

On Wed, Oct 24, 2018 at 01:40:26PM +0200, Pierre Neidhardt wrote: > Is there a good reason for sticking to 1.9 or should we update to 1.11? There are two reasons. First, the implementation of go-build-system is really inefficient for Go 1.11, especially since things compiled with Go 1.11 keep a h

Re: Packaging gx (for IPFS): Need to update default Go to 1.11?

> First, the implementation of go-build-system is really inefficient for > Go 1.11, especially since things compiled with Go 1.11 keep a huge > run-time dependency graph: Is it _only_ inefficient because of issue 32949 or is there another reason? > https://bugs.gnu.org/32949 > > That could prob

Re: Mono and .NET Core

I tried to package .NET Core a while ago but didn't produce anything useful. Their GNU/Linux story was rapidly changing at the time. .NET Core was a pain to package partly because it bootstraps from a binary version of .NET Core similar to Rust. Although it may be possible to bootstrap via Mo

Re: Mono and .NET Core

Hello! Brett Gilio skribis: > Two questions here. > > 1) Has anybody already started taking to try and upgrade Mono to latest? > If not, I will give it a go. > > 2) Have we started any packaging on .NET Core, would like to know to > prevent redundancy in work. AFAIK nobody worked in this area y

Re: Mono and .NET Core

Hello! Brett Gilio skribis: > Two questions here. > > 1) Has anybody already started taking to try and upgrade Mono to latest? > If not, I will give it a go. > > 2) Have we started any packaging on .NET Core, would like to know to > prevent redundancy in work. AFAIK nobody worked in this area y

Re: Package variation

Hi! Brett Gilio skribis: > I am trying to customize my the default gnome-package which gets > installed with the gnome-desktop-service. On this topic, don’t miss Chris’s excellent tutorial: https://gnu.org/software/guix/blog/2018/customize-guixsd-use-stock-ssh-agent-everywhere/ :-) Ludo’.

Re: Come back and graphical installer

Hello Danny! Danny Milosavljevic skribis: > I agree. I've been meaning to write parted bindings for guile, but > I got side-tracked with https://github.com/daym/guile-gcc-unit which > can extract prototypes out of gcc source files (in order to automate > wrapper generation). Now I'm motivated

Re: Channel dependencies

Hello! Chris Marusich skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> Good point. I agree that it’s similar to the question of propagated >> inputs, which we deal with by reporting an error when a collision >> arises. >> >> So, similarly, I think the safe way would be to report an error

Re: Guix & IPFS

Hi! Pierre Neidhardt skribis: >> As discussed before (I think?), builds are performed in an isolated >> environment without network access—this is one of the measures taken to >> guarantee build reproducibility and statelessness. >> >> So what you’re doing here (running “gx” in a derivation) ca

Re: GuixSD on AArch64

Vagrant Cascadian skribis: > On 2018-10-22, Ludovic Courtès wrote: >> On IRC earlier today Vagrant mentioned that the Pinebook AArch64 laptop >> (see ) should be able to run >> GuixSD when Linux-libre 4.19 and U-Boot 2018.11 are out, with 100% free >> softwar

Re: Packaging Inferno

Hi Diego, Diego Nicola Barbato skribis: > I have sent a patch incorporating most of your feedback to > guix-patc...@gnu.org (bug#33080). Thank you, and sorry that review takes some time. I guess that’s the price to pay when submitting non-trivial packages. ;-) >> Do you know whether other FS

Re: 01/01: gnu: snap: Update to 4.2.2.2.

Hello, Mark H Weaver writes: > According to 'git' on my machine, this commit is signed with GnuPG key > ED0EF1C8E126BA831B485FE9DA00B4F048E92F2D, which is different from the > key that you uploaded to Savannah (A834B9E080A93738). Oops! > Can you please verify that ED0EF1C8E126BA831B485FE9DA00B

Re: Packaging gx (for IPFS): Need to update default Go to 1.11?

Correction: gx itself does not need Go 1.11, but go-ipfs requires that gx be compiled with Go 1.11+. -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

Re: Promoting the GNU Kind Communication Guidelines?

Hello Mathieu, Good to see you here! Mathieu Lirzin skribis: > Following the announcement made by RMS regarding the new GNU Kind > Communication Guidelines (GKCG) [1], I would like to know if the Guix > developpers in particular its maintainers would agree to adopt it in > place of the current

Re: Promoting the GNU Kind Communication Guidelines?

Hello, Jack Hill skribis: > On Tue, 23 Oct 2018, Alex Griffin wrote: > >> FWIW once I noticed that Guix had adopted the Contributor Covenant, it >> factored strongly into my decision to stop contributing to the project >> last year. > > Interesting. I too am eager understand your thinking on thi

hydra.gnu.org off-line for maintenance

Hello Guix, The hydra.gnu.org build farm has been off-line since yesterday ~4PM UTC and will remain off-line roughly until the end of the week. The FSF sysadmins (it’s hosted at the FSF’s data center) are performing a major storage upgrade that happens to need more time than expected. In the mea

Re: Promoting the GNU Kind Communication Guidelines?

Hello Tobias, Tobias Geerinckx-Rice writes: > I've (re-)read the links you've provided (thanks). I guess it's > supposed to be obvious what you find disagreeable about them, but if > one doesn't disagree, it's not that obvious. :-) IMO Discussing what I find disagreeable with the particular for

Re: [outreachy] Further steps

Hello Laura, Congratulations! Björn Höfling ezt írta (időpont: 2018. okt. 24., Sze, 7:17): > > On Tue, 23 Oct 2018 22:48:30 -0300 > Laura Lazzati wrote: > > > Hi all! > > > > I'm really happy that the patch worked :) > > > > Tomorrow -yet Tuesday here, I live in the past :P - I will close the >