GNU bug report logs - #28167
decide how to deal with gschemas

Previous Next

To reply to this bug, email your comments to 28167 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: ng0 <ng0 <at> infotropique.org>
To: bug-guix <at> gnu.org
Subject: decide how to deal with gschemas
Date: Sun, 20 Aug 2017 20:04:38 +0000

[Message part 1 (text/plain, inline)]

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.

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.
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

[signature.asc (application/pgp-signature, inline)]

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

From: Ricardo Wurmus <rekado <at> elephly.net>
To: ng0 <ng0 <at> infotropique.org>
Cc: 28167 <at> debbugs.gnu.org
Subject: Re: bug#28167: decide how to deal with gschemas
Date: Mon, 21 Aug 2017 15:58:43 +0200

ng0 <ng0 <at> 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

Previous Next

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