Expat 2.2.7 with security fixes has been released / CVE-2018-20843

Hello everyone! Sorry for the noise if you heard about the release of 2.2.7 about a week ago through some other channel and maybe even took action, already! To be quick, there is one DoS fix — for CVE-2018-20843 [1] — and misc build system fixes. The change log with details is up at [2]. If

Re: Guix beyond 1.0: let’s have a roadmap!

On 2019-06-27 21:02, Alex Griffin wrote: On Thu, Jun 27, 2019, at 4:31 PM, Ludovic Courtès wrote: What do *you* want Guix to address in the future? * Guix System ** TODO add firewall-service to provide a configurable stateful firewall suitable for most desktops and servers +1 *** TODO

Re: Guix beyond 1.0: let’s have a roadmap!

Le 27 juin 2019 18:05:27 GMT+02:00, "Ludovic Courtès" a écrit : >Hello Guix! > >People rightfully suggested having some sort of a roadmap for what’s >next. Many of us certainly have specific ideas in mind, but having >that >written down can certainly clarify what this project is about to

Re: Guix beyond 1.0: let’s have a roadmap!

- A graphical install and interface to package management (GTK or something else graphical). - Finally fix TeXlive... :p - User services (That's more of a Shepherd thing, but Guix is involved.) -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

Re: Guix beyond 1.0: let’s have a roadmap!

Hi Svante, Svante Signell skribis: > Are you interested in a buildd (in the context of Debian)? I'm > currently hosting the mahler Debian buildd VM for GNU/Hurd and kamp > Debian buildd VM for kFreeBSD amd64 and i386. The first box (mahler) is > reasonably fast and has excellent bandwidth

Re: Guix beyond 1.0: let’s have a roadmap!

zerodaysford...@sdf.lonestar.org (Jakob L. Kreuze) skribis: > Ludovic Courtès writes: > >> What do *you* want Guix to address in the future? > > Is there room for parameterized packages? À la Gentoo's USE flags? Sounds good to me! I’ve added it to my local copy. Ludo’.

Re: Guix beyond 1.0: let’s have a roadmap!

Hello, Vagrant Cascadian skribis: > On 2019-06-27, Ludovic Courtès wrote: >> People rightfully suggested having some sort of a roadmap for what’s >> next. > ... >> What do *you* want Guix to address in the future? > > A few architecture support issues come to mind: > > * Architectures > > **

Re: Guix beyond 1.0: let’s have a roadmap!

Hi P, P skribis: > System upgrades are still incredibly slow even with a small number of > packages, there definitely needs to be more build servers and a way to tell > `guix package -u` to wait for substitutes to become available. > > Package search is kind of bad compared to Arch's pacman.

Re: Guix beyond 1.0: let’s have a roadmap!

On Thu, Jun 27, 2019 at 12:31 PM Ludovic Courtès wrote: > > What do *you* want Guix to address in the future? * Extend 'guix environment' to cover use-cases that people currently use docker-compose for * Improve UX of 'guix environment' by using sane defaults and conventions such as reading from

Re: Guix beyond 1.0: let’s have a roadmap!

On Thu, 2019-06-27 at 18:05 +0200, Ludovic Courtès wrote: > Hello Guix! > > People rightfully suggested having some sort of a roadmap for what’s > next. Many of us certainly have specific ideas in mind, but having > that written down can certainly clarify what this project is about to >

Re: Guix beyond 1.0: let’s have a roadmap!

On Thu, Jun 27, 2019, at 4:31 PM, Ludovic Courtès wrote: > What do *you* want Guix to address in the future? * Guix System ** TODO add firewall-service to provide a configurable stateful firewall suitable for most desktops and servers *** TODO add service-extensions to existing services so that

Re: Guix beyond 1.0: let’s have a roadmap!

Ludovic Courtès writes: > What do *you* want Guix to address in the future? Is there room for parameterized packages? À la Gentoo's USE flags? > ** TODO ‘guix system reconfigure --target=host.example.org’ is a thing > ** TODO ‘guix deploy’ is a thing :) Regards, Jakob signature.asc

Re: Guix beyond 1.0: let’s have a roadmap!

On 2019-06-27, Ludovic Courtès wrote: > People rightfully suggested having some sort of a roadmap for what’s > next. ... > What do *you* want Guix to address in the future? A few architecture support issues come to mind: * Architectures ** TODO system/installer images for armhf ** TODO

Re: Guix beyond 1.0: let’s have a roadmap!

‐‐‐ Original Message ‐‐‐ On Thursday, June 27, 2019 6:05 PM, Ludovic Courtès wrote: > What do you want Guix to address in the future? System upgrades are still incredibly slow even with a small number of packages, there definitely needs to be more build servers and a way to tell `guix

Guix beyond 1.0: let’s have a roadmap!

Hello Guix! People rightfully suggested having some sort of a roadmap for what’s next. Many of us certainly have specific ideas in mind, but having that written down can certainly clarify what this project is about to newcomers, and it can help us insiders build a common understanding of what it

Re: 01/02: Revert "gnu: openssh: Clean-up custom install phase."

Hello! Mark H Weaver skribis: > In general, when reverting commits, I think it would be useful to > include an explanation in the commit log. What do you think? I’m all for it. Reverts are the one thing whose explanation cannot go anywhere but in the commit log. (Regardless, thank you

Re: having trouble modifying guix-daemon

Hi, Robert Vollmert skribis: > I’m trying to investigate why guix-daemon appears to spend > a lot of time locking store directories. (It’s possible that > it’s doing useful work and just the debug output is useless.) Note that there are already quite a few debugging statements that you can

Re: guix lint TLS certificate error

Hi, Giovanni Biscuolo skribis: > /home/giovanni/{git}/giovanni.biscuolo.net/guix/gnu/packages/astronomy.scm:190:4: > celestia@1.6.1-815.9dbdf29: failed to create x86_64-linux derivation: > (srfi-34 # "/usr/local/var/guix/daemon-socket/socket" errno: 111] 6570090>) Note that you should

Re: GNU Guix 1.0.1 released

Hi! Jonathan Brielmaier skribis: > On 5/19/19 11:43 PM, Ludovic Courtès wrote: >> We are pleased to announce the release of GNU Guix 1.0.1. >> >> This is a bug-fix release primarily addressing one major issue in the >> graphical installer of the standalone Guix system, as well as less >>

Re: Lightning talk at IPFS camp

Hello! Pierre Neidhardt skribis: > Update: I've been asked if I wanted to conduct a "Deep dive" > (https://github.com/ipfs/camp/blob/master/DEEP_DIVES/README.md) about > IPFS and Guix. In other words: what problem we've encountered, how to > solve them, what we'd like to do. Neat. > I think

Re: 01/02: Revert "gnu: openssh: Clean-up custom install phase."

On 6/27/19 8:16 AM, Tobias Geerinckx-Rice wrote: > Mark, > > Mark H Weaver wrote: >> I don't doubt that reverting these commits was the right thing to do, >> but it would be good to know _why_ they were reverted.  Can you provide >> a link to a relevant discussion, or else explain it here? > >

Re: 01/02: Revert "gnu: openssh: Clean-up custom install phase."

Mark H Weaver wrote: Thanks. For the record, the relevant bug is . I absolutely would have added that URL had I been aware of its existence before now :-) Thanks, T G-R signature.asc Description: PGP signature

Re: 01/02: Revert "gnu: openssh: Clean-up custom install phase."

Thanks. For the record, the relevant bug is . Mark

Re: 01/02: Revert "gnu: openssh: Clean-up custom install phase."

Mark, Mark H Weaver wrote: I don't doubt that reverting these commits was the right thing to do, but it would be good to know _why_ they were reverted. Can you provide a link to a relevant discussion, or else explain it here? They remove .../var/empty which breaks ssh-daemon. In general,