GNU bug report logs - #41139
duplicate service provision error message is too terse

Previous Next

To reply to this bug, email your comments to 41139 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: bug-guix <at> gnu.org
Subject: duplicate service provision error message is too terse
Date: Fri, 08 May 2020 22:39:36 +0200

“guix system” prints a very terse error message when a display manager
is added on top of %desktop-services:

    guix system: error: service 'xorg-server' provided more than once

This is not very helpful, because it’s hard to tell how we got there.
Which of the selected services provide xorg-server?

It would be nice if the error message could be a little more helpful.

-- 
Ricardo

Message #8 received at 41139 <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: 41139 <at> debbugs.gnu.org
Subject: Re: bug#41139: duplicate service provision error message is too terse
Date: Thu, 14 May 2020 07:33:15 +0200

Ricardo Wurmus <rekado <at> elephly.net> writes:

> This is not very helpful, because it’s hard to tell how we got there.
> Which of the selected services provide xorg-server?

This is the wrong question.  While Shepherd services may have been
introduced to the Shepherd service graph by other general system
services, this kind of information is unavailable when just looking at
the Shepherd service itself.

The only user-facing identifiers a Shepherd service has is its
provisions.  It’s hard to do better without extending Shepherd services
to include provenance information.

-- 
Ricardo

Message #11 received at 41139 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: 41139 <at> debbugs.gnu.org
Subject: Re: bug#41139: duplicate service provision error message is too terse
Date: Mon, 18 May 2020 00:16:08 +0200

Hi,

Ricardo Wurmus <rekado <at> elephly.net> skribis:

> Ricardo Wurmus <rekado <at> elephly.net> writes:
>
>> This is not very helpful, because it’s hard to tell how we got there.
>> Which of the selected services provide xorg-server?
>
> This is the wrong question.  While Shepherd services may have been
> introduced to the Shepherd service graph by other general system
> services, this kind of information is unavailable when just looking at
> the Shepherd service itself.
>
> The only user-facing identifiers a Shepherd service has is its
> provisions.  It’s hard to do better without extending Shepherd services
> to include provenance information.

Yes, or ‘fold-services’ could provide the “service extension stack”
somehow, for use in error reports.

Ludo’.

Previous Next

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