Re: Neovim plugin/addon packaging

On Mon, May 03, 2021 at 12:46:30AM -0400, Jack Hill wrote: > On Sun, 2 May 2021, Efraim Flashner wrote: > > > ng0/nikita thought about it a few years ago but I think the > > copy-build-system works well enough. I know for vim we need a vim > > profile hook to create the documentation, does neovim

Re: Neovim plugin/addon packaging

On Sun, 2 May 2021, Efraim Flashner wrote: ng0/nikita thought about it a few years ago but I think the copy-build-system works well enough. I know for vim we need a vim profile hook to create the documentation, does neovim need something like that too? I'm not sure and will need to

Re: [PATCH] maint: Do not xz-compress ISO images.

Le Sun, 2 May 2021 23:16:48 +0200, Ludovic Courtès a écrit : > The xz-compressed image is 23% smaller than the original ISO image > (with built-in zlib compression), but the extra decompression step is > unconventional and often a hindrance for users. See discussion at >

Re: RISC-V is giving away developer boards

> Could interested developers raise their hands? :-) *raises hand* In other news, tinycc has now an RISC-V assembler[1] :) [1] https://lists.nongnu.org/archive/html/tinycc-devel/2021-04/msg9.html

Re: linux-libre source tarballs

On Sun, May 02, 2021 at 06:26:15PM -0400, Leo Famulari wrote: > In the meantime, can we make a 'kernel-updates' Cuirass job again, that > would build a kernel-updates branch on Savannah? Mistake: I'd want to call the branch wip-kernel-updates, so that it's rebaseable. > We had one recently for a

Re: linux-libre source tarballs

On Sun, May 02, 2021 at 11:08:49PM +0200, Ludovic Courtès wrote: > For packages we can add a ‘max-silent-time’ property, but there’s > nothing like this for origins. Oh, right. > I wonder if there’s a way we could address it in (gnu ci). > > Thoughts? In the meantime, can we make a

Re: GNU Guix 1.3.0rc1 available for testing!

On Sun, May 02, 2021 at 02:45:18PM -0400, Maxim Cournoyer wrote: > It should fail only once (as it currently would if Ludo's key was > missing), and display two messages/two commands instead of one to get > the missing keys. This is because we exit after the loop, based on the > exit_flag

Re: Pinebook Pro no longer WIP

Hello, On Sun, May 2, 2021 at 2:33 AM Vagrant Cascadian wrote: > Untested: > eMMC I've tested this today. I was on sdcard, and migrated "/" to emmc, keeping the bootloader on sdcard because I don't like opening the PBP to get back to a booting state in case of problems. I modified the root

Re: Criticisms of my "tone" (was Re: A "cosmetic changes" commit that removes security fixes)

Hi Mark, Am Sonntag, den 02.05.2021, 17:02 -0400 schrieb Mark H Weaver: > Hi Leo, > > Leo Prikler writes: > > > Am Sonntag, den 02.05.2021, 15:29 -0400 schrieb Mark H Weaver: > > > > Likewise, there's no middle ground on assuming evil > > intentions, you either assume they exist or you don't.

Re: Bringing substitutes from the Guix Build Coordinator to users

Hi Christopher, Thanks for your message! It’s great to see a summary of what’s been cooking in the Coordinator and your vision around it. Christopher Baines skribis: > More specifically, while the architecture is similar to daemon > offloading, there are some practical advantages. Since the

Re: Criticisms of my "tone" (was Re: A "cosmetic changes" commit that removes security fixes)

Hi Ludovic, Ludovic Courtès writes: > I’m sorry to inform you that this is not a philosophy or linguistics > mailing list. *lol* Indeed, this conversation has wandered quite far off-topic. Thanks for stepping in. > I invite you to continue this discussion off-list. We have a release > coming

[PATCH] maint: Do not xz-compress ISO images.

The xz-compressed image is 23% smaller than the original ISO image (with built-in zlib compression), but the extra decompression step is unconventional and often a hindrance for users. See discussion at . * Makefile.am

Re: Jam: which licence is this?

Hi, Mark H Weaver skribis: > For most purposes, the relevant question is: which license(s) cover the > source code, because that's where users will want to exercise the four > freedoms of free software. The license(s) that cover the package > outputs are of far less interest, because that's

Re: linux-libre source tarballs

Leo Famulari skribis: > On Sat, May 01, 2021 at 10:45:22PM -0400, Leo Famulari wrote: >> The immediate solution is for me to make sure the tarballs have built >> before committing the updates. I already do this for x86_64 and I can >> start doing it for aarch64 too. > > I started building the

Re: Pinebook Pro no longer WIP

Vagrant Cascadian skribis: > Someone pointed to me various patches[0][1] and kernel module > selections[2] related to the Pinebook Pro that lead to me feeling > confident to merge some kernel and u-boot changes for the Pinebook Pro > into guix/master... > > Which now means that you should be

Re: Criticisms of my "tone" (was Re: A "cosmetic changes" commit that removes security fixes)

Hi Leo, Leo Prikler writes: > Am Sonntag, den 02.05.2021, 15:29 -0400 schrieb Mark H Weaver: >> >> Leo Prikler writes: >> >> > Let us assume for the sake of argument I were to introduce a bug >> > into Guix. There are a number of ways this can happen, but let's >> > focus on the important

Re: Guix Home upstreaming plan

Hi, Xinglu Chen skribis: > On Fri, Apr 30 2021, Ludovic Courtès wrote: [...] >> Since this kind of tool is rather unusual (there’s no real equivalent >> I’m aware of in other distros) > > Nix Home Manager[2] is very similar to Guix Home, it allows for the same > kind of declarative

Re: Criticisms of my "tone" (was Re: A "cosmetic changes" commit that removes security fixes)

Leo, Mark, Mark H Weaver skribis: > This is a false dilemma , > because you've missed a very important case, namely: > > 5. You assume *nothing*. I’m sorry to inform you that this is not a philosophy or linguistics mailing list. I invite you to

Re: FYI: guile-scheme bindings to GNU Mach and the Hurd

Hi Maxime & all, Maxime Devos skribis: > Joshua Branson schreef op za 01-05-2021 om 11:04 [-0400]: >> Hey guix people, >> >> I just ran across a pretty recent thread in bug-hurd land. Apparently >> there is a VERY WIP effort to get some guile-scheme bindings for GNU >> Mach and the Hurd. >>

Re: Criticisms of my "tone" (was Re: A "cosmetic changes" commit that removes security fixes)

Hi Mark, Am Sonntag, den 02.05.2021, 15:29 -0400 schrieb Mark H Weaver: > Hi Leo, > > Leo Prikler writes: > > > Let us assume for > > the sake of argument I were to introduce a bug into Guix. There > > are a > > number of ways this can happen, but let's focus on the important > > distinction

Re: Criticisms of my "tone" (was Re: A "cosmetic changes" commit that removes security fixes)

Hi Leo, Leo Prikler writes: > Let us assume for > the sake of argument I were to introduce a bug into Guix. There are a > number of ways this can happen, but let's focus on the important > distinction here, which is me purposefully introducing that bug vs. it > happening due to oversight. > >

Re: GNU Guix 1.3.0rc1 available for testing!

Hi Leo, Leo Famulari writes: > On Sat, May 01, 2021 at 05:25:45PM -0400, Leo Famulari wrote: >> Maybe we should update the manual to mention "1.3.0rc1" and the correct >> key. > > I've attached a patch. > >> > 1. Testing the binary tarball on the distro of your choice. You can >> >

Re: please, let avoid misunderstandings

Hi Simon, Thanks for your heroic explanation. I think it also tells us something about the grief some of the maintainers went through. This is a good point to close the threads. All points have been made and it is necessary not to burden the people too much who do the real work. As in talk is

Re: branch master updated: gnu: sbcl: Update to 2.1.4.

OK, thanks for the update! Cheers! -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

Re: guix-install.sh: Add support for more than one signing key.

Maxim, Maxim Cournoyer 写道： The forthcoming 1.3.0 release will be signed with my personal GnuPG key \o/ Don't forget to also update OPENPGP-SIGNING-KEY-{ID,URL} in doc/guix.texi on the master and release-1.3.0 branches. Thank you! T G-R signature.asc Description: PGP signature

Re: Jam: which licence is this?

On Sun, May 02, 2021 at 12:53:07AM -0400, Mark H Weaver wrote: > My understanding is that the 'license' field of a package in Guix has > _always_ been meant to summarize the license restrictions associated > with the package source (the output of "guix build --source"), and > *not* merely the

How is the LaTeX-related file psfonts.map installed on Guix?

Hi, I'm trying to define a Guix environment that enables the following LaTeX document to be compiled: \documentclass[a4paper,12pt]{article} > \usepackage[utf8]{inputenc} > \usepackage[swedish]{babel} > \usepackage{url} > \usepackage{color} > \usepackage[colorlinks=true, linkcolor=blue,

Re: branch master updated: gnu: sbcl: Update to 2.1.4.

On Sun, May 02, 2021 at 11:57:10AM +0200, Pierre Neidhardt wrote: > Indeed, as far as I can remember we've always updated SBCL directly on > master, because it's one of those exceptions. Alright, I didn't know that. Let's keep the status quo in that case. Maybe we should mention this kind of

Re: Criticisms of my "tone" (was Re: A "cosmetic changes" commit that removes security fixes)

Am Sonntag, den 02.05.2021, 12:17 +0800 schrieb 宋文武: > Hello Leo, I see nothing wrong for assuming bad faith when security > fixes of packages are removed, in the end the truth matter, which I > believe is: You thought the patches for cario is not needed now on > core-updates, so you remove them.

Re: [Outreachy] [Guix Data Service]: Identify the slow parts of process

Canan Talayhan writes: >>From this I'm guessing the temp_package_metadata table has only one >>row. My understanding is that this table would normally have as many >>rows as packages in the revision of Guix being processed. It might not >>be possible to reproduce the slowness of the query

Re: please, let avoid misunderstandings

On Sun, 02 May 2021 at 12:37, zimoun wrote: > Personally, I am still staying away from Guix proper because I felt hurt > by the fact that the whole community did nothing for two months to > prevent such escalations. I apology for this wording. I do not mean that individuals had not tried to

Re: [Outreachy] [Guix Data Service]: Identify the slow parts of process

>From this I'm guessing the temp_package_metadata table has only one >row. My understanding is that this table would normally have as many >rows as packages in the revision of Guix being processed. It might not >be possible to reproduce the slowness of the query without more rows. I've inserted

Re: Hero culture among Guix maintainers

Hello Ryan, tl;dr: (!= 'accountability 'blame), but accountability is essential to any social endeavour. Ryan Prior writes: > Hey Guix. There's a specific thing I'm motivated to address after the > recent security incident with the "cosmetic" patches & all the fallout > of that. Some

please, let avoid misunderstandings

Dear Léo, Dear Guix, My name pops up here so let me expose *my* feelings. I am truly sad by the situation. From my eyes, such escalation and such wordings means we––as a community––collectively failed somewhere. Instead of speaking, we have to individually introspect and ask what each of us

Re: Criticisms of my "tone" (was Re: A "cosmetic changes" commit that removes security fixes)

Am Samstag, den 01.05.2021, 23:13 -0400 schrieb Mark H Weaver: > Hi Leo, > > I took the liberty of refilling the quotations in your email to make > them more readable. Please do. > > Leo Prikler writes: > > > Am Samstag, den 01.05.2021, 18:12 -0400 schrieb Mark H Weaver: > > > Can you please

Re: branch master updated: gnu: sbcl: Update to 2.1.4.

Hi Leo, Indeed, as far as I can remember we've always updated SBCL directly on master, because it's one of those exceptions. > `guix refresh -l sbcl` shows "Building the following 221 packages would > ensure 988 dependent packages are rebuilt [...]" Note that most of these packages are "cl-*"

Re: Outreachy: Timeline tasks

Luciana Lima Brito writes: > On Sat, 01 May 2021 20:07:56 +0100 > Christopher Baines wrote: > >> Luciana Lima Brito writes: >> >> > For that I propose to build 2 charts, one of the >> > macro view, what we call "overview first", showing the >> > sections(processes) and their whole time taken.

Re: Neovim plugin/addon packaging

On Sat, May 01, 2021 at 04:25:18PM -0400, Jack Hill wrote: > Thanks for your reply. > > On Fri, 30 Apr 2021, Efraim Flashner wrote: > > > On Fri, Apr 30, 2021 at 01:03:23AM -0400, Jack Hill wrote: > > > Greetings Guix, > > > > > > I'd like to improve the experience of installing Neovim

Re: rust-tempfile-3 update to 3.2.0 breaks sequoia build

Hi Nicolas, I was able to fix sequoia by updating to 1.1 and applying some more changes. Please review so we can get it into upcoming guix 1.3. Thanks in advance -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com

Re: Criticisms of my "tone" (was Re: A "cosmetic changes" commit that removes security fixes)

Leo Famulari writes: > [...] > To clarify, Leo Prikler is not the same person that was involved in > removing the Cairo bug fixes. That was a different person, also named > Leo. > > Not me, either :) Um, my bad, thank you!

Re: FYI: guile-scheme bindings to GNU Mach and the Hurd

Hi Maxime, Maxime Devos writes: > Joshua Branson schreef op za 01-05-2021 om 11:04 [-0400]: >> Hey guix people, >> >> I just ran across a pretty recent thread in bug-hurd land. Apparently >> there is a VERY WIP effort to get some guile-scheme bindings for GNU >> Mach and the Hurd. >> >>

Re: What processor features does Guix support on i686?

Hi Leo, Thanks for asking about this, and for ably taking care of our Linux-libre packages. I'm grateful for your work on this. Leo Famulari writes: > I noticed that Linux 5.12 has a new config option regarding "Processor > family". The default choice, Pentium-Pro (M686), is highlighted in