#28167 - decide how to deal with gschemas

Package	Source(s)		Maintainer(s)
guix		PTS Buildd Popcon

Message #8 received at 28167@debbugs.gnu.org (full text, mbox, reply):

Received: (at 28167) by debbugs.gnu.org; 21 Aug 2017 13:58:50 +0000
From debbugs-submit-bounces@debbugs.gnu.org Mon Aug 21 09:58:50 2017
Received: from localhost ([127.0.0.1]:47896 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces@debbugs.gnu.org>)
	id 1djnE9-0007Vf-UF
	for submit@debbugs.gnu.org; Mon, 21 Aug 2017 09:58:50 -0400
Received: from sender-of-o51.zoho.com ([135.84.80.216]:21094)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <rekado@elephly.net>) id 1djnE8-0007VW-Ar
 for 28167@debbugs.gnu.org; Mon, 21 Aug 2017 09:58:48 -0400
Received: from localhost (141.80.244.60 [141.80.244.60]) by mx.zohomail.com
 with SMTPS id 1503323926004822.3575361213436;
 Mon, 21 Aug 2017 06:58:46 -0700 (PDT)
References: <20170820200438.kouji7n6hkr2i6hz@abyayala>
User-agent: mu4e 0.9.18; emacs 25.2.1
From: Ricardo Wurmus <rekado@elephly.net>
To: ng0 <ng0@infotropique.org>
Subject: Re: bug#28167: decide how to deal with gschemas
In-reply-to: <20170820200438.kouji7n6hkr2i6hz@abyayala>
X-URL: https://elephly.net
X-PGP-Key: https://elephly.net/rekado.pubkey
X-PGP-Fingerprint: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
Date: Mon, 21 Aug 2017 15:58:43 +0200
Message-ID: <87fuclvx7w.fsf@elephly.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-ZohoMailClient: External
X-Spam-Score: 1.0 (+)
X-Debbugs-Envelope-To: 28167
Cc: 28167@debbugs.gnu.org
X-BeenThere: debbugs-submit@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@debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit@debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request@debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request@debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces@debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
X-Spam-Score: 1.0 (+)

ng0 <ng0@infotropique.org> writes:

> Creating manual page database for 59 packages... done in 2.152 s
> warning: collision encountered: /gnu/store/7dq7vkvrykv3wm9l8j617v3xbn44g51i-epiphany-3.24.3/share/glib-2.0/schemas/gschemas.compiled /gnu/store/1c7w0pjf80z8l6yb9a8wmni8za3mpx85-simple-scan-3.24.1/share/glib-2.0/schemas/gschemas.compiled
> warning: arbitrarily choosing /gnu/store/7dq7vkvrykv3wm9l8j617v3xbn44g51i-epiphany-3.24.3/share/glib-2.0/schemas/gschemas.compiled
>
> 1.
> How do we deal with these gschema collisions? I know eventually we
> should solve almost all collisions we have, but gschemas seems
> more important than the usual ones.

For reference, here’s the discussion of the same issue by the Nix folks:

  https://github.com/NixOS/nixpkgs/issues/1455

> 2.
> I also think we should formalize how to deal with the collisions
> or specific groups of collisions, so that we might have a better
> way to tackle these issues.

I don’t know what “formalize” means in this context, but I agree that we
should aim to reduce the number of conflicts where possible.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

Display info messages

Send a report that this bug log contains spam.

debbugs.gnu.org maintainers <help-debbugs@gnu.org>. Last modified: Wed Sep 10 15:26:12 2025; Machine Name: wallace-server

GNU bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

#28167 decide how to deal with gschemas