unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Paul Dufresne <dufresnep@gmail.com>
Cc: 27976@debbugs.gnu.org
Subject: bug#27976: install 32b xfce no gnome: collision hicolor/icon-theme.cache
Date: Mon, 21 Aug 2017 17:40:12 +0200	[thread overview]
Message-ID: <87r2w5rktf.fsf@gnu.org> (raw)
In-Reply-To: <CAGQ-=q3Z7Mb+56Zog3dS5-oJv2yO=h9W1PwzOM6ymWAkYxPsyA@mail.gmail.com> (Paul Dufresne's message of "Sat, 5 Aug 2017 21:05:53 +0000")

Paul Dufresne <dufresnep@gmail.com> skribis:

> After having problem with adwaita-icon-them-3.24.0, (reported in other bug)
>  I decided to give a try by removing gnome service from the
> list of "meta-package" to install.
>
> So in fact keeping 'only' XFCE.
>
> I tried two times, once after the adwaita problem, the other after a reboot
> and from scratch (except partitioning).
>
> The result was the same (from poorly taken notes):
> ...
> warning: collision encountered:
> /gnu/store/7qnfb279...hicolor/icon-theme.cache
> ...
> warning: arbitrarily choosing 7qnfb...icons/hicolor/icons-theme.cache

This is a harmless warning.

> Backtrace:
> In Ice-0/boot-9.scm
> ...
> In unknown file
>    gtk-in-modules-builder

This looks like the real error, but unfortunately we don’t have enough
details here to see what the failure was.  It would have been helpful to
see the whole backtrace or the actual “ERROR” line, along with the line
that says precisely which derivation failed (though I understand it’s
hard to grab that info while you’re installing.)

Thanks,
Ludo’.

      parent reply	other threads:[~2017-08-21 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-05 21:05 bug#27976: install 32b xfce no gnome: collision hicolor/icon-theme.cache Paul Dufresne
2017-08-07  0:31 ` Paul Dufresne
2017-08-21 15:40 ` Ludovic Courtès [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r2w5rktf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=27976@debbugs.gnu.org \
    --cc=dufresnep@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).