Re: emacs-next periodic updates

[Gabriel Santos]

>Yeah, so our options are building the xwidget emacs without webkit

Is this possible? I think that WebKit is a requirement.

- 
- 


>dropping it entirely.

That seems to be more likely.

Regards,

--
Gabriel Santos

[Shepherd] Disappearing timer

[Development of GNU Guix and the GNU System distribution.]

Hi,

My timer join-irc-channels [1] starts when being 'deployed' but is gone
after a reboot, even though the Shepherd configuration includes a
reference to it. [2]  There is no trace:

# herd status join-irc-channels
herd: error: service 'join-irc-channels' could not be found

The system generation was updated properly.  Any ideas are welcome.

Thanks,
Felix

P.S. Do I need to start services explicitly when they appear in
another's 'requirements'?

[1] 
https://codeberg.org/lechner/system-config/src/commit/b754f05d19d8fafb8027ef90a62e582689f0b365/host/wallace-server/operating-system.scm#L2271
[2] https://paste.mozilla.org/7VFW0Vo2

Re: Debbugs changes on #guix

[Ian Eure]

Hi Felix, Guixers,

Felix Lechner via "Development of GNU Guix and the GNU System 
distribution."  writes:



Hi,

I enabled an experimental barebones feature that broadcasts 
Debbugs
changes on #guix.  It's another technical feature that could 
improve the

speed at which bugs are being closed.

Please let me know what you think!



Reiterating what I said in IRC:

I think the bot messages have value, but the value is subjective. 
To regular Guix users, they have more value, and to those looking 
for help with problems, they have less.


Becasue of this, I think the messages need to be opt-in.  The 
simplest way to do that is to put them in a separate channel, 
which those who want to see the messages can join.  I could see 
posting in #guix for uncommon, exceptional, and/or important 
cases, such as new bugs with grave severity being filed (or 
existing bugs upgraded to grave severity).


Thanks,

 -- Ian

Re: [fr] Moment de convivialité Guix@Paris en mars

[Tanguy Le Carrour]

(Warning: this email is in french because the meeting is supposed
to be held in French… and in person.)


Bonjour Guix,


On Wed Mar 5, 2025 at 12:16 PM CET, Tanguy Le Carrour wrote:
> Jeudi 20 mars à 19h se tiendra la sixième soirée de la 3ème saison
> des rencontres Guix à Paris.

Petit rappel de dernière minute : Guix@Paris, c’est aujourd’hui ! 😁

Bonne journée et… à ce soir !

-- 
Tanguy

Re: Guix on the MNT/Reform

[Denis 'GNUtoo' Carikli]

On Tue, 18 Mar 2025 08:38:02 -0400
Christine Lemmer-Webber  wrote:

> The modularity of the Reform design is the most hope I have for a FOSS
> future on the otherwise largely dystopian direction of hardware
> lately. Hopefully we will get better and better options over time for
> the SoCs too.

It's also repairable so if there is enough interest people could work
on it during years for instance to make one of the hardware combination
boot with fully free software.

Denis.


pgpwZTLy2A5Y3.pgp
Description: OpenPGP digital signature

[Shepherd] Skipping a beat

[Development of GNU Guix and the GNU System distribution.]

Hi,

Should #:wait-for-termination? be called #:skip-when-running?

The name captures that beats are missed when a process has not yet
terminated.  Due the connection with time, "when" is better than "if".

Kind regards
Felix

Re: Guix on the MNT/Reform

[pelzflorian (Florian Pelz)]

Thank you Denis for the info!

Denis 'GNUtoo' Carikli  writes:
> For DDR3 you need to do training to precisely configure the delays to
> have good performances, […]
> Basically delays tell the RAM controller how much time it needs to wait
> for all the signals to have arrived.

So at least for DDR3 the problem is not adjusting for cross-talk but
waiting not longer than a specific hardware’s propagation delay?


> neox also wrote a paper on DDR3 RAM initialization for the KGPE-D16 but
> it's not public yet (and it needs some improvements as well), so if you
> want to help review it you need to write to him. Once released, it will
> be published under one or more free licenses.

Interesting, but I am unable to type efficiently and lack time to help
inefficiently.  I hope others help or benefit from your knowledge.

Regards,
Florian

Re: Thoughtful updates to TexLive

[Andreas Enge]

Hello Nicolas,

Am Wed, Jan 22, 2025 at 04:20:01PM +0100 schrieb Nicolas Goaziou:
> FWIW, I think texlive-scheme-* packages are opinionated collections that
> have no other purpose than recreating past TeX distributions. One should
> only rely on texlive-collection-* packages.
> What collection to elect is another topic. If space is not an issue, and
> you don’t want to bother with optimized dependencies,
> texlive-collection-latexextra (1GB, around 1.4k packages) provides
> almost everything needed to compile LaTeX documents, including PGF/TikZ
> (no PSTricks, that’s in another collection). You may also want to add
> texlive-babel-XXX for non-English languages.

thanks for your helpful suggestions! I think here again latency for
downloading a lot of packages is an issue. In the end I gave the
following a try: texlive-collection-latex,
texlive-collection-latexrecommended, texlive-collection-xetex,
texlive-babel, texlive-babel-{english,french,german},
plus a few eclectic packages I happen to use.

For compiling a set of slides of a talk, now time is an issue:
real0m36,095s
user0m13,706s
sys 0m22,710s

With the monolithic texlive:
real0m9,127s
user0m9,260s
sys 0m0,613s
(which is already a lot when one has to recompile every time after
making a small change).

This looks a lot like https://issues.guix.gnu.org/75893 .
I should test with your fix on the tex-team branch.

Andreas

Re: Thoughtful updates to TexLive

[Development of GNU Guix and the GNU System distribution.]

Hello,

Andreas Enge  writes:

> For compiling a set of slides of a talk, now time is an issue:
> real  0m36,095s
> user  0m13,706s
> sys   0m22,710s
>
> With the monolithic texlive:
> real  0m9,127s
> user  0m9,260s
> sys   0m0,613s
> (which is already a lot when one has to recompile every time after
> making a small change).
>
> This looks a lot like https://issues.guix.gnu.org/75893 .
> I should test with your fix on the tex-team branch.

I would indeed appreciate some feedback!

Regards,
-- 
Nicolas Goaziou