decide how to deal with gschemas

OpenSubmitted by ng0.
Details
2 participants
  • ng0
  • Ricardo Wurmus
Owner
unassigned
Severity
normal
N
(address . bug-guix@gnu.org)
20170820200438.kouji7n6hkr2i6hz@abyayala
Creating manual page database for 59 packages... done in 2.152 swarning: 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.compiledwarning: 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 weshould solve almost all collisions we have, but gschemas seemsmore important than the usual ones.
2.I also think we should formalize how to deal with the collisionsor specific groups of collisions, so that we might have a betterway to tackle these issues.-- ng0GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588GnuPG: https://n0is.noblogs.org/my-keyshttps://www.infotropique.orghttps://krosos.org
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlmZ61YACgkQ4i+bv+40hYgs2BAAjofdrukgQrDfk40GIKg3g5iH42JpgynZ317kQTa/+2IjGRGzSIo5INh6pyUqbhHU14zaBnPQ+U3aGsqM8LE/mX2OPKLTKZLpSJf4HNb9iA3U39iRrffUFXZLkxItOpVcvoFklrGg5cUMm/+qpg6Zw4QXh+S31r/7DTWR/yQJE4v0Xuf5CsmH5UfC992ibqzsRsldCqAlqP3sMgiZVtLs4KeroOCH6/TdUKKH0/rH9UVmOvjUH/DXI3Wqm/ie0hwJS1OjjsAIujXPsPsdbLj0Pvmi3Lgb7JXdfAHb8OzfoJPnzBRWPGAUmVFaFB29OUXZlxWgQcI7z2KpKXfejokNdIjA0eT6+YCxjDR+NEeuyztl6gi81DJ2bJWrbWM5C4USCG0njafEomWktfmvostv+1w6HXN9/u0tAxPVG0pQ3ejlXb2YTknDR8lGHosXS8YHbeJ52z1w9kPCNHYSDGtW3zLkkbPRwWvA6efuFaI2vtCCWcI/uGJ/K5dJCNbsFfHr/3TyCb2AUP0VHmPiyqINPGqHxDRZcjb0kzp7eWAiNiZNjHXQ1oUawr9v/FVhnP5my2OEgslFVlVjykH+u/9d1PmQfNYBTwpBzoO1RUAzNiiqroC+sSIZ+8puPeWHEM4h223FiEUvJX3wYgxALrZ3zDfrn/46/z45Ji2Qhz5FG8U==Gyky-----END PGP SIGNATURE-----

R
R
Ricardo Wurmus wrote on 21 Aug 2017 15:58
(name . ng0)(address . ng0@infotropique.org)(address . 28167@debbugs.gnu.org)
87fuclvx7w.fsf@elephly.net
ng0 <ng0@infotropique.org> writes:
Toggle quote (9 lines)> 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
Toggle quote (5 lines)> 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 weshould aim to reduce the number of conflicts where possible.
-- Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAChttps://elephly.net
?