(Warning: this email is in french because the meeting is supposed
to be held in French.)
Bonjour Guix,
Pour rappel, Guix@Paris c'est demain soir ! 😎
C'est toujours à l’April et toujours à 19h !
**SPOILER ALERT**… on risque d’un peu parler de ce qui s’est dit pendant
les Guix Days !
D’ici là, je
Hi,
Nicolas Graves via "Development of GNU Guix and the GNU System
distribution." writes:
> The snapper branch is here with no activity for quite some time.
>
> There's a patch for snapper in 57311, maybe we can start by deleting the
> branch.
Done (the branch is now deleted).
--
Thanks,
Max
Felix Lechner via "Development of GNU Guix and the GNU System
distribution." writes:
> My primary hurdle with modernizing Debbugs, if anyone cares, is that the
> FSF is reluctant to deploy GNU Guix. They insist on Trisquel plus
> Ansible [11] which is what they have been using for some time.
>
>
> ./guix/docker.scm:261: (((head ...) (tail ...) id)
This one is not like the others. However, looking at the context I think
the pattern could just be (head tail id).
> Why not? Do I miss something in the implementation of ’match’?
The only reason I can think of would be if these matches
Hi,
>From Ludo’s mastodon message [1]:
Re ‘match’ penalty: when using ellipses in patterns, the generated
code checks for “proper lists”, which is O(n). The trick is to
instead match a pair:
✔ (match lst ((head . tail) …))
❎ (match lst ((head tail ...) …))
Therefore I have
Hi Felix,
> I also packaged and deployed on GNU Guix
>
> (A) the fifteen-year old Debbugs version deployed at gnu.org [2][3][4]
> (B) the modern Debbugs version deployed at debian.org [5][6][7]
> (C) and a custom version of Mumi for my own bug fixes [8][9]
>
> Together with the official de
Josselin Poiret writes:
> Your mailing system is sending out emails that contain an invalid
> Message-ID header (missing right part of the msgid as specified in
> [1]),
> ...
> [1] https://datatracker.ietf.org/doc/html/rfc2822#section-3.6.4
My apologies (to everyone)! Thank you for bringing thi
Josselin Poiret writes:
> One thing I would like to get rid of though is debbugs. It causes a
> lot of pain for everyone, eg. when sending patchsets, it completely
> breaks modern email because it insists on rewriting DMARC-protected
> headers, thus needing to also rewrite "From:" to avoid DMARC
Steve George writes:
> The general opinion seemed to be, that it was better to fix small
> issues and commit the change for new users, so they had the
> satisfaction of their contribution making it into the repository. One
> proposal was to do the 'fix', and to then reply back to the bug with a
>
Steve George writes:
> elsewhere in the thread someone mentions some tags we could use
> consistently so maintainers can find patches that have been reviewed
> easily.
It seems on the [dev manual] we already have "reviewed-looks-good"
documented. Thus, I'd like to propose the below *mutually ex
salut,
On jeu., 01 févr. 2024 at 20:51, Tanguy LE CARROUR wrote:
> Ce jeudi 8 février 2024 à 19h, se tiendra la cinquième édition de Guix@Paris
> ouverte au public.
> Comme les fois précédentes, il sera possible de participer à distance
> (*cf* ci-dessous).
Chouette ! Ayant raté la journée de
> The wishlist is: provide a machine-readable description on guix-science
> channel side in order to help in finding the good overlap between
> commits of different channels.
i wrote about a missing abstraction here:
https://lists.gnu.org/archive/html/guix-devel/2023-12/msg00104.html
which is m
> Anything is better than an obscure failure/backtrace
i disagree with this specific statement. in the long run, the (inconspicuous)
cost of added complexity can easily move anything into net negative territory.
IOW, feel encouraged to account for the cost of complexity. it's rarely done
prior
Hi Suhail,
On 5 Feb, Suhail wrote:
> Felix Lechner via writes:
>
> > Another is that committers should commit what they think is right
> > rather than ask for revised patches.
>
> I could be mistaken, but I believe this does happen today at least some
> of the time. Is your position that
>
>
Am Tue, Feb 06, 2024 at 09:22:43AM -0500 schrieb Maxim Cournoyer:
> Thanks for the report. It occurred a few times in the past weeks, where
> the 'mumi' service had to be restarted on Berlin. Let's keep this open
> to see if it'll occur again. Otherwise I'll close it in a week or two.
It has ha
Hello Carlo,
On Tue, 2024-02-06 at 23:10 +1100, Carlo Zancanaro wrote:
> The nginx{,-upstream,-server}-configuration records have fields for
> {extra,raw}-content, which do allow arbitrary configuration lines to
> be
> added to their config. I think this is a sensible escape hatch to
> have
> to p
Hello!
Timothy Sample skribis:
> I sent https://issues.guix.gnu.org/68769. Now I see that I didn’t have
> the newest Git hooks installed, so no change ID and no email to the
> relevant team. Sorry! (I use worktrees so the Makefile didn’t fix this
> for me automatically – I should have double
Hi Christina,
Christina O'Donnell writes:
> Hi Guix,
>
> From my machine[1] connecting to https://issues.guix.gnu.org/ results
> in, after 130 seconds[2], a 502 bad gateway. It's been having issues
> for over a week, but I only just found a need to test it.
>
> I couldn't see an issue about it o
Hi,
Simon Tournier writes:
> Hi,
>
> Well, using Guix bdab356 from a little bit more than one month old, then
> associating the channel guix-science 0b3d4a2f last week, I get the
> failure:
>
> $ guix build /gnu/store/g3aa5rh7bs5pyxd3q1gvhwz1s9z1vh3z-guix-science.drv
> The following derivation w
Hi Hartmut & Josselin,
On Mon, Feb 05 2024, Hartmut Goebel wrote:
> Am 05.02.24 um 10:39 schrieb Steve George:
>
> [order of quotations reversed]
>
> The current mail-based workflow is too complicated ... which has been
> discussed several times already without any result:
Well, that's not total
Hi Edouard,
On 6 Feb, Edouard Klein wrote:
> I, for one, would be willing to review patches, hoping that in turn my
> patches would be reviewed instead of staying in limbo forever, which is
> a drag on me submitting more patches.
>
> Is there a procedure to follow, or do I just start replying
I, for one, would be willing to review patches, hoping that in turn my
patches would be reviewed instead of staying in limbo forever, which is
a drag on me submitting more patches.
Is there a procedure to follow, or do I just start replying "LGTM" to
patch email threads ?
Cheers,
Edouard.
Steve
Hi Christian!
On Sun, Feb 04 2024, Christian Miller wrote:
> I wanted to try out the Nix service and followed the manual. I had
> some trouble while doing so. The following are the steps I took, the
> errors I encountered, and how I resolved them. As well as feedback to
> the experience.
Thank
On 2024-02-06 13:09:15 +0100, Clément Lassieur wrote:
> Hi! Why is it more complicated with services? You don't need forks at
> all to use packages and services outside of Guix proper.
For packages we have transformations, or I can just inherit. But I am not aware
of such option for services (i
Quoting Tanguy LE CARROUR (2024-02-06 08:31:39)
> In order to test the latest installer, I went to the "latest download"
> page [1] and clicked on "x86_64-linux" under "GNU Guix System on Linux"
> and ended up on an error page [2]:
> […]
> Is it the ISO that has to be tested? How can I download it?
Hi Dale!
On Tue, Feb 06 2024, Dale Mellor wrote:
>There is no middle ground.
The nginx{,-upstream,-server}-configuration records have fields for
{extra,raw}-content, which do allow arbitrary configuration lines to be
added to their config. I think this is a sensible escape hatch to have
to pr
On Tue, Feb 06 2024, Tomas Volf wrote:
> On 2024-02-05 23:08:29 +0100, Wilko Meyer wrote:
>> Guix offers ways to use packages outside of Guix proper in a pretty feasible
>> and maintainable way (manifests, setting up channels), maybe promoting them
>> as
>> an alternative to having things in guix
On 2024-02-05 23:08:29 +0100, Wilko Meyer wrote:
> Guix offers ways to use packages outside of Guix proper in a pretty feasible
> and maintainable way (manifests, setting up channels), maybe promoting them as
> an alternative to having things in guix proper "as soon as possible" (as
> that's not th
Hi Sunhail,
Your mailing system is sending out emails that contain an invalid
Message-ID header (missing right part of the msgid as specified in [1]),
which causes erratic behavior from other participants (the gmail smtp
servers for example just rewrite the message id to indicate it is
malformed,
Hi Hartmut,
Hartmut Goebel writes:
> Anyhow, all of this has been discussed several times already. And as
> long as vocal (and active :-) members of the community insist on being
> able to work via e-mail — while also not adopting modern e-mail-capable
> forges — this situation will not chang
Hi Giovanni,
Giovanni Biscuolo writes:
> Sorry I don't understand the problem, could you expand please?
>
> The guix (and daemon) versione are those of the channel used when
> creating the install .iso image; booting the 1.40 installer we get a
> "guix version" and "guix describe" value of 989a3
Hi Steve,
Quoting Steve George (2024-02-06 11:17:42)
> Ludo said they put them into this repo:
>
> https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/guix-days-2024
>
> Do you have access to this? (I do not).
No. I mean, I can read it, but that’s it.
> We can ask people on the ch
Hi Tanguy,
On 06/02/2024 08:19, Tanguy LE CARROUR wrote:
(...)
Quoting Pjotr Prins (2024-02-06 08:39:25)
It would also be nice to write a BLOG about what was discussed at Guix
days
I have notes about what sessions took place during the Guix days.
I was planning to send (tomorrow?) a patch for
Hi,
Sounds good.
A blog post for the main Guix web site, with links to the detailed notes
that were collected.
Ludo told me the raw notes are being collected here:
https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/guix-days-2024
Thanks,
Steve
On 06/02/2024 07:39, Pjotr Prins
Quoting Pjotr Prins (2024-02-06 09:48:42)
> On Tue, Feb 06, 2024 at 09:19:15AM +0100, Tanguy LE CARROUR wrote:
> > I have notes about what sessions took place during the Guix days.
> […]
> That is great. We can link out to notes hosted elsewhere.
**SPOILER ALERT** … WIP!
```markdown
# Guix Days 2
On Tue, Feb 06, 2024 at 09:19:15AM +0100, Tanguy LE CARROUR wrote:
> Hi Pjotr,
>
>
> Quoting Pjotr Prins (2024-02-06 08:39:25)
> > It would also be nice to write a BLOG about what was discussed at Guix
> > days
>
> I have notes about what sessions took place during the Guix days.
> I was plannin
Hi Pjotr,
Quoting pjotr.publi...@thebird.nl (2024-02-06 08:48:56)
> We had a very interesting discussion about the Hurd.
Very interesting, indeed! 10+ persons in a room talking about Hurd!
I guess that hadn’t happened in a long time! 😉
On my side, I decided to start patching broken packages… ag
Hi Pjotr,
Quoting Pjotr Prins (2024-02-06 08:39:25)
> It would also be nice to write a BLOG about what was discussed at Guix
> days
I have notes about what sessions took place during the Guix days.
I was planning to send (tomorrow?) a patch for the Guix Foundation website
to make it available, l
38 matches
Mail list logo
