eport.
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
useful and I have applied them to my local
copy of test-driver.scm file. Feel free to apply them, or ignore them, as you
see fit.
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
From
Hello Ludo',
On 2024-07-18 17:34:08 +0200, Ludovic Courtès wrote:
> Hi Tomas,
>
> Tomas Volf <~@wolfsden.cz> skribis:
>
> > when I try to use the above, it returns wrong module. The module returned
> > is
> > prefixed by #{.}# symbol. Full r
ant parts (I
assume at least bootloader, file-systems and mapped-devices fields)?
I would like to properly understand the problem here and why it works for me.
Thanks,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
si
On 2024-07-31 19:10:03 +0200, Liliana Marie Prikler wrote:
> The other (recommended at the moment) would be to use the proper
> transformation to natively compile your emacs packages.
So just to make sure I understand correctly what is the correct work around
here. Let us assume I install emacs a
The emacs-yaml package is configured to build against emacs-minimal,
which seems to work. When you however switch to emacs package, it takes
way to long to build, much longer than compiling for example firefox
package. That feels off.
--8<---cut here---start-
Hello,
Ian Eure writes:
> Disregard this, I continued thinking after sending the email (as one does) and
> realized that any managed file will be a link into the store -- so if the
> system
> is reconfigured with no build-machines or channels *and* the corresponding
> file
> is a store link,
his cannot be handled correctly, it would be great if it at least
failed with an error instead of a silent corruption.
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
Hi,
I think the patch is wrong. No comment regarding the udev rule itself (I do
not know much about it), it does spam the logs with:
Oct 31 18:31:35 localhost vmunix: [ 60.013538] udevd[327]: invalid key/value
pair in file
/gnu/store/a3xvv1zxzyb53r5r752q8nh9v9vd150h-udev-rules/69-dm-lvm.rul
id=28861 . On the page there is
also a workaround, and that is to compile with the locales with -c.
So that would be one solution until we update to 2.36 or higher. I do not see a
way to override this (add the -c) from the operating-system definition.
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
On 2023-11-27 23:02:26 +0100, Ludovic Courtès wrote:
> Hi Tomas!
Hi! :)
>
> Tomas Volf <~@wolfsden.cz> skribis:
>
> > when trying to build a system with C.utf8 locale, I end up with the
> > following
> > error:
> >
> > building /gnu/store/
Hi :)
On 2023-12-07 11:27:04 +0100, Ludovic Courtès wrote:
> [..]
>
> I decided to give it a go:
>
> https://issues.guix.gnu.org/67686
>
> Please do chime in and let me know what you think!
Thanks to the detailed cover letter, now I understand the benefit, so I agree it
would make sense. I loo
On 2023-12-09 15:46:58 +0100, Ludovic Courtès wrote:
> > I still believe it makes sense to add the -c also into the locale builder,
> > because my understanding is that this change will not allow using (locale
> > "C.utf8") in the operating-system definition (since that would still try to
> > build
it, it was quite messy. I wonder if having just a single
ovmf package would simplify things. The size bloat from merging them
seems... negligible. At least for the QEMU use case.
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things
Superseded by #68394.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
On 2024-01-12 17:02:37 +0100, Simon Tournier wrote:
> [..]
>
> It is a known time-bomb. For now we do not have better other than
> hard-code the time. On my machine, I do:
>
> [..]
Thank you very much for the explanation. :)
Have a nice day,
Tomas Volf
--
There are only
Hello,
when Guix machine is shutting down, it keeps waiting for PID associated with
[mt76-tx phy0] to terminate. Since it is a kernel thread, it does not happen.
Previous discussion on this bug was done via email, and is copied here:
Date: Sun, 7 Jan 2024 15:59:51 +0100
From: Tomas Volf
> Date: Mon, 29 Jan 2024 17:31:33 +0100
> From: Ludovic Courtès
> To: guix-de...@gnu.org
> Subject: Re: GNU Shepherd 0.10.3 released
>
> Hi,
>
> Tomas Volf <~@wolfsden.cz> skribis:
>
> > Ah, that code indeed returns #f for the pid in question:
> >
it to reproducibility).
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
Hello,
I have noticed that despite the pre-push hook having a `while' loop to read all
the refs, it calls exec/exit on the very first one. Effectively that means that
only the first ref is checked, the rest is assumed to be authenticated. That
seems wrong.
Have a nice day,
Tomas Volf
--
Hello,
the pre-push hook just calls `make authenticate check-channel-news' without any
attempt to actually switch to the ref that it should check. This means it
always authenticates HEAD, not the ref being pushed. That seems wrong.
Have a nice day,
Tomas Volf
--
There are only two hard t
ached-checkout _ #:ref _ #:recursive? _ # _ # _ …)
>281:19 4 (resolve _)
> In git/reference.scm:
> 60:8 3 (_ _ _)
> In git/bindings.scm:
> 77:2 2 (raise-git-error _)
> In ice-9/boot-9.scm:
> 1685:16 1 (raise-exception _ #:continuable? _)
> 1683:16 0 (raise-exception _ #:continuable? _)
>
> ice-9/boot-9.scm:1683:16: In procedure raise-exception:
> Git error: reference 'refs/tags/v1.3.1' not found
>
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
'guile-colorized' package
+for a colorful Guile experience.\n\n\"\n"))
(define %default-skeleton-home-config
(plain-file "default-home-config" "\
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
Hello,
when I try to compile Guix
guix shell -CWND guix -- ./bootstrap
guix shell -CWND guix -- ./configure --localstatedir=/var --sysconfdir=/etc
guix shell -CWND guix -- make -j16
I get the following error:
[ 91%] GUILEC gnu/build/dbus-service.go
;;; Failed to autoload d
7xq0fw08kv30-texinfo-7.0.3/share/texinfo/Texinfo/Convert/ParagraphNonXS.pm
line 298, <$fh> line 8.
Am I doing something wrong or is this expected?
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
the /lib/modules subdirectory, it just chokes down
the line on something else.
I think it would be best to just support (kernel #f) for container deployments,
since that would simplify it and keep it manageable.
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
Hi,
On 2024-04-08 14:28:58 +0200, Ludovic Courtès wrote:
> [..]
>
> Could you confirm?
Yes, the attached patch fixed the issue for me. :)
>
> > I think it would be best to just support (kernel #f) for container
> > deployments,
> > since that would simplify it and keep it manageable.
>
> Yes, l
link.rst] Error 1
make[2]: *** [Documentation/Makefile:111:
Documentation/networking/netlink_spec/tc.rst] Error 1
make[1]: ***
[/tmp/guix-build-linux-libre-documentation-6.8.4.drv-0/linux-6.8.4/Makefile:1705:
infodocs] Error 2
make: *** [Makefile:240: __sub-make] Error 2
How are these not caught in the CI?
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
On 2024-04-10 23:12:43 -0400, Leo Famulari wrote:
> On Wed, Apr 10, 2024 at 05:05:15PM +0200, Tomas Volf wrote:
> > linux-libre-documentation is broken again:
> >
> > starting phase `build'
> > Traceback (most recent call last):
> >
pk (sigaction SIGPIPE))'
;;; ((0 . 0))
--8<---cut here---end--->8---
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
Code in `ui.scm' in `initialize-guix' procedure changes the handling of
SIGPIPE to SIG_IGN. So restore the handling to SIG_DFL so that process
executed will have the usual action. Technically we should record what the
handling was, and restore it to the previous value, but that would be much
more
The documentation for `with-extensions' says:
> In the same vein, sometimes you want to import not just pure-Scheme
> modules, but also “extensions” such as Guile bindings to C libraries
> or other “full-blown” packages.
However it does not actually add those C libraries into
(guile-extensions-p
Hello,
thank you for CC-ing me.
Jelle Licht writes:
> Addendum:
> running `herd eval root "(setsid)"` solves my particular issue, making
> ^C on my shell no longer kill my user shepherd.
Oh, that is neat. I did not realize this can be fixed like that without
modifying shepherd's source code.
Hi,
when system guix produced by the guix-for-channels procedure is
installed, modules in any channel (except in the 'guix) will shadow the
same modules acquired via `guix pull'.
Steps to reproduce:
Have a channels.scm:
--8<---cut here---start->8---
(cons (c
Hi,
I wrote a shepherd service to function as a check for networking being
actually up, but it does not get respawned when it fails and I do not
understand why.
This is the service in my operating-system:
--8<---cut here---start->8---
(simple-service
'network
Hello,
I think I found a bug in the GNU Shepherd. Dependencies between
one-shot? #t services do not seem to be respected.
Documentation for #:requirement says the following (emphasis mine):
--8<---cut here---start->8---
#:requirement is, like provision, a l
Ludovic Courtès writes:
> Hi,
>
> Tomas Volf <~@wolfsden.cz> skribis:
>
>> The documentation for `with-extensions' says:
>>
>>> In the same vein, sometimes you want to import not just pure-Scheme
>>> modules, but also “extensions” such as G
ebug it myself. Hence this report.
Have a nice day,
Tomas
;;; GNU Guix --- Functional package management for GNU
;;; Copyright © 2024 Tomas Volf <~@wolfsden.cz>
;;;
;;; This file is part of GNU Guix.
;;;
;;; GNU Guix is free software; you can redistribute it and/or modify it
;;; und
e@(guix-user)> (define-configuration test (s string ""))
scheme@(guix-user)> (test (s (pk "x")))
;;; ("x")
;;; ("x")
--8<---cut here---end--->8---
That probably is not intentional.
Have a nice day,
Tomas vol
Ludovic Courtès writes:
> Hi!
>
> Tomas Volf <~@wolfsden.cz> skribis:
>
>> When you have another login session active when you log out and in
>> again, new shepherd is *not* spawned. I am guessing here but probably
>> last log out causes XDG_RUNTIME_DIR to
I am not sure how this relates to this specific bug report, but
b...@bokr.com writes:
> I wonder how many guix-daemon-process-relationship type problems would be
> simplified
> if (radical vision) one let wayland's inner event-driven loop/protocol
> be the dispatcher
not everyone uses wayland.
Hello,
thank you for finding the time to look into this issue. Replies below.
Ludovic Courtès writes:
> Hi,
>
> Tomas Volf <~@wolfsden.cz> skribis:
>
>> I am writing a configuration for mpv and hit an issue of the generated
>> constructor (`home-mpv-configurati
Hello,
during debugging #74787, I noticed that when ran via pre-inst-env, guix
deploy does not use packages from the local git tree. I reverted the
commit da3c8a963f83c044568d99921480259eaa26a923 and applied the
following patch locally:
--8<---cut here---start---
In 0.18.0, the `open-remote-pipe*' now correctly quotes the arguments, so the
double quoting that was done by `shell-quote' is not harmful and breaks at
least offloading and deploy.
* guix/remote.scm (remote-pipe-for-gexp): Call object->string just once.
Change-Id: Id922d26d318bfdd4714e267687c1b2
The check for make-session stopped working after update to 0.18.0. This
commit adds the additional `#:config #f' to skip reading the ssh
configuration, arguably we did not want to do that anyway.
* m4/guix.m4 (GUIX_CHECK_GUILE_SSH): Add `#:config #f' to make-session call.
Change-Id: Id6ea3860292
Hello,
Simon Streit writes:
> Is there maybe an easy way around this? I tried:
>
> (connection-local-set-profile-variables
> 'remote-system
> '((tramp-remote-path . ("/bin" "/usr/bin" "/sbin" "/usr/sbin"
> "/usr/local/bin" "/usr/local/sbin" "/local/bin"
> (connection-local-set-profiles
Ludovic Courtès writes:
> Hello,
>
> Jake skribis:
>
>> I think I'm experiencing a bug in Shepherd since version 1.0.
>> Whenever I log out and log back in again, my user shepherd from the
>> previous login session is still present, and a new user shepherd spawns for
>> the current login session
Hi,
Dariqq writes:
> Are the (or port 22) clauses in guix/scripts/copy.scm still neccesary?
>
> From my limited testing removing them fixed the problem and passing a
> port of #f will result in 22 being used.
Yeah I think you are right.
>
> This might also be a problem in other places wghere
After update to guile-ssh 0.18.0, options passed to the `make-session'
procedure now take precedence over the configuration file. In few places we
however had code like `(or port 22)' leading to (in absence of alternative
port being specified) always using port 22, ignoring the configuration file.
Hello,
Z572 writes:
>> How it that usually done? I cannot do that *before* build, because then
>> tests would not run (the library is not yet installed into the absolute
>> path), and I cannot do it after, because I would need to rebuild the .go
>> files after patching the source code.
>
> you
Maxim Cournoyer writes:
> Hi Tomas,
>
> Tomas Volf <~@wolfsden.cz> writes:
>
>> After update to guile-ssh 0.18.0, options passed to the `make-session'
>> procedure now take precedence over the configuration file. In few places we
>> however had code like
Hi Ludo',
Ludovic Courtès writes:
> Indeed. As Dariqq found out, the problem was that we’d mark one-short
> services in ‘%one-shot-services-started’ as soon as we’ve started them,
> effectively acting as if “started” were synonymous with “running”.
>
> This is fixed with 550c0370985022c5c90a7b4
* doc/htmlxref.cnf (ELPA, ELPA_DOC): New variables.
(debbugs-ug): Define `mono' version.
Change-Id: I3a914354df732ec8d2cc92d56e551ba63c723041
---
doc/htmlxref.cnf | 5 +
1 file changed, 5 insertions(+)
diff --git a/doc/htmlxref.cnf b/doc/htmlxref.cnf
index e1f3415fc0..bd7cf72db4 100644
--- a
--git a/doc/htmlxref.cnf b/doc/htmlxref.cnf
index dc819a92ad..46a396bcad 100644
--- a/doc/htmlxref.cnf
+++ b/doc/htmlxref.cnf
@@ -1,7 +1,8 @@
# htmlxref.cnf - reference file for free Texinfo manuals on the web.
# Modified by Ludovic Courtès for the GNU Guix manual.
+# Further modified by Tomas
At the same time the reference text is adjusted. I found it confusing for
link to the `Top' to be labeled `Introduction'. So let us just link to the
`Introduction', it is probably what the author intended.
* doc/htmlxref.cnf (stow): Add both mono and node versions.
* doc/guix.texi (Essential Hom
Change-Id: Idda2684864248b1ef11acff31bc145b1cbdabe9d
---
doc/htmlxref.cnf | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/htmlxref.cnf b/doc/htmlxref.cnf
index 46a396bcad..e1f3415fc0 100644
--- a/doc/htmlxref.cnf
+++ b/doc/htmlxref.cnf
@@ -5,7 +5,7 @@
htmlxrefversion
jgart via Bug reports for GNU Guix writes:
> Hmmm, yeah, I don't know the texinfo arcana to fix that either... 🦆
I took the liberty to send a patch fixing the reported issue. There are
few more remaining (in the EN manual):
--8<---cut here---start->8---
guix
45mg <45mg.wri...@gmail.com> writes:
> Hi all,
>
> Though the bug is closed, I still faced this issue. Solution was to
> explicitly install gtk+ along with libreoffice (ie. specify it in the
> 'packages' field of my home-environment declaration, in my case).
>
> I'm not sure if this is expected or
45mg <45mg.wri...@gmail.com> writes:
> Hi Tomas,
>
> Tomas Volf <~@wolfsden.cz> writes:
>
>> I have sent a series fixing the issue (/me checks the list of open
>> bugs) 1 year, 3 weeks, 2 days ago.
>
> Would you mind linking to it? I am unable to solve th
Nicolas Graves writes:
> On 2025-01-24 03:03, 45mg wrote:
>
> Seems to be issue bug#68150.
> I will review it today
Fair warning, I have not idea whether it even still applies cleanly. I
lost the will to push it after half a year or something.
T.
--
There are only two hard things in Computer
For some reason the generated configuration by `guix system deploy'
differs from the one generated by `guix system delete-generations'. The
one from `delete-generations' is missing the extra-initrd, interfering
with the boot of the system.
From `guix deploy':
--8<---cut here
--8<---cut here---start->8---
$ guix shell guile shepherd -- guile -c '(use-modules (shepherd service timer))'
Backtrace:
In ice-9/boot-9.scm:
3564:26 19 (_)
In unknown file:
18 (primitive-load-path "shepherd/service/timer" #)
In ice-9/boot-9.scm:
Hello,
when I try to configure a timer based on my legacy crontab file, I get
the following error:
--8<---cut here---start->8---
$ guix shell guile shepherd guile-fibers -- guile -c '(use-modules (shepherd
service timer)) (cron-string->calendar-event "*/15 *
When trying to use (web client) Guile module, one gets the following
error:
--8<---cut here---start->8---
$ guix shell -CN guile guile-gnutls nss-certs -- guile -c '((@ (web client)
http-get) "https://gnu.org";)'
Backtrace:
In ice-9/boot-9.scm:
1752:10 7 (w
Five asterisks (* * * * *) is a valid cron time specification, but
cron-string->calendar-event chokes one it:
--8<---cut here---start->8---
$ guix shell guile shepherd guile-fibers -- guile -c '(use-modules (shepherd
service timer)) (cron-string->calendar-even
Hi,
I have tried to write a service type for smartd from smartmontools,
however the bundled script fails.
When the test (-m root -M test) is executed, some programs seem to be
missing in the $PATH:
--8<---cut here---start->8---
Jan 14 01:34:19 localhost smar
Hello,
when I try to deploy my system, I see the following warning:
--8<---cut here---start->8---
The following derivations will be built:
/gnu/store/w8cxahgkf6xkial3pnmv4hlpqybf5bad-kexec-load-system.scm.drv
/gnu/store/7zaprr6p1w6w3bjg00ai3s0f247a7gax-remo
Maxim Cournoyer writes:
> Hello,
>
> Altadil via Bug reports for GNU Guix writes:
>
>> Hi,
>>
>> GnuCash 5.3, as packaged in Guix, cannot access quote sources. When
>> adding a new security, it displays "Warning: Finance::Quote not
>> installed properly." and the "Get Online Quotes" checkbox is
Liliana Marie Prikler writes:
> I think you're making this more complicated than it needs to be.
> checkout, authenticate, rebase*, merge* ought to have you covered.
>
> * you can authenticate after these if you're paranoid
>
>> We could create a script to do all the steps for us, but if and wh
Ricardo Wurmus writes:
> Liliana Marie Prikler writes:
>
>>> This has the slight issue that I can no longer easily answer a
>>> question "is this commit in my fork", since I cannot search by the
>>> commit hash. I admit it is not a question I need to answer often
>>> (last time was on 21st of Oc
Liliana Marie Prikler writes:
> [..]
>
>> Then there is anything modifying any of the guix commands. #74832 is
>> over month old, and as far as I know, I am not able to fix guix-copy
>> from a channel. #72928 took over a month to merge, and again, not
>> sure how to patch guix-describe from a c
Saturanya Rahjane de Lasca writes:
>> Again, not disputing that things work fine for people with commit
>> access. Perhaps that is part of why this issue hasn't been addressed
>> before :P
> You may call us privileged – and yes, we are – but that doesn't change
> the fact that weakening security
Liliana Marie Prikler writes:
>> All of these things discussed in this thread are technically
>> possible. But I think that we all agree that the friction involved,
>> compared to just using my own fork with the patch applied, is much
>> larger, at least in my opinion.
> Yes, we can agree that t
The script started with reset of the $PATH to a value not suitable to Guix.
In addition, the script requires coreutils and sed, so add those into the
$PATH.
* gnu/packages/admin.scm (smartmontools)[arguments]<#:phases>: Add 'fix-path.
Change-Id: Ide97f572e6f369fe24337f945474dc7a65584eda
---
gnu/
Hello,
thank you for the bug report.
"Murilo" via Bug reports for GNU Guix writes:
> Hi, I (and a friend too) have been getting an infinite reboot loop when trying
> to boot into guix system.
> Going back a generation fixes it, but doesn't solve the issue as I cannot
> upgrade guix any further.
Ludovic Courtès writes:
> Hi,
>
> Tomas Volf <~@wolfsden.cz> skribis:
>
>> We can see the difference boils down to different search paths:
>>
>> $ guix shell -CN guile guile-gnutls nss-certs --search-paths
>> export
>> PATH="/gnu/store/gg2qyb
Hello,
after pulling recent Guix, I got this error during guix deploy:
--8<---cut here---start->8---
guix deploy: warning: an error occurred while upgrading services on '127.0.0.1':
%exception #>
--8<---cut here---end--->8-
Hi :)
When you execute the following code:
--8<---cut here---start->8---
herd spawn transient -- $(which sh) -c 'printf x'
--8<---cut here---end--->8---
The `x' is nowhere to be found in the log:
--8<---cut he
Hi :)
Shepherd does not seem to support UTF-8 output (Japanese in my case) in
the log output. I noticed the issue with timers, but can be reproduced
with transient as well:
--8<---cut here---start->8---
$ herd spawn transient -- $(which sh) -c 'echo "猫"'
Spa
I have put together a reproducer in a VM:
1. Install Guix system using 1.4.0 installer
--> Include sshd, openbox
2. Reboot
3. Copy the /run/current-system/configuration.scm out of the VM
4. Adjust the configuration.scm (full file attached)
4.1 Allow NOPASSWD sudo
(sudoers-file
(plain-file
Simon Josefsson via Bug reports for GNU Guix writes:
> Hi
>
> It seems shepherd in Debian print the following on a simple --help:
>
> 132s warning: call to environ while multiple threads are running;
> 132s further behavior unspecified.
>
> I can't find the error message in guile-fibers
Ludovic Courtès writes:
> Hi Tomas,
>
> Tomas Volf <~@wolfsden.cz> skribis:
>
>> However that did not happen. Here are the logs:
>>
>> 2025-02-22 19:17:00 Service kerberos-log-in running with value #<
>> id: 730 command: ("/gnu/store/8m21cnqn
Ludovic Courtès writes:
> Ludovic Courtès skribis:
>
>>> 2025-02-23 12:00:02 Waiting anew for timer 'kerberos-log-in-refresh'
>>> (resuming from sleep state?).
>
> The “Waiting anew” message happens when the timer fires 2 seconds or
> more later than expected (see ‘sleep-operation/check’), whic
Ludovic Courtès writes:
> Tomas Volf <~@wolfsden.cz> skribis:
>
>> (I wonder if there is better way to detect the sleep. I feel like *any*
>> number will be wrong for someone. Do we know how for example systemd's
>> timers handle this?)
>
> I believe
Hi,
I might have find a bug in shepherd timers. I have a timer scheduled to
run every 24 hours, the definition is as follow:
--8<---cut here---start->8---
(define %kerberos-log-in-refresh-service
(let ((name 'kerberos-log-in-refresh))
(simple-service
Ludovic Courtès writes:
> Hey Tomas,
>
> Ludovic Courtès skribis:
>
>> I tried the config file you gave with:
>>
>> ./pre-inst-env guix system vm /tmp/config.scm
>>
>> and it hangs, to my surprise (I’ve been using ‘system-log’ on my laptop
>> since June, and “make check-system TESTS=basic” & c
Leo Famulari writes:
> On Sun, Mar 02, 2025 at 08:08:50PM +0100, Tomas Volf wrote:
>> Possible explanation would be that there is a bug in the descendancy
>> detection when your current Guix is on specific commits (my guesstimate
>> would be the trigger is having large c
Hello,
when using `activation-service-type' combined with `with-extension', the
various modules seem to interfere with each other.
In my case the samba-service-type interferes with my custom service:
--8<---cut here---start->8---
(define (watcher-activation* c
Leo Famulari writes:
> On Sat, Mar 01, 2025 at 11:37:40AM -0500, Jack Hill wrote:
>> guix pull: error: aborting update of channel 'guix' to commit
>> 6ca7b07a251739dfaefa639e74c01e3013c9454c, which is not a descendant of
>> f13f0769688493271f43f31a016957355dbecb30
>> hint: This could indicate t
Jack Hill writes:
> jackhill@lissome ~$ guix describe
> Generation 159 Feb 27 2025 22:08:27(current)
> guix f13f076
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: f13f0769688493271f43f31a016957355dbecb30
> jackhill@lissome ~$ guix pull
>
Ludovic Courtès writes:
> Hi,
>
> Tomas Volf <~@wolfsden.cz> skribis:
>
>> I have no idea how Shepherd works internally (and much less how Fibers
>> work), so maybe this comment is completely off, but this seems
>> suspicious. Should this lambda not
Ludovic Courtès writes:
> [..]
>
> Another thing I had in mind was to use an elogind hook so that shepherd
> would know when we’re suspending; this is necessary for other things
> such as locking LUKS devices on suspend. But that’s a change for 1.1.x.
I see two possible problem here (both solva
Hilton Chain writes:
> Hi Tomas,
>
> On Mon, 03 Mar 2025 09:02:22 +0800,
> Tomas Volf wrote:
>>
>> Hello,
>>
>> when using `activation-service-type' combined with `with-extension', the
>> various modules seem to interfere with each other.
>
Hilton Chain writes:
> On Sat, 08 Mar 2025 05:29:51 +0800,
> Tomas Volf wrote:
>>
>> > but unfortunately (gnu build activation) and (guix build utils) are
>> > implicit dependencies. This is hard to change at the moment.
>>
>> I do not think this is t
Jack Hill writes:
> Assuming I understand correctly that there's no way to get this commit to
> verify: what are the next steps?
>
> Future looking, we should apply the patch so that we don't get non-verifiable
> commits in the future, but that won't help me, since I'll have to verify it
> with
Leo Famulari writes:
> On Sun, Mar 09, 2025 at 10:33:45AM +0100, Tomas Volf wrote:
>> I think it could be influenced by the commit you are currently on, and
>> the commit you are pulling as latest. So depending on time of previous
>> and current pull, it might work or
Ludovic Courtès writes:
> Hi Tomas,
>
> Somehow nobody acted over this bug report for a long time. Terrible.
>
> wolf skribis:
>
>> There is an assumption made by Guix regarding guile-git, which is not
>> true. The problem is demonstrated using my fork, since that is where
>> I encounter
Leo Famulari writes:
> I didn't report this to bug-guix (although I did complain on #guix),
> because I thought it was just me, but now another user on #guix has the
> same problem:
>
> https://logs.guix.gnu.org/guix/2025-03-11.log#205907
>
> `guix gc --verify=contents` reported all the broken fi
Hi!
Timo Wilken writes:
> * gnu/packages/guile-xyz.scm (guile-yamlpp) [arguments] :
> Add 'set-extension-file-name.
>
> Change-Id: I49a7199b4e0fe4053822374bae59c6e1d0b7ead0
> ---
> gnu/packages/guile-xyz.scm | 13 +
> 1 file changed, 13 insertions(+)
>
> diff --git a/gnu/packages/
"Timo Wilken" writes:
> It still feels wrong to do this on a per-package basis (shouldn't
> `with-extension' take care of setting up the path?), but hey ho.
I definitely agree here...
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors
1 - 100 of 109 matches
Mail list logo
