GNU logs - #55898, boring messages

Message sent to bug-guix@HIDDEN:

Subject: bug#55898: jami service failing following 'guix deploy' update
Resent-From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Sat, 11 Jun 2022 05:54:02 +0000
Resent-Message-ID: <handler.55898.B.165492681632193 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 55898 <at> debbugs.gnu.org
From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
Date: Sat, 11 Jun 2022 01:53:24 -0400
Message-ID: <87a6ajg2zv.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain
Received-SPF: pass client-ip=2607:f8b0:4864:20::f31;
 envelope-from=maxim.cournoyer@HIDDEN; helo=mail-qv1-xf31.google.com
X-Spam_score_int: -20
X-Spam_score: -2.1
X-Spam_bar: --
X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001,
 T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-Spam-Score: -1.3 (-)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -2.3 (--)

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

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
Subject: bug#55898: Acknowledgement (jami service failing following 'guix
 deploy' update)
Message-ID: <handler.55898.B.165492681632193.ack <at> debbugs.gnu.org>
References: <87a6ajg2zv.fsf@HIDDEN>
X-Gnu-PR-Message: ack 55898
X-Gnu-PR-Package: guix
Reply-To: 55898 <at> debbugs.gnu.org
Date: Sat, 11 Jun 2022 05:54:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-guix@HIDDEN

If you wish to submit further information on this problem, please
send it to 55898 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
55898: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D55898
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-guix@HIDDEN:

Subject: bug#55898: jami service failing following 'guix deploy' update
Resent-From: Maxime Devos <maximedevos@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Sat, 11 Jun 2022 14:52:01 +0000
Resent-Message-ID: <handler.55898.B55898.165495907816542 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Maxim Cournoyer <maxim.cournoyer@HIDDEN>, 55898 <at> debbugs.gnu.org
Message-ID: <5521716772922285f7c6bc381c82613026eebbd9.camel@HIDDEN>
From: Maxime Devos <maximedevos@HIDDEN>
Date: Sat, 11 Jun 2022 16:51:05 +0200
In-Reply-To: <87a6ajg2zv.fsf@HIDDEN>
References: <87a6ajg2zv.fsf@HIDDEN>
Content-Type: multipart/signed; micalg="pgp-sha512";
 protocol="application/pgp-signature"; boundary="=-u2ACpbWMpAKejaiK0MsF"
User-Agent: Evolution 3.38.3-1 
MIME-Version: 1.0
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>


--=-u2ACpbWMpAKejaiK0MsF
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Maxim Cournoyer schreef op za 11-06-2022 om 01:53 [-0400]:
> 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?=C2=A0 Could it be a
> fault in 'guix deploy'?

Maybe the shepherd has the old (gnu build jami-service) module loaded
and it doesn't know know to reload modules during reconfiguration?

Greetings,
Maxime.

--=-u2ACpbWMpAKejaiK0MsF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iI0EABYKADUWIQTB8z7iDFKP233XAR9J4+4iGRcl7gUCYqSr2RccbWF4aW1lZGV2
b3NAdGVsZW5ldC5iZQAKCRBJ4+4iGRcl7k8FAP9hlar7xP3IHawtI1wLXjXnxRp0
cbdlFmEs08Ex8uCz3wD/YAiRVRIL6f18vnmp7Er9gvzM/3bm9Uq9iT4YCswNIAs=
=BDRp
-----END PGP SIGNATURE-----

--=-u2ACpbWMpAKejaiK0MsF--

Message sent to bug-guix@HIDDEN:

Subject: bug#55898: jami service failing following 'guix deploy' update
Resent-From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Tue, 14 Jun 2022 19:42:02 +0000
Resent-Message-ID: <handler.55898.B55898.16552356721086 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Maxime Devos <maximedevos@HIDDEN>
Cc: 55898 <at> debbugs.gnu.org
From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
References: <87a6ajg2zv.fsf@HIDDEN>
 <5521716772922285f7c6bc381c82613026eebbd9.camel@HIDDEN>
Date: Tue, 14 Jun 2022 15:40:51 -0400
In-Reply-To: <5521716772922285f7c6bc381c82613026eebbd9.camel@HIDDEN>
 (Maxime Devos's message of "Sat, 11 Jun 2022 16:51:05 +0200")
Message-ID: <87bkuvdoe4.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Hello Maxime,

Maxime Devos <maximedevos@HIDDEN> writes:

> Maxim Cournoyer schreef op za 11-06-2022 om 01:53 [-0400]:
>> 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?=C2=A0 Could it be a
>> fault in 'guix deploy'?
>
> Maybe the shepherd has the old (gnu build jami-service) module loaded
> and it doesn't know know to reload modules during reconfiguration?

If true, that would indeed explain it.

Thanks,

Maxim

Message sent to bug-guix@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#55898: jami service failing following 'guix deploy' update
Resent-From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Fri, 24 Jun 2022 17:53:02 +0000
Resent-Message-ID: <handler.55898.B55898.165609313820105 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 55898
X-GNU-PR-Package: guix
X-GNU-PR-Keywords: 
To: Maxime Devos <maximedevos@HIDDEN>
Cc: 55898 <at> debbugs.gnu.org
Received: via spool by 55898-submit <at> debbugs.gnu.org id=B55898.165609313820105
          (code B ref 55898); Fri, 24 Jun 2022 17:53:02 +0000
Received: (at 55898) by debbugs.gnu.org; 24 Jun 2022 17:52:18 +0000
Received: from localhost ([127.0.0.1]:43449 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1o4nTd-0005ED-T4
	for submit <at> debbugs.gnu.org; Fri, 24 Jun 2022 13:52:18 -0400
Received: from mail-qv1-f43.google.com ([209.85.219.43]:34661)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <maxim.cournoyer@HIDDEN>) id 1o4nTb-0005Dz-Hr
 for 55898 <at> debbugs.gnu.org; Fri, 24 Jun 2022 13:52:15 -0400
Received: by mail-qv1-f43.google.com with SMTP id t16so5676304qvh.1
 for <55898 <at> debbugs.gnu.org>; Fri, 24 Jun 2022 10:52:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=from:to:cc:subject:references:date:in-reply-to:message-id
 :user-agent:mime-version:content-transfer-encoding;
 bh=8zMlKQZTvUdnzhyKOTAPYfEFYHaTN/TJ7mEWNhnZAdM=;
 b=dRuzmOkPZh0WnV8mltZKPtdVaYEzCZqiPUehtCPzAXSPqdxGY0yJKcym01wKPpYpFV
 KSRRDbFiCfLwd+DUmU/dwwq6HzcwZ6rYS8T5NV8AQGDwQa29sRT5VrUJC5ECtOm+y15X
 bGjXNf8UzF7ys2DZ4t/kDpU3pbGtdvguNzptCmEs+Sm0kLysyINJVt/4Lm7JBxPMaFY1
 X7qBEV9UWz1fhSOrCNGdJ530aZkqWAlN+Wv4TQOeh0V/yTXNnvtev29IVah2CSVb4xkQ
 lHKS8TxtNSslKTzvnubiD+4Au5eDWPA/0us4d/ZqP+VSE4ZQICVz6il6QgynFJYQXiaw
 XdZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to
 :message-id:user-agent:mime-version:content-transfer-encoding;
 bh=8zMlKQZTvUdnzhyKOTAPYfEFYHaTN/TJ7mEWNhnZAdM=;
 b=krVO2puGWUrS2WBmar6basrkQqT7ao00rMYq1ARHH/OyOwoyFRFoDVlUsMce/96meC
 9IgZ8umOfh95hdFgQdJXG5dQWuDIIPlf4M/J4hlzw6Uq1zNdg4BNRwZzlVXhdD6QFym/
 Di2fJ5r2+/Z2tp/yJt+0NUdBdtMVDpjZ1S+VWQ7X/Jdn0QYcVLqV8uZfhWzMzZfdHsUj
 ljlzwv1XA/eWzQBIK3Rb43vaVtFESOXsrKV/qMEUtJj6za/PC+nWuBP7Rz6TFQz5BFim
 ICx3LfccVxVIFyQtQvtn0Je3NrMVewa++DpTes7dTZhcPEDZen/+oX7FfPyLB5B1YNb9
 lgSQ==
X-Gm-Message-State: AJIora/mMiM9tOLsY+9QtTuA2U+6iWzW2Wb5ZyS0I8wAIZhb5GSkTrnJ
 3Wy8BohMG22qHd05UeV01OBMT8ZYsXFeUHuNxnY=
X-Google-Smtp-Source: AGRyM1vVIM9d1+G+aSXKZ+BZW26WKDVKB3rrEoo+caqaZMi+YRt4oEGVOm+6cZccaxGjcSCUZ9IAPw==
X-Received: by 2002:a05:6214:411b:b0:470:8461:f85 with SMTP id
 kc27-20020a056214411b00b0047084610f85mr100340qvb.60.1656093129184; 
 Fri, 24 Jun 2022 10:52:09 -0700 (PDT)
Received: from hurd (dsl-158-129.b2b2c.ca. [66.158.158.129])
 by smtp.gmail.com with ESMTPSA id
 u13-20020a05620a0c4d00b006a71398f06fsm2399773qki.32.2022.06.24.10.52.08
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Fri, 24 Jun 2022 10:52:08 -0700 (PDT)
From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
References: <87a6ajg2zv.fsf@HIDDEN>
 <5521716772922285f7c6bc381c82613026eebbd9.camel@HIDDEN>
 <87bkuvdoe4.fsf@HIDDEN>
Date: Fri, 24 Jun 2022 13:52:07 -0400
In-Reply-To: <87bkuvdoe4.fsf@HIDDEN> (Maxim Cournoyer's message of "Tue, 14
 Jun 2022 15:40:51 -0400")
Message-ID: <87v8sqx83c.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.0 (/)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

retitle 55898 jami service fails to start following reconfigure
thanks

Hello,

Maxim Cournoyer <maxim.cournoyer@HIDDEN> writes:

> Hello Maxime,
>
> Maxime Devos <maximedevos@HIDDEN> writes:
>
>> Maxim Cournoyer schreef op za 11-06-2022 om 01:53 [-0400]:
>>> 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?=C2=A0 Could it be=
 a
>>> fault in 'guix deploy'?
>>
>> Maybe the shepherd has the old (gnu build jami-service) module loaded
>> and it doesn't know know to reload modules during reconfiguration?

The module seems to be simply missing, according to:

--8<---------------cut here---------------start------------->8---
$ guix gc -R /gnu/store/sq7krjjpwbkr3z573flbnvkml1574mn5-system | grep jami
/gnu/store/vkgamffkm92l3xdzid42k4lcz6aqfj7i-ffmpeg-jami-4.4.2
/gnu/store/kk3dzx2xsa135d1i5jsjm8i787gbl56i-pjproject-jami-2.11-0.e1f389d
/gnu/store/fyd7rmvzhhqbk1f08c4pl7ahhlfgig40-shepherd-jami.scm
/gnu/store/kqiqnza4l0jawrs0mszymj8diaa2j97m-shepherd-file-system--home-jenk=
ins-jami.scm
/gnu/store/yp9awyfgiym32card9w5mds8id6d6d0l-shepherd-file-system--home-jenk=
ins-jami-workspace.scm
/gnu/store/xib9gc60a8bbff99cffh2x74gqpszf0i-shepherd-jami-dbus-session.scm
/gnu/store/q00v0f7syc1b6phfq4gih8i9irnm862w-dbus-for-jami-1.12.20
/gnu/store/dqfply51lzqc5z697k98avigsv21qm8q-libjami-20211223.2.37be4c3
/gnu/store/5w1zqbwagkhavqs7xjbzb8m7j978dcwj-shepherd-file-system--var-cache=
-jami.scm
/gnu/store/njrxi4apky4ckb2py9qz0ciz0b92smrd-shepherd-jami.go
/gnu/store/kciz8nady3rc5jd9j67bmlzyn622j5md-shepherd-file-system--home-jenk=
ins-jami.go
/gnu/store/ddxa8yxqh1c3h6iax2x24wj0lfxrx8c6-shepherd-file-system--home-jenk=
ins-jami-workspace.go
/gnu/store/d54hhmd90h7q4qmnb3q6ngsdp9457r80-shepherd-jami-dbus-session.go
/gnu/store/59lizyj4miag5if9ylhk383qr1qbxw1h-shepherd-file-system--var-cache=
-jami.go
--8<---------------cut here---------------end--------------->8---

After a 'guix system reconfigure' that successfully changed
/run/current-system.

I was expecting the module should have been pulled in the closure via
the encapsulating:

--8<---------------cut here---------------start------------->8---
    (with-extensions (list guile-packrat ;used by guile-ac-d-bus
                           guile-ac-d-bus
                           ;; Fibers is needed to provide the non-blocking
                           ;; variant of the 'sleep' procedure.
                           guile-fibers)
      (with-imported-modules (source-module-closure
                              '((gnu build dbus-service)
                                (gnu build jami-service)
                                (gnu build shepherd)
                                (gnu system file-systems)))
--8<---------------cut here---------------end--------------->8---

in (gnu services telephony) around line 312.

Thoughts?

Maxim

Message sent to bug-guix@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#55898: jami service failing following reconfigure
Resent-From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Fri, 24 Jun 2022 18:02:02 +0000
Resent-Message-ID: <handler.55898.B55898.165609369421231 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 55898
X-GNU-PR-Package: guix
X-GNU-PR-Keywords: 
To: Maxime Devos <maximedevos@HIDDEN>
Cc: 55898 <at> debbugs.gnu.org
Received: via spool by 55898-submit <at> debbugs.gnu.org id=B55898.165609369421231
          (code B ref 55898); Fri, 24 Jun 2022 18:02:02 +0000
Received: (at 55898) by debbugs.gnu.org; 24 Jun 2022 18:01:34 +0000
Received: from localhost ([127.0.0.1]:43472 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1o4ncc-0005WM-0Y
	for submit <at> debbugs.gnu.org; Fri, 24 Jun 2022 14:01:34 -0400
Received: from mail-qv1-f54.google.com ([209.85.219.54]:35513)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <maxim.cournoyer@HIDDEN>) id 1o4ncZ-0005W5-9Q
 for 55898 <at> debbugs.gnu.org; Fri, 24 Jun 2022 14:01:33 -0400
Received: by mail-qv1-f54.google.com with SMTP id u14so3017752qvv.2
 for <55898 <at> debbugs.gnu.org>; Fri, 24 Jun 2022 11:01:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=from:to:cc:subject:references:date:in-reply-to:message-id
 :user-agent:mime-version:content-transfer-encoding;
 bh=fE1zpGOtasbL9IWV7872T0AabkmNQVg97Lkr0Vg2fn4=;
 b=WKCu2ubSjxdS21XkLo4CF2Bzs6oA2EAjSirlWzRd7XXcAs0ROGvIZ/lzwF2Iua9GCF
 ZtxeY25PQx7lHSzDdXSkD2R3bqiaEZ7fz0ZsNtlzPz0eZCgeGh9duu/5yUd8haNaaEKZ
 dFK9l5b9UM4Noni7bsLo7Y37X5oxyIZYQUrvblQq1topfvDhGJvgo71vn6qTuADU9Nze
 ovuhPrTSEt7jVrF/jyAXWTfm8oidqietU9fDgF3K+JlW8fx5c4ogwn3iOB9I9WnqZuRn
 O1e7Lp2GcVA0T1LoHmvrIhLDk7k52eN2AEzQufvn/UivcdSszBYiH3pT0KExc/iHuAFi
 jGiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to
 :message-id:user-agent:mime-version:content-transfer-encoding;
 bh=fE1zpGOtasbL9IWV7872T0AabkmNQVg97Lkr0Vg2fn4=;
 b=NiwkLRA9p2UyDymzNbxFqAZg1fpjKov6sYWVzZRZMPN0reSiG7zVsfGCLwoJewwOl2
 NJboFN0teyUorFUXBVCtUpO/FW3fnUKa23r6/hJq/97pWDAIj/w8L587lDfpKwrjQ19k
 4IbwKo4x+YOD0eQQG+OIXjtaVPOKZGnGs+NQhZQYzpKgwHkVxERGzR5poWv1ZsG6GDdb
 Em31saI1SuYzNC0OuHkF81UQSraUsbt3F8kkOAfH/ZAMp5lBfZ80vcfQ+aE6tzazKJmd
 qJ4u0q+NvkzzZr6nY94X7iDwTqu8p1boYf+T97aqA9ifi45HmmMNCGJjjyEHY//NP4iQ
 aT/g==
X-Gm-Message-State: AJIora++yxy2anHtWZSBh6fagnmkOmrBDxTs/xSNInWqATAskZQ33Rgs
 HWQmfcBo7Bc/AcTRbXIoJFHcUU/nIINgEp8IUxI=
X-Google-Smtp-Source: AGRyM1sFn4vgYpn+it5NXSCZUPyuOFT47IdCb9A9eMCti4HivAFUEbJnQWIEsepQYvmoMNwg542MVw==
X-Received: by 2002:ad4:5d49:0:b0:46a:66a2:d73f with SMTP id
 jk9-20020ad45d49000000b0046a66a2d73fmr37872339qvb.45.1656093685105; 
 Fri, 24 Jun 2022 11:01:25 -0700 (PDT)
Received: from hurd (dsl-158-129.b2b2c.ca. [66.158.158.129])
 by smtp.gmail.com with ESMTPSA id
 f10-20020a05620a280a00b006a69d7f390csm2260478qkp.103.2022.06.24.11.01.24
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Fri, 24 Jun 2022 11:01:24 -0700 (PDT)
From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
References: <87a6ajg2zv.fsf@HIDDEN>
 <5521716772922285f7c6bc381c82613026eebbd9.camel@HIDDEN>
 <87bkuvdoe4.fsf@HIDDEN>
Date: Fri, 24 Jun 2022 14:01:23 -0400
In-Reply-To: <87bkuvdoe4.fsf@HIDDEN> (Maxim Cournoyer's message of "Tue, 14
 Jun 2022 15:40:51 -0400")
Message-ID: <87r13ex7nw.fsf_-_@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.0 (/)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

Hi again,

Maxim Cournoyer <maxim.cournoyer@HIDDEN> writes:

> Hello Maxime,
>
> Maxime Devos <maximedevos@HIDDEN> writes:
>
>> Maxim Cournoyer schreef op za 11-06-2022 om 01:53 [-0400]:
>>> 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?=C2=A0 Could it be=
 a
>>> fault in 'guix deploy'?
>>
>> Maybe the shepherd has the old (gnu build jami-service) module loaded
>> and it doesn't know know to reload modules during reconfiguration?

I verified that in the
/gnu/store/fyd7rmvzhhqbk1f08c4pl7ahhlfgig40-shepherd-jami.scm file it
was setting up the load path with everything needed, such as

--8<---------------cut here---------------start------------->8---
(eval-when
    (expand load eval)
  (let
      ((extensions
        (quote
         ("/gnu/store/f6q4237n62lq7n8z3qyh3jx5iinb9myr-guile-packrat-0.1.1"=
 "/gnu/store/l2f9gmd64w56nnhnlb63hg8f5crfvwln-guile-ac-d-bus-1.0.0-beta.0" =
"/gnu/store/is9f6ki7i2f6qk80ivvz7q1vvlibb96l-guile-fibers-1.0.0")))
       (prepend
        (lambda
            (items lst)
          (let loop
              ((items items)
               (lst lst))
            (if
             (null? items)
             lst
             (loop
              (cdr items)
              (cons
               (car items)
               (delete
                (car items)
                lst))))))))
    (set! %load-path
          (prepend
           (cons "/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import"
                 (map
                  (lambda
                      (extension)
                    (string-append extension "/share/guile/site/"
                                   (effective-version)))
                  extensions))
           %load-path))
    (set! %load-compiled-path
          (prepend
           (cons "/gnu/store/zqgpayc87lfmcmncgzbp5v59hav8ww1c-module-import=
-compiled"
                 (map
                  (lambda
                      (extension)
                    (string-append extension "/lib/guile/"
                                   (effective-version)
                                   "/site-ccache"))
                  extensions))
           %load-compiled-path))))
--8<---------------cut here---------------end--------------->8---

The /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import directory
contains:

--8<---------------cut here---------------start------------->8---
$ find /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/build
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/build/dbus-se=
rvice.scm
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/build/file-sy=
stems.scm
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/build/jami-se=
rvice.scm
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/build/linux-c=
ontainer.scm
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/build/shepher=
d.scm
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/system
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/system/file-s=
ystems.scm
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/system/uuid.s=
cm
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/build
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/build/bourni=
sh.scm
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/build/syscal=
ls.scm
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/build/utils.=
scm
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/colors.scm
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/i18n.scm
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/profiling.scm
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/diagnostics.=
scm
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/memoization.=
scm
/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/records.scm
--8<---------------cut here---------------end--------------->8---

and the referenced [...]/gnu/build/jami-service.scm file does contain
the supposedly missing 'jami-service-available?' procedure.

I'm suspecting that given the service makes use of Shepherd 0.9
features, perhaps it fails loading and the error is reported erroneously
that way... a reboot would tell but I'm not in a position to do that at
this moment (remote machine).

Thanks,

Maxim

Message sent to bug-guix@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#55898: jami service failing following 'guix deploy' update
Resent-From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Wed, 06 Jul 2022 21:39:02 +0000
Resent-Message-ID: <handler.55898.B55898.165714353221676 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 55898
X-GNU-PR-Package: guix
X-GNU-PR-Keywords: 
To: Maxime Devos <maximedevos@HIDDEN>
Cc: GNU Debbugs <control <at> debbugs.gnu.org>, 55898 <at> debbugs.gnu.org
Received: via spool by 55898-submit <at> debbugs.gnu.org id=B55898.165714353221676
          (code B ref 55898); Wed, 06 Jul 2022 21:39:02 +0000
Received: (at 55898) by debbugs.gnu.org; 6 Jul 2022 21:38:52 +0000
Received: from localhost ([127.0.0.1]:55304 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1o9CjQ-0005dP-DX
	for submit <at> debbugs.gnu.org; Wed, 06 Jul 2022 17:38:52 -0400
Received: from mail-qk1-f170.google.com ([209.85.222.170]:45728)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <maxim.cournoyer@HIDDEN>)
 id 1o9Cj0-0005cd-OL; Wed, 06 Jul 2022 17:38:31 -0400
Received: by mail-qk1-f170.google.com with SMTP id p11so12041194qkg.12;
 Wed, 06 Jul 2022 14:38:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=from:to:cc:subject:references:date:in-reply-to:message-id
 :user-agent:mime-version;
 bh=LSrjcxRU1f6l55UpvHRtUQI0pCr/pGJmKaDnxoJ+Ofs=;
 b=mTUw685fmiO4yNqvq9JRcPgVKfiQodIfvq2GbGM28ZpD6ks3v+LkO89ov4JSndf4Cw
 4mZsc7Lph4JmbTdgFulOXxMOJAp6HF8ggTN5FXUryTdE8fIrQrbz4JorV7YXl9Vurt4u
 TIE8lKmJfzhM/EyajkkMuwHG+a01JY7WlblJI+zo56vO54MaysImZyrYASfjoG/1pBoK
 WO6VREDqgdN9iVU0iMXtWH4WvzLZV7ONUi00tveqHImyu1+fGNsutaYaO6Nl0P4aTols
 H5gHxksv7rPZqE6g0/gNXK6rI2ugK80RNypF/o62z/+OQdorXfeYFvWsE9r8DlzlKWKN
 dPFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to
 :message-id:user-agent:mime-version;
 bh=LSrjcxRU1f6l55UpvHRtUQI0pCr/pGJmKaDnxoJ+Ofs=;
 b=I4WG1Jubw7onzhv1N8mJYXH66SdYGIKQRCQsn9FtLrkeM2SGGorv8owk3FhMaJ4N0P
 AjQ6TfpkNu9pSRZ3/wtua+bzwbOnw5om0bG8dGBIoc0dGXT7UIAEETbbTx5e7CNBsmSe
 ZCRw+Xk/JyeIwfvKwGC2uhbQSOU8iUAKENVqKnkXgTwYMvsPEXQnEFwH4J3lklvFt03F
 nkbzSN62ETf7MGvCNbalK5KZFEeZuyZBMRkKDpc+/M/3m1k7/NaOHI17I5jjR6qCoPVq
 JdeGto5Rq6iSaMEeFjW0X1oCygRJd9ricaVuJiHWnhJL82VdGMADgQhgeSSrTPlEaU0m
 /yBw==
X-Gm-Message-State: AJIora+Si3GMTD1wSWcnQq9PEKE88yTxmyrQTbc/sms9JQV8VqX7xXGu
 W2rtdtQPGxggDA9LjU6wpNWmVf7Ftl8zqaRt
X-Google-Smtp-Source: AGRyM1um74pLtujyxPcHmo+7v37SkfAN95Z+xFkGqSL55Ve2nfR42HJ5I9K8PjngiQoW1O0IEuh+kA==
X-Received: by 2002:ae9:f711:0:b0:6af:9d1:8ede with SMTP id
 s17-20020ae9f711000000b006af09d18edemr29232150qkg.179.1657143495451; 
 Wed, 06 Jul 2022 14:38:15 -0700 (PDT)
Received: from hurd (dsl-10-134-148.b2b2c.ca. [72.10.134.148])
 by smtp.gmail.com with ESMTPSA id
 bs11-20020a05620a470b00b006b1eb3a8364sm16959061qkb.5.2022.07.06.14.38.14
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Wed, 06 Jul 2022 14:38:14 -0700 (PDT)
From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
References: <87a6ajg2zv.fsf@HIDDEN>
 <5521716772922285f7c6bc381c82613026eebbd9.camel@HIDDEN>
 <87bkuvdoe4.fsf@HIDDEN> <87r13ex7nw.fsf_-_@HIDDEN>
Date: Wed, 06 Jul 2022 17:38:13 -0400
In-Reply-To: <87r13ex7nw.fsf_-_@HIDDEN> (Maxim Cournoyer's message of "Fri, 
 24 Jun 2022 14:01:23 -0400")
Message-ID: <87mtdl2a7u.fsf_-_@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Spam-Score: -0.0 (/)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

retitle 55898 Services depending on new Shepherd features may fail until
a reboot
thanks

Hi,

Maxim Cournoyer <maxim.cournoyer@HIDDEN> writes:

[...]

> I'm suspecting that given the service makes use of Shepherd 0.9
> features, perhaps it fails loading and the error is reported erroneously
> that way... a reboot would tell but I'm not in a position to do that at
> this moment (remote machine).

I confirm that following a reboot, the service runs normally.

Perhaps services should allow specifying the minimum required Shepherd
version, which Shepherd could ensure is met before attempting to restart
a service, printing something like:

'Could not restart service X due to unmet Shepherd version requirement;
the service will continue unchanged until the next reboot'

or something similar.

I've re-titled the bug, as this isn't specific to our jami service.

Thanks!

Maxim

Message received at control <at> debbugs.gnu.org:

Received: (at control) by debbugs.gnu.org; 6 Jul 2022 21:38:48 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Wed Jul 06 17:38:48 2022
Received: from localhost ([127.0.0.1]:55302 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1o9CjB-0005d4-Ag
	for submit <at> debbugs.gnu.org; Wed, 06 Jul 2022 17:38:48 -0400
Received: from mail-qk1-f170.google.com ([209.85.222.170]:45728)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <maxim.cournoyer@HIDDEN>)
 id 1o9Cj0-0005cd-OL; Wed, 06 Jul 2022 17:38:31 -0400
Received: by mail-qk1-f170.google.com with SMTP id p11so12041194qkg.12;
 Wed, 06 Jul 2022 14:38:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=from:to:cc:subject:references:date:in-reply-to:message-id
 :user-agent:mime-version;
 bh=LSrjcxRU1f6l55UpvHRtUQI0pCr/pGJmKaDnxoJ+Ofs=;
 b=mTUw685fmiO4yNqvq9JRcPgVKfiQodIfvq2GbGM28ZpD6ks3v+LkO89ov4JSndf4Cw
 4mZsc7Lph4JmbTdgFulOXxMOJAp6HF8ggTN5FXUryTdE8fIrQrbz4JorV7YXl9Vurt4u
 TIE8lKmJfzhM/EyajkkMuwHG+a01JY7WlblJI+zo56vO54MaysImZyrYASfjoG/1pBoK
 WO6VREDqgdN9iVU0iMXtWH4WvzLZV7ONUi00tveqHImyu1+fGNsutaYaO6Nl0P4aTols
 H5gHxksv7rPZqE6g0/gNXK6rI2ugK80RNypF/o62z/+OQdorXfeYFvWsE9r8DlzlKWKN
 dPFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to
 :message-id:user-agent:mime-version;
 bh=LSrjcxRU1f6l55UpvHRtUQI0pCr/pGJmKaDnxoJ+Ofs=;
 b=I4WG1Jubw7onzhv1N8mJYXH66SdYGIKQRCQsn9FtLrkeM2SGGorv8owk3FhMaJ4N0P
 AjQ6TfpkNu9pSRZ3/wtua+bzwbOnw5om0bG8dGBIoc0dGXT7UIAEETbbTx5e7CNBsmSe
 ZCRw+Xk/JyeIwfvKwGC2uhbQSOU8iUAKENVqKnkXgTwYMvsPEXQnEFwH4J3lklvFt03F
 nkbzSN62ETf7MGvCNbalK5KZFEeZuyZBMRkKDpc+/M/3m1k7/NaOHI17I5jjR6qCoPVq
 JdeGto5Rq6iSaMEeFjW0X1oCygRJd9ricaVuJiHWnhJL82VdGMADgQhgeSSrTPlEaU0m
 /yBw==
X-Gm-Message-State: AJIora+Si3GMTD1wSWcnQq9PEKE88yTxmyrQTbc/sms9JQV8VqX7xXGu
 W2rtdtQPGxggDA9LjU6wpNWmVf7Ftl8zqaRt
X-Google-Smtp-Source: AGRyM1um74pLtujyxPcHmo+7v37SkfAN95Z+xFkGqSL55Ve2nfR42HJ5I9K8PjngiQoW1O0IEuh+kA==
X-Received: by 2002:ae9:f711:0:b0:6af:9d1:8ede with SMTP id
 s17-20020ae9f711000000b006af09d18edemr29232150qkg.179.1657143495451; 
 Wed, 06 Jul 2022 14:38:15 -0700 (PDT)
Received: from hurd (dsl-10-134-148.b2b2c.ca. [72.10.134.148])
 by smtp.gmail.com with ESMTPSA id
 bs11-20020a05620a470b00b006b1eb3a8364sm16959061qkb.5.2022.07.06.14.38.14
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Wed, 06 Jul 2022 14:38:14 -0700 (PDT)
From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
To: Maxime Devos <maximedevos@HIDDEN>
Subject: Re: bug#55898: jami service failing following 'guix deploy' update
References: <87a6ajg2zv.fsf@HIDDEN>
 <5521716772922285f7c6bc381c82613026eebbd9.camel@HIDDEN>
 <87bkuvdoe4.fsf@HIDDEN> <87r13ex7nw.fsf_-_@HIDDEN>
Date: Wed, 06 Jul 2022 17:38:13 -0400
In-Reply-To: <87r13ex7nw.fsf_-_@HIDDEN> (Maxim Cournoyer's message of "Fri, 
 24 Jun 2022 14:01:23 -0400")
Message-ID: <87mtdl2a7u.fsf_-_@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Spam-Score: -0.0 (/)
X-Debbugs-Envelope-To: control
Cc: GNU Debbugs <control <at> debbugs.gnu.org>, 55898 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

retitle 55898 Services depending on new Shepherd features may fail until
a reboot
thanks

Hi,

Maxim Cournoyer <maxim.cournoyer@HIDDEN> writes:

[...]

> I'm suspecting that given the service makes use of Shepherd 0.9
> features, perhaps it fails loading and the error is reported erroneously
> that way... a reboot would tell but I'm not in a position to do that at
> this moment (remote machine).

I confirm that following a reboot, the service runs normally.

Perhaps services should allow specifying the minimum required Shepherd
version, which Shepherd could ensure is met before attempting to restart
a service, printing something like:

'Could not restart service X due to unmet Shepherd version requirement;
the service will continue unchanged until the next reboot'

or something similar.

I've re-titled the bug, as this isn't specific to our jami service.

Thanks!

Maxim

Message sent to bug-guix@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#55898: jami service failing following 'guix deploy' update
Resent-From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Wed, 06 Jul 2022 22:02:02 +0000
Resent-Message-ID: <handler.55898.B55898.165714491732411 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 55898
X-GNU-PR-Package: guix
X-GNU-PR-Keywords: 
To: Maxime Devos <maximedevos@HIDDEN>
Cc: GNU Debbugs <control <at> debbugs.gnu.org>, 55898 <at> debbugs.gnu.org
Received: via spool by 55898-submit <at> debbugs.gnu.org id=B55898.165714491732411
          (code B ref 55898); Wed, 06 Jul 2022 22:02:02 +0000
Received: (at 55898) by debbugs.gnu.org; 6 Jul 2022 22:01:57 +0000
Received: from localhost ([127.0.0.1]:55321 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1o9D5p-0008Qf-B3
	for submit <at> debbugs.gnu.org; Wed, 06 Jul 2022 18:01:57 -0400
Received: from mail-qt1-f169.google.com ([209.85.160.169]:37472)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <maxim.cournoyer@HIDDEN>)
 id 1o9D5l-0008QK-K3; Wed, 06 Jul 2022 18:01:55 -0400
Received: by mail-qt1-f169.google.com with SMTP id i11so20269297qtr.4;
 Wed, 06 Jul 2022 15:01:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=from:to:cc:subject:references:date:in-reply-to:message-id
 :user-agent:mime-version;
 bh=0rvaPlqFPOPduEkxVAoLVsmjaVt4VYO7nub8kv3x5GE=;
 b=f7+C/Z0AHyGmn129G69jf3BBI8FbX5uvB4BPZ+2XjUSjIxdvmVGA1gV/sikD1RZuSq
 VzprYtBlqpZ+NF189sIJashXB5L/A8+XQIsS45AY70KouUDVywTS5JzlhFnWVabfn6gY
 h2rZoAfMl3vVxULG6zenEuPdMweLZ3yjrYVKdvGoOMuPQUdtMxibyNzJltJjzdIvSm8t
 hhdSYxkXNgk5lvqQ777XEH51mkcpaORr0RgHu7+h11gWf28vF9e4f/+jgZQhjEDHh1xp
 2is+EMS06l1mbysyDU4La+5U/T8UF+prxI3tsVYbh06s/7h/C33wHoW1YX8JoYmk3YN+
 fHYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to
 :message-id:user-agent:mime-version;
 bh=0rvaPlqFPOPduEkxVAoLVsmjaVt4VYO7nub8kv3x5GE=;
 b=C/yAvPFRWZrkwb/9V3xqPAbUNGckNziNzrtmMGFkH4H7DCSgYWt/Lkf36Rclc+TcFw
 vxrymx7u4TRKo5P2pSbVLUIEcU9uRP6NZwBZmu7znXIz2ZYRHy7N2I0t8W4WmgEhbRZN
 ESM9Ky6YYWBZJATOt9B85mlBt/tRdKSCNQePZ5mnt0DzEjwQd22us6BjUkSxmAscV4Cc
 llhe+KgBXO96OTDrBjCBOTkPWWZdYFkhzBT7fZSMBVL/dCiePZznEcVCg/PaAXorXUbO
 A51DcSe0VUdSaVR0tgul+esnobyWLj287jlUe6lb3RF9AnwT7sp/zF91b164mDv5/xmu
 wa6Q==
X-Gm-Message-State: AJIora/r4v4oFqsqCOEiQkzLMKSU+PmRg0By8EKcwzjWpf/XOT2H5ION
 Fs6lsJfdL5k8fxs6rpuu8D5pdfqi0itwP2hr
X-Google-Smtp-Source: AGRyM1u624e+H3hdtn/Na12o5Ku2mEliZ6OQ2Bx/ybWyXoE2W7XOvETcImt8ggNBOcdJGHa1I2inQQ==
X-Received: by 2002:a05:622a:5cf:b0:31d:4c04:b642 with SMTP id
 d15-20020a05622a05cf00b0031d4c04b642mr15481037qtb.310.1657144907635; 
 Wed, 06 Jul 2022 15:01:47 -0700 (PDT)
Received: from hurd (dsl-10-134-148.b2b2c.ca. [72.10.134.148])
 by smtp.gmail.com with ESMTPSA id
 bp10-20020a05622a1b8a00b0031d4044c464sm10003350qtb.46.2022.07.06.15.01.46
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Wed, 06 Jul 2022 15:01:47 -0700 (PDT)
From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
References: <87a6ajg2zv.fsf@HIDDEN>
 <5521716772922285f7c6bc381c82613026eebbd9.camel@HIDDEN>
 <87bkuvdoe4.fsf@HIDDEN> <87r13ex7nw.fsf_-_@HIDDEN>
 <87mtdl2a7u.fsf_-_@HIDDEN>
Date: Wed, 06 Jul 2022 18:01:45 -0400
In-Reply-To: <87mtdl2a7u.fsf_-_@HIDDEN> (Maxim Cournoyer's message of "Wed, 
 06 Jul 2022 17:38:13 -0400")
Message-ID: <87ilo9294m.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Spam-Score: -0.0 (/)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

Hi again,

[...]

> Perhaps services should allow specifying the minimum required Shepherd
> version, which Shepherd could ensure is met before attempting to restart
> a service, printing something like:
>
> 'Could not restart service X due to unmet Shepherd version requirement;
> the service will continue unchanged until the next reboot'
>
> or something similar.
>
> I've re-titled the bug, as this isn't specific to our jami service.

I've asked in #systemd about what a similar situation would happen in
systemd-land, and here's what I've learned:

1. service units aren't reloaded automatically after new versions of
them are installed -- this effectively prevent the breakage seen here
(the jami service was reloaded and restarting manually it caused it to
fail).

2. a savvy user can still opt to force the new service to be reloaded
via 'systemctl daemon-reload'.  In case the service update depends on
new systemd features, systemd would need to be restarted itself, via
'systemctl daemon-reexec'.   The later command is interesting, but its
documented as a debugging tool [0]:

  daemon-reexec

    Reexecute the systemd manager. This will serialize the manager
    state, reexecute the process and deserialize the state again. This
    command is of little use except for debugging and package
    upgrades. Sometimes, it might be helpful as a heavy-weight
    daemon-reload. While the daemon is being reexecuted, all sockets
    systemd listening on behalf of user configuration will stay
    accessible.

[0]  https://www.freedesktop.org/software/systemd/man/systemctl.html#

systemd folks told me it is not typically run in systemd package upgrade
hooks, but perhaps some distribution do this (I don't know).

So the situation is not very different in systemd vs shepherd, except
that we more aggressively load the new service definitions, potentially
leading to breakage.

Thoughts?

Maxim

Message received at control <at> debbugs.gnu.org:

Received: (at control) by debbugs.gnu.org; 7 Jul 2022 13:16:36 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Thu Jul 07 09:16:36 2022
Received: from localhost ([127.0.0.1]:56008 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1o9RMx-0000S3-SB
	for submit <at> debbugs.gnu.org; Thu, 07 Jul 2022 09:16:35 -0400
Received: from mail-qt1-f174.google.com ([209.85.160.174]:41582)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <maxim.cournoyer@HIDDEN>) id 1o9RMt-0000Rg-CT
 for control <at> debbugs.gnu.org; Thu, 07 Jul 2022 09:16:34 -0400
Received: by mail-qt1-f174.google.com with SMTP id c20so326606qtw.8
 for <control <at> debbugs.gnu.org>; Thu, 07 Jul 2022 06:16:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=date:message-id:to:from:subject;
 bh=K8d5JYDSHsjZsP1wo//jgPJdl/2FAqEtCKVJhke/E/4=;
 b=H7CNoiSW6igy8LevOckaLvChK5mnGIenGibwHEgPG1BHrpkv4h/uWVXtAb9pgy8hsi
 whqY5+UWxnb6esfs0lX8+gncbKFbgKx17XIz5XG4Z2VayMg1jI8dBceY6mRNR9jNRD43
 3EB9kzL0HmaHCW7IfsgEz/PlaKDbVwCSvT0a2mkRqdn7IetOyfzLii0ZOUWTYqhB2fVP
 tFd44ud2Uq0x34t5JreMgaGBT0LIFwR4r3UivyyZZw+k0c1US8IfOMjGqEiT95fSRe18
 pBJ64qEO3w9kUyNQmj4qGNM9KnJvAEq0CNdLZQo0lPK8/B+UM1wFcogtSg2JF8m2GBGi
 45iw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:date:message-id:to:from:subject;
 bh=K8d5JYDSHsjZsP1wo//jgPJdl/2FAqEtCKVJhke/E/4=;
 b=k5OC7/1gwGzMvZ6m90RI4iltr9hhH8682N+lYukbHRDg4hkFxr4wtiyyWXAN6uC/0b
 2CqH6cx8vBamFwTePRkbddvkdFzWYW8TYigliwWyxyfMaBGeyUeIwDnHrKBfqJyTiEkV
 dtSZSryW28azAP/IGF+XhgD8j/vStv/71ioIoqr/TqvzzVaR0GbLvFNndc8I9zmDVphW
 i7kpGsBuIFLXiVZzaVTSghvZ6Nr/QBbnaBkRJVYQksgXxdXLeUgWLpQPEtwrmG+zTQRV
 5XSyrMliVfpeVwJxBDDibYJjyyV/9snlDn9r/FBp8PEDOZ8lIQb/dIRGNl/IFgEnhKOO
 XelA==
X-Gm-Message-State: AJIora/kEoBJF3ESheJLkiCnqC7Qfny30CdsWXC7IwZevkEa8C99OCXJ
 gINqpi3w+XwC4G0TVVAxxwfkHHYnqonqZQ==
X-Google-Smtp-Source: AGRyM1s6XssdgjD7P8e3msH9yD2apV7hz8kzTjJIh8S0OBYOrPxIU3/G0hnbcB7CwOr+lukCfcP+Sw==
X-Received: by 2002:a05:6214:d81:b0:45a:e07e:6bcb with SMTP id
 e1-20020a0562140d8100b0045ae07e6bcbmr40900622qve.29.1657199785569; 
 Thu, 07 Jul 2022 06:16:25 -0700 (PDT)
Received: from hurd (dsl-153-127.b2b2c.ca. [66.158.153.127])
 by smtp.gmail.com with ESMTPSA id
 r13-20020ae9d60d000000b006b28277939bsm12189757qkk.71.2022.07.07.06.16.24
 for <control <at> debbugs.gnu.org>
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Thu, 07 Jul 2022 06:16:25 -0700 (PDT)
Date: Thu, 07 Jul 2022 09:16:23 -0400
Message-Id: <87h73t12s8.fsf@HIDDEN>
To: control <at> debbugs.gnu.org
From: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
Subject: control message for bug #55898
X-Spam-Score: -0.0 (/)
X-Debbugs-Envelope-To: control
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

retitle 55898 Services depending on new Shepherd features may fail until reboot
quit

Message sent to bug-guix@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#55898: Services depending on new Shepherd features may fail until reboot
Resent-From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Wed, 20 Jul 2022 21:20:01 +0000
Resent-Message-ID: <handler.55898.B55898.165835199710105 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 55898
X-GNU-PR-Package: guix
X-GNU-PR-Keywords: 
To: Maxim Cournoyer <maxim.cournoyer@HIDDEN>
Cc: GNU Debbugs <control <at> debbugs.gnu.org>, Maxime Devos <maximedevos@HIDDEN>, 55898 <at> debbugs.gnu.org
Received: via spool by 55898-submit <at> debbugs.gnu.org id=B55898.165835199710105
          (code B ref 55898); Wed, 20 Jul 2022 21:20:01 +0000
Received: (at 55898) by debbugs.gnu.org; 20 Jul 2022 21:19:57 +0000
Received: from localhost ([127.0.0.1]:36185 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1oEH6r-0002cu-1Q
	for submit <at> debbugs.gnu.org; Wed, 20 Jul 2022 17:19:57 -0400
Received: from eggs.gnu.org ([209.51.188.92]:44736)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <ludo@HIDDEN>)
 id 1oEH6o-0002cd-3m; Wed, 20 Jul 2022 17:19:56 -0400
Received: from fencepost.gnu.org ([2001:470:142:3::e]:38702)
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <ludo@HIDDEN>)
 id 1oEH6i-0006ON-74; Wed, 20 Jul 2022 17:19:48 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=MIME-Version:In-Reply-To:Date:References:Subject:To:
 From; bh=nvJ0LMfkwpO95UeZJVfkVRoOKjIvGVfuI9yXOXaAuRw=; b=mIg7/Ic+7NbaxcbEqvGH
 XwrZ0tffLIwwHTbI0DwJ0XyZplvB/T4Y6DCCQ16/35+/vp7tjTgauWhdeFkCxt815ZLvPCdhk8JsJ
 M0OB7K/7JIgCUWWJwPo2e9e18xCP20KkPYYw1y0DSr0Dxdy0HCpxW+SHQn+/QPyDJWTBqGkhUlOOe
 uqX4PUuMrPTpD/KvXJJ+sQcYS6J7KGikHdKiCn2dskRyMT82MvZsCl5w/HkIwt8mPLU1il5wOtedp
 cswILq01clf9kdwT4BdtpDAYN5hoSNoGIU4tti6oa37m7cmReMN7dNgSfmpEdNgE1Vdwjt38kQxRw
 9zbhA/b72PTRgQ==;
Received: from 91-160-117-201.subs.proxad.net ([91.160.117.201]:56462
 helo=ribbon)
 by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <ludo@HIDDEN>)
 id 1oEH6h-0008UN-JZ; Wed, 20 Jul 2022 17:19:48 -0400
From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@HIDDEN>
References: <87a6ajg2zv.fsf@HIDDEN>
 <5521716772922285f7c6bc381c82613026eebbd9.camel@HIDDEN>
 <87bkuvdoe4.fsf@HIDDEN> <87r13ex7nw.fsf_-_@HIDDEN>
 <87mtdl2a7u.fsf_-_@HIDDEN> <87ilo9294m.fsf@HIDDEN>
Date: Wed, 20 Jul 2022 23:19:44 +0200
In-Reply-To: <87ilo9294m.fsf@HIDDEN> (Maxim Cournoyer's message of "Wed, 06
 Jul 2022 18:01:45 -0400")
Message-ID: <87a693pjm7.fsf_-_@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -2.3 (--)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -3.3 (---)

Hi!

Maxim Cournoyer <maxim.cournoyer@HIDDEN> skribis:

>> Perhaps services should allow specifying the minimum required Shepherd
>> version, which Shepherd could ensure is met before attempting to restart
>> a service, printing something like:
>>
>> 'Could not restart service X due to unmet Shepherd version requirement;
>> the service will continue unchanged until the next reboot'
>>
>> or something similar.

Yes.  The issue is that we=E2=80=99re more free-style than systemd: we=E2=
=80=99re
basically loading code live in the running Shepherd.  So we have to
write that code such that it works with older Shepherd versions.

This is why we have things like conditions on

  (defined? 'make-inetd-constructor)

and the likes, with a fallback.

>> I've re-titled the bug, as this isn't specific to our jami service.
>
> I've asked in #systemd about what a similar situation would happen in
> systemd-land, and here's what I've learned:
>
> 1. service units aren't reloaded automatically after new versions of
> them are installed -- this effectively prevent the breakage seen here
> (the jami service was reloaded and restarting manually it caused it to
> fail).
>
> 2. a savvy user can still opt to force the new service to be reloaded
> via 'systemctl daemon-reload'.  In case the service update depends on
> new systemd features, systemd would need to be restarted itself, via
> 'systemctl daemon-reexec'.   The later command is interesting, but its
> documented as a debugging tool [0]:
>
>   daemon-reexec
>
>     Reexecute the systemd manager. This will serialize the manager
>     state, reexecute the process and deserialize the state again. This
>     command is of little use except for debugging and package
>     upgrades. Sometimes, it might be helpful as a heavy-weight
>     daemon-reload. While the daemon is being reexecuted, all sockets
>     systemd listening on behalf of user configuration will stay
>     accessible.
>
> [0]  https://www.freedesktop.org/software/systemd/man/systemctl.html#
>
> systemd folks told me it is not typically run in systemd package upgrade
> hooks, but perhaps some distribution do this (I don't know).
>
> So the situation is not very different in systemd vs shepherd, except
> that we more aggressively load the new service definitions, potentially
> leading to breakage.

I think any upgrade, be it =E2=80=98guix system reconfigure=E2=80=99 or =E2=
=80=98apt
dist-upgrade=E2=80=99, is likely to end up loading new service definitions=
=E2=80=94Guix
System isn=E2=80=99t more aggressive in that respect.

The main difference is that our services are code and that they might
depend on specific Shepherd APIs.  It=E2=80=99s a much more direct dependen=
cy
compared to .service files I guess.

Thanks,
Ludo=E2=80=99.

Last modified: Wed, 20 Jul 2022 21:30:01 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.