From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 55898@debbugs.gnu.org
Subject: bug#55898: jami service failing following 'guix deploy' update
Date: Sat, 11 Jun 2022 01:53:24 -0400 [thread overview]
Message-ID: <87a6ajg2zv.fsf@gmail.com> (raw)
Hello Guix!
After having fixed the tests of the jami-service-type and pushed the fix
as 85b4dabd94d53f8179f31a42046cd83fc3a352fc, I was confident it would
work, but my freshly 'guix deploy'ed machine says otherwise:
--8<---------------cut here---------------start------------->8---
$ sudo herd stop jami
$ sudo herd start jami
Service jami-dbus-session has been started.
herd: exception caught while executing 'start' on service 'jami':
Unbound variable: jami-service-available?
$ guix system describe
Generation 141 Jun 11 2022 01:38:12 (current)
file name: /var/guix/profiles/system-141-link
canonical file name: /gnu/store/vx9sd4vb2yfv0zhycd461m9wfvgzclsp-system
label: GNU with Linux-Libre 5.17.14
bootloader: grub-efi
root device: label: "btrfs-pool-1"
kernel: /gnu/store/zf4062hz23485dp1xr8w6zbk2m8igpsk-linux-libre-5.17.14/bzImage
configuration file: /gnu/store/n2wqba6npybjd8i730cpi9qc61p16jkr-configuration.scm
--8<---------------cut here---------------end--------------->8---
I don't get it; how can the service runs fine in the instrumented VMs
the system tests use, and fail in my updated machine? Could it be a
fault in 'guix deploy'?
To be investigated...
Thanks,
Maxim
next reply other threads:[~2022-06-11 5:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 5:53 Maxim Cournoyer [this message]
2022-06-11 14:51 ` bug#55898: jami service failing following 'guix deploy' update Maxime Devos
2022-06-14 19:40 ` Maxim Cournoyer
2022-06-24 17:52 ` Maxim Cournoyer
2022-06-24 18:01 ` bug#55898: jami service failing following reconfigure Maxim Cournoyer
2022-07-06 21:38 ` bug#55898: jami service failing following 'guix deploy' update Maxim Cournoyer
2022-07-06 22:01 ` Maxim Cournoyer
2022-07-20 21:19 ` bug#55898: Services depending on new Shepherd features may fail until reboot Ludovic Courtès
2022-07-21 4:10 ` Maxim Cournoyer
2022-08-29 13:43 ` Ludovic Courtès
2022-08-29 21:06 ` Maxim Cournoyer
2022-08-30 7:33 ` Ludovic Courtès
2022-08-30 9:35 ` Maxime Devos
2022-08-30 13:50 ` Ludovic Courtès
2022-09-01 13:18 ` Maxim Cournoyer
2022-09-01 13:28 ` Maxime Devos
2022-09-01 13:51 ` Ludovic Courtès
2022-09-01 19:16 ` Maxim Cournoyer
2022-09-02 9:10 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6ajg2zv.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=55898@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).