all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jack Hill <jackhill@jackhill.us>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: 37911@debbugs.gnu.org
Subject: bug#37911: Cannot build a system with colord-service.
Date: Thu, 24 Oct 2019 17:19:52 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.20.1910241713580.11560@marsh.hcoop.net> (raw)
In-Reply-To: <87ftjhyi4l.fsf@gmx.com>

On Thu, 24 Oct 2019, Pierre Langlois wrote:

> In gnome's settings it tells me that there are no devices that can be
> colour managed, I had assumed that was because colord was missing from
> the config but that's probably not it. Is it working for other people?
> If so it's probably just my hardware (ThinkPad x220).

I think it is not able to manage devices because the Argyll CMS dependency 
[0] is missing in Guix. Unfortunately, it seems to also depend on the 
discontinued Jam build tool [1], so there is a little bit of work to be 
done.

[0] https://argyllcms.com/
[1] https://www.perforce.com/documentation/jam-documentation

I did spot another issue with colord since the recent core-updates merge: 
https://issues.guix.gnu.org/issue/37843 It seems like it is no longer 
being started automatically via dbus?

Hope that helps,
Jack

  reply	other threads:[~2019-10-24 21:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 20:45 bug#37911: Cannot build a system with colord-service Pierre Langlois
2019-10-24 20:50 ` Pierre Langlois
2019-10-24 20:59   ` Pierre Langlois
2019-10-24 21:19     ` Jack Hill [this message]
2019-10-25 21:05       ` Ludovic Courtès
2019-11-01 23:17         ` bug#37843: " Ludovic Courtès
2019-11-02 14:11           ` Pierre Langlois
2019-11-04 17:20             ` Ludovic Courtès
2019-11-02 14:14           ` Jack Hill
2019-10-24 20:51 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix

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=alpine.DEB.2.20.1910241713580.11560@marsh.hcoop.net \
    --to=jackhill@jackhill.us \
    --cc=37911@debbugs.gnu.org \
    --cc=pierre.langlois@gmx.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 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.