Hi Mark,
Mark H Weaver writes:
> Hi Pierre,
>
> Pierre Langlois writes:
>
>> [...] However, it mentions that `emacs-seq` has been
>> included in emacs proper for a while.
>>
>> So, what would be the best fix for this? Should we remove `emacs-seq`
>> en
Hi Mark,
Replying with the bug on CC, I didn't realise your last email didn't
include it. I assume that was a mistake?
Mark H Weaver writes:
> Hi Pierre,
>
> Pierre Langlois writes:
>
>> Mark H Weaver writes:
>>
>>> If 'emacs-seq' is include
Hi Vitaly
Vitaliy Shatrov writes:
> Hello Guixes.
>
> OK, picture: webkitgtk has propagated-input libsoup
> libsoup has native-input php
>
> The libsoup builds fine, but one of its tests (performed by php) fails.
That sounds familiar, I think I hit this issue a few weeks
b
Hello Guix!
I'm afraid I broke r-v8 and a few of its dependants by updating node,
sorry about that!
AFAIK, the new node uses a function from nghttp2 1.41 that's not present
in 1.40, `nghttp2_option_set_max_settings'. However, since curl depends
on nghttp2 we've grafted 1.40 -> 1.41 to avoid a ful
Hi Mark,
Mark H Weaver writes:
> Hi Pierre,
>
> I'm quoting your message out of order to ease my reply.
>
> Pierre Langlois writes:
>
>> I'm afraid I broke r-v8 and a few of its dependants by updating node,
>> sorry about that!
> [...]
>> I&#x
Mark H Weaver writes:
> Hi Pierre,
>
> Pierre Langlois writes:
>
>> Mark H Weaver writes:
>>
>>> One possible solution might be to update the replacement (graft) for
>>> _curl_ so that it's *built* against nghttp2-1.41. Something like this
>
Hi Mark,
Mark H Weaver writes:
> Hi Pierre,
>
> Your new patch looks good to me, but the node-10.22 source field could
> be simplified to avoid repeating the unchanged field (especially the
> snippet), by inheriting from (package-source node) like this:
>
> --8<---cut here
Hi Martin,
Sorry this not working for you :-/
Martin Becze writes:
> emacs-next recently broke. It now has this error on start up.
>
> "require: Cannot open load file: No such file or directory, seq"
>
> I think this must have happened relatively recently (with the last 3
> weeks) since it was w
Hi Tobias,
Tobias Geerinckx-Rice via Bug reports for GNU Guix writes:
> Guix,
>
> ‘readmsg’ from mailutils@3.10 segfaults on aarch64, blocking
> ‘emacs’
> and ‘emacs-no-x’, but not ‘emacs-minimal’.
>
> --- ./readmsg/tests/testsuite.dir/4/testsuite.log
> ---
>
> #
Pierre Langlois writes:
> Hi Tobias,
>
> Tobias Geerinckx-Rice via Bug reports for GNU Guix writes:
>
>> Guix,
>>
>> ‘readmsg’ from mailutils@3.10 segfaults on aarch64, blocking
>> ‘emacs’
>> and ‘emacs-no-x’, but not ‘emacs-minimal’.
>>
>
Hi Ludo,
Ludovic Courtès writes:
> Hi Pierre,
>
> Well done!
>
> Pierre Langlois skribis:
>
>> From 0aac8082acd0c19a2d991376c7527053e196a1fd Mon Sep 17 00:00:00 2001
>> From: Pierre Langlois
>> Date: Sun, 13 Sep 2020 13:02:52 +0100
>> Subject: [PATCH
Hi Morgan,
morgan.j.sm...@outlook.com writes:
> From: Morgan Smith
>
> * gnu/packages/emacs.scm (emacs):
> [strip-double-wrap] Modify to work with emacs-next
>
> * gnu/packages/emacs.scm (emacs-next):
> [version] Change version from 28.0.50.1 to 28.0.50
> [arguments] Removed field
> [native-sear
Hi!
Marinus Savoritias writes:
> I update Guix yesterday and org-mode doesn't load anymore.
>
> The debug trace is this:
>
> Debugger entered--Lisp error: (error "Invalid version syntax: ‘’ (must start
> with a number)")
> signal(error ("Invalid version syntax: ‘’ (must start with a number)"))
Pierre Langlois writes:
> Hi!
>
> Marinus Savoritias writes:
>
>> I update Guix yesterday and org-mode doesn't load anymore.
>>
>> The debug trace is this:
>>
>> Debugger entered--Lisp error: (error "Invalid version syntax: ‘’ (must start
>
Pierre Langlois writes:
> Pierre Langlois writes:
>
>> Hi!
>>
>> Marinus Savoritias writes:
>>
>>> I update Guix yesterday and org-mode doesn't load anymore.
>>>
>>> The debug trace is this:
>>>
>>> Debugger enter
Nicolas Goaziou writes:
> Hello,
>
> Pierre Langlois writes:
>
>> In the meantime, we can either revert the update or just fix it
>> downstream temporarily. The following patch works for me for example:
>>
>> diff --git a/gnu/packages/emacs-xyz.scm b
Hello!
qblade via Bug reports for GNU Guix writes:
> after this commit, the `virsh` does not work corrent:
>
> ```
> commit 383b02a370252c08eb1d43ac94d659c1d3993a35
> Author: Pierre Langlois
> Date: Sat Mar 20 21:31:22 2021 +
>
> gnu: libvirt: Update to 7.1.0
Pierre Langlois writes:
> Hello!
(snip)
> I'll see if I can look into it at the weekend, although I'm not sure
> I'll be able to get to it, so in the meantime we should probably just
> revert the updates. Thanks a lot for investigating though, I think we
> oug
Hi Ludo,
Ludovic Courtès writes:
> Hi Pierre,
>
> Pierre Langlois skribis:
>
>> I'll see if I can look into it at the weekend, although I'm not sure
>> I'll be able to get to it, so in the meantime we should probably just
>> revert the updates. Than
Hello,
divoplade writes:
> Hello,
>
> I tried to add my comment to issue 31365, but it has been archived and
> made read-only.
>
> This issue is not fully fixed. I’m using gnome-boxes to create virtual
> machines, and I noticed something similar to what is experienced in
> this issue.
>
> The har
divoplade writes:
> Le lundi 05 avril 2021 à 19:45 +0100, Pierre Langlois a écrit :
>> Do you know at which guix commit this happened? I'm wondering which
>> version of libvirt triggered this. AFAICT, right now, if you create
>> a
>> fresh VM using gnome-boxe
Hello!
Christopher Lemmer Webber writes:
> Ludovic Courtès writes:
>
>> Hi,
>>
>> Christopher Lemmer Webber skribis:
>>
>>> It seems to me that StumpWM broke somehow, for some reason. I can
>>> confirm there was a version change:
>>>
>>> -sbcl-stumpwm@18.05:out
>>> /gnu/store/i0picr2xr2
Alex Kost writes:
> Pierre Langlois (2018-12-18 17:34 +) wrote:
>
>> Hello!
>>
>> Christopher Lemmer Webber writes:
>>
>>> Ludovic Courtès writes:
>>>
>>>> Hi,
>>>>
>>>> Christopher Lemmer Webber sk
Christopher Lemmer Webber writes:
> Christopher Lemmer Webber writes:
>
>> Pierre Langlois writes:
>>
>>> Alex Kost writes:
>>>
>>>> I have built stumpwm from the latest commit (which is one commit after
>>>> 18.11 release) and tri
Hello!
Ludovic Courtès writes:
> Hello,
>
> On berlin, Rust 1.24.1 builds systematically exceed the timeout:
>
> --8<---cut here---start->8---
> Building stage1 compiler artifacts (x86_64-unknown-linux-gnu ->
> x86_64-unknown-linux-gnu)
>Compiling arena v0
Hello Guix!
It looks like the hash for the new rust 1.36 is wrong, I get the following:
~~~
$ guix build rust
building
/gnu/store/37wfhzp1yqm9w4vq0dhmy6bg3ajaa9yh-rustc-1.36.0-src.tar.gz.drv...
Starting download of
/gnu/store/jm9xvf6qy4zxkb7rkmpz8ygf55l8v8v5-rustc-1.36.0-src.tar.gz
>From https
Thanks Tobias for fixing this!
Pierre
Hi Marius,
Marius Bakke writes:
> Berlin fails to build "linux-libre" for AArch64 on the 'core-updates'
> branch. Here is a recent attempt:
>
> https://ci.guix.gnu.org/build/1758844/details
>
> Log file for the latest build:
>
> https://ci.guix.gnu.org/log/aq2rnrmjsgnyk8vmsm7aa3mgdj39dcwh-linux-
Hello Guix!
I tried to add (service colord-service) to my config and I got a
error back :-(. I reduced my system to the minimum but the problem is
persist.
Here's the backtrace I get with the colord-system.scm config attached:
```
$ guix system build colord-system.scm
(snip)
27692 entries proces
Pierre Langlois writes:
> Hello Guix!
>
> I tried to add (service colord-service) to my config and I got a
> error back :-(. I reduced my system to the minimum but the problem is
> persist.
>
> Here's the backtrace I get with the colord-system.scm config attached:
Pierre Langlois writes:
> (use-modules
> (gnu bootloader grub)
> (gnu bootloader)
> (gnu services desktop)
> (gnu system file-systems))
>
> (operating-system
> (host-name "hello")
> (bootloader (bootloader-configuration
>
Hi Ludo,
Ludovic Courtès writes:
> Hi Jack and all,
>
> Ludovic Courtès skribis:
>
>> Jack Hill skribis:
>
> [...]
>
>>> I did spot another issue with colord since the recent core-updates
>>> merge: https://issues.guix.gnu.org/issue/37843 It seems like it is no
>>> longer being started automati
Hi Guix!
After updating the system, the dovecot service got confused and started
moving around all mailboxes. I looked up the configuration and noticed
strange invalid syntax for the location field:
--8<---cut here---start->8---
location=#< file: "path/to/conf
Hi,
Maxim Cournoyer writes:
> Hi,
>
> Ludovic Courtès writes:
>
>> Hi,
>>
>> Pierre Langlois skribis:
>>
>>> After updating the system, the dovecot service got confused and started
>>> moving around all mailboxes. I looked up the config
Maxim Cournoyer writes:
> Hi Pierre,
>
> Pierre Langlois writes:
>
>> Hi Guix!
>>
>> After updating the system, the dovecot service got confused and started
>> moving around all mailboxes. I looked up the configuration and noticed
>> str
Pierre Langlois writes:
> [[PGP Signed Part:Undecided]]
>
> Maxim Cournoyer writes:
>
>> Hi Pierre,
>>
>> Pierre Langlois writes:
>>
>>> Hi Guix!
>>>
>>> After updating the system, the dovecot service got confused and started
>
Pierre Langlois writes:
> [[PGP Signed Part:Undecided]]
>
> Pierre Langlois writes:
>
>> [[PGP Signed Part:Undecided]]
>>
>> Maxim Cournoyer writes:
>>
>>> Hi Pierre,
>>>
>>> Pierre Langlois writes:
>>>
>>>>
Hi Maxim,
Maxim Cournoyer writes:
[...]
Yeah I'm afraid I still see the same issue after a `git pull` just now:
~/code/guix [env]$ ./pre-inst-env guix system build -e '(@@ (gnu tests
mail) %dovecot-os)'
/gnu/store/ayfvf5s561q955kv8wrkklrvq3ga3qpy-system
~/code/gui
Hi Maxim,
Maxim Cournoyer writes:
> Hi Ludovic,
>
> Ludovic Courtès writes:
>
>> Hi,
>>
>> Maxim Cournoyer skribis:
>>
> The issue seems to be with the serialization of the
> object nested in the
> record. I tried this at the REPL:
>
> scheme@(guile-user)> ,m (gnu servic
Hi all!
As suggested by mirai off-list, it would be nice to have a test that
would have caught the issue. How do people feel about something along
the following patch? The idea is to use namespaces in the dovecot config
to declare the INBOX and another additional mailbox.
The bug is quite obscure
's fair for that function expect the arch to be valid (why
would you ask the config for an unsupported arch?).
I think it should be possible to fix this by checking the arch is
supported at the call site:
signature.asc
Description: PGP signature
>From 77829140f14928e30cbe4e53c625be3ba2f5895f Mon Sep 17
Pierre Langlois writes:
(snip)
> What seems to happen is that the `kernel-config' function now receive an
> `arch' argument for an architecture that isn't actually supported by
> that kernel, as is the case for linux-libre@4.14.300. And, correctly,
> the function sh
Pierre Langlois writes:
(snip)
> I'm currently trying this fix to make sure it does solve the problem
> (guix pull takes so long without substitutes :-) ). Will report back in
> 5-10 minutes.
Yeey the fixed worked!
signature.asc
Description: PGP signature
Hi Maxim,
guix-comm...@gnu.org writes:
> This is an automated email from the git hooks/post-receive script.
>
> apteryx pushed a commit to branch master
> in repository guix.
>
> The following commit(s) were added to refs/heads/master by this push:
> new 0ffa501f2b Revert "gnu: make-linux-li
Maxim Cournoyer writes:
> Hi Pierre,
>
> Pierre Langlois writes:
>
>> Hi Maxim,
>>
>> guix-comm...@gnu.org writes:
>>
>>> This is an automated email from the git hooks/post-receive script.
>>>
>>> apteryx pushed a commit to branc
Hi Guix!
There seems to be a bug with the --network flag to `guix system
container', if we try to use docker-image.tmpl as an example we get the
following failure:
--8<---cut here---start->8---
$ sudo `guix system container -v3 --network
gnu/system/examples/do
Pierre Langlois writes:
> [[PGP Signed Part:Undecided]]
> Hi Guix!
>
> There seems to be a bug with the --network flag to `guix system
> container', if we try to use docker-image.tmpl as an example we get the
> following failure:
>
> $ sudo `guix system containe
t, are you happy with the
patch attached?
Thanks,
Pierre
signature.asc
Description: PGP signature
>From f3c647bb447706f465a3fb4b8d6e09cd089dbed9 Mon Sep 17 00:00:00 2001
From: Pierre Langlois
Date: Sat, 8 May 2021 16:19:23 +0100
Subject: [PATCH 1/3] gnu: u-boot-rockpro64-rk3399: Disable USB bo
Hi Vagrant,
I just had a break-through with this! See inline.
Vagrant Cascadian writes:
> On 2021-07-13, Pierre Langlois wrote:
>> I'm afraid since commit 3a851d45576e046d696fcf35b34d57b2cd28ea49 [0]
>> I've not been able to boot from eMMC on the rockpro64 board, it
Whoops, I hadn't realised the bug email wasn't included in the email,
sorry!
Pierre Langlois writes:
> Hi Vagrant,
>
> I just had a break-through with this! See inline.
>
> Vagrant Cascadian writes:
>
>> On 2021-07-13, Pierre Langlois
Hi Guix!
Pierre Langlois writes:
> [[PGP Signed Part:Undecided]]
> Hi Vagrant,
>
> I just had a break-through with this! See inline.
(snip)
From 055d1d358c55811cafd4c56b919865b75e59d936 Mon Sep 17 00:00:00 2001
From: Pierre Langlois
Date: Tue, 27 Jul 2021 20:15:55 +0100
Subject:
Hi,
Katherine Cox-Buday writes:
> It looks like it expects a ~/test.org file to be present and prompts for user
> input when that is not the case.
Yeah I noticed that as well :-/, I took a quick look at and the tests
can be enabled properly with this commit:
https://github.com/alphapapa/org-su
Hi Chris,
Chris Marusich writes:
> [[PGP Signed Part:Undecided]]
> Hi Aiko and Leo,
>
> Aiko Kyle writes:
>
>> It would be great to get this upstreamed soon so I can start guix
>> pulling master. I think the guix commit and revision in
>> package-management.scm will also need to be bumped after
Hi there,
raid5atemyhomework via Bug reports for GNU Guix writes:
>> > > Eog and Epiphany should be fixed with Guix at
>> > > f7afefba00b65e94d073af3af2278a076c89dbc1 or later.
>> >
>> > Ha, it seems I'm late to the party. Thanks Guillaume! Will check.
>>
>> Unfortunately it seems to still be br
unblock the guix package then the farm might catch other
issues that could help getting to the bottom of this.
WDYT?
Thanks,
Pierre
signature.asc
Description: PGP signature
From cdd2c995b7c03400a9702a6b354655b0584b727c Mon Sep 17 00:00:00 2001
From: Pierre Langlois
Date: Wed, 22 Dec 2021 22:0
Hi,
Chris Marusich writes:
> [[PGP Signed Part:Undecided]]
> Hi,
>
> Chris Marusich writes:
>
>> If nobody has further comments, I will commit the attached version to
>> master in about 24 hours.
>
> I've committed this in 24c3485bb3ffc05e687ef6513ac287b8d3048bab. We
> still need to update the
Hi Leo,
Leo Famulari writes:
> On Wed, Jan 19, 2022 at 11:28:28AM -0800, Vagrant Cascadian wrote:
>> I tried building a newer version, but there were new test suite failures
>> on both aarch64 and x86_64 :/
>
> Since the 'guix' package still does not build on aarch64, I'm reopening
> this bug.
Leo Famulari writes:
> On Sat, Jan 29, 2022 at 08:54:24PM +0000, Pierre Langlois wrote:
>> > Since the 'guix' package still does not build on aarch64, I'm reopening
>> > this bug.
>>
>> Oh it doesn't? What hash are you on?
>
>
Hi there,
Maxime Devos writes:
> [[PGP Signed Part:Undecided]]
> I took a look but I don't know what's up with
>
>> g++ [...] -o cc1 [...]
>> collect2: fatal error: ld terminated with signal 9 [Killed]
>
> Seems like the linking step failed somehow?
I would guess that the build ran out of memo
Hi,
"D. Birch" writes:
> Thank-you for all the help.
>
> I left the laptop ticking away again after adding 10G of swap.
>
> I've attached the stdout and stderr, as before.
>
> Things got much further and the system was building for the whole day, I left
> it running overnight and in the morning
Hi Nicolas, hello Guix!
I just noticed the last update to the emacs-ivy package removed
swiper.el from the package by moving from github to elpa. It seems elpa
packages ivy and swiper separately
(https://elpa.gnu.org/packages/swiper.html).
I don't have time to submit a patch to fix it at the mome
Pierre Langlois writes:
> Hi Nicolas, hello Guix!
>
> I just noticed the last update to the emacs-ivy package removed
> swiper.el from the package by moving from github to elpa. It seems elpa
> packages ivy and swiper separately
> (https://elpa.gnu.org/packages/swiper.html)
Nicolas Goaziou writes:
> Hello,
>
> Pierre Langlois writes:
>
>> I just noticed the last update to the emacs-ivy package removed
>> swiper.el from the package by moving from github to elpa. It seems elpa
>> packages ivy and swiper separately
>> (https
Nicolas Goaziou writes:
> Pierre Langlois writes:
>
>> Nice, thanks for the quick fix! Originally I noticed this because of the
>> emacs-lispy package failing to build. Here's a patch to add
>> `emacs-swiper` as a dependency to fix it.
>>
>> I suspect
Hello Guix!
Since switching to emacs 27 I've been having issues starting it, seeing
lots of errors like 'Lisp nesting exceeds ‘max-lisp-eval-depth’' when
loading various packages such as magit, ivy, ...etc.
After quite a bit of troubleshooting I reduced it to the `emacs-seq`
package. So if you cr
h it in a
minute.
signature.asc
Description: PGP signature
>From 42fbe62d52a82d1003c3d7039d3c4a46806c5cee Mon Sep 17 00:00:00 2001
Message-Id: <42fbe62d52a82d1003c3d7039d3c4a46806c5cee.1679836531.git.pierre.langl...@gmx.com>
From: Pierre Langlois
Date: Sun, 26 Mar 2023 13:55:14 +0100
Pierre Langlois writes:
> [[PGP Signed Part:Undecided]]
> Hi Arun and Bruno,
>
> Arun Isaac writes:
>
>>> I'm inclined to keep it in %network-configuration-files just to be
>>> safe.
>>
>> I agree. I don't really understand the implication
67 matches
Mail list logo
