From: ng0 <ng0@infotropique.org>
To: 28167@debbugs.gnu.org
Subject: bug#28167: decide how to deal with gschemas
Date: Sun, 20 Aug 2017 20:04:38 +0000 [thread overview]
Message-ID: <20170820200438.kouji7n6hkr2i6hz@abyayala> (raw)
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-08-20 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 20:04 ng0 [this message]
2017-08-21 13:58 ` bug#28167: decide how to deal with gschemas Ricardo Wurmus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170820200438.kouji7n6hkr2i6hz@abyayala \
--to=ng0@infotropique.org \
--cc=28167@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.