unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jacob MacDonald <jaccarmac@gmail.com>
To: 54033@debbugs.gnu.org
Subject: bug#54033: Calibre's ebook-viewer only shows white-on-white or dark-on-dark.
Date: Thu, 3 Mar 2022 22:07:51 -0600	[thread overview]
Message-ID: <CACy6W0CoOVnje0QPXPbjEt-QOo5A_kt2u6k5HhsRH0ayr=23eg@mail.gmail.com> (raw)
In-Reply-To: <CACy6W0Czc1aLqX9SOhnMCtUUKpK4bXkoEDF1_XrxMpzjbGx4JA@mail.gmail.com>

Jesse wrote:
> I do not know if this is specific to guix or a problem generally with Calibre 5.36.

As far as I can tell, it's a problem introduced by Guix, as I noticed
it occurring with Calibre 5.21. For what it's worth, I have the latest
working version that I can find installed.

guix time-machine --commit=b603554ed044638dd40b6863d5dada59eefe03b8 --
package -i calibre

Leo:

I've continued to attempt the last bisect I mentioned, but I'm bogged
down by repeated build errors that force me to skip more commits than
I can test. Is there a trick to building the commits which got merged
in; Do they not work with time-machine? The errors I'm seeing are of
the form:

guix time-machine: error: You found a bug: the program
'/gnu/store/mqhfdbrl834biajwq667fzsck344g09s-compute-guix-derivation'
failed to compute the derivation for Guix (version:
"b2b799e2d8330af934f48bf66afb5114addb4dd7"; system: "x86_64-linux";
host version: "1af78ab5e80b98d1914b85709c60fa7f9782e1db"; pull-version: 1).
Please report it by email to <bug-guix@gnu.org>.

That latest failure seems to be related to tcsh, but that's not the
only derivation which has failed for me in the same way.




  reply	other threads:[~2022-03-04  4:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17  7:05 bug#54033: Calibre's ebook-viewer only shows white-on-white or dark-on-dark Jacob MacDonald
2022-02-17 23:41 ` Leo Famulari
2022-02-20  3:39   ` Jacob MacDonald
2022-02-20  4:33     ` Leo Famulari
     [not found]   ` <CACy6W0Aj8CAnc47p_R5rHw2d3vNaFEoKaxhRRJRXyhVQekcR7w@mail.gmail.com>
2022-02-20  5:05     ` bug#54033: Fwd: " Jacob MacDonald
     [not found]     ` <18be745d-10bf-4be9-bef3-c88cc88d9554@www.fastmail.com>
2022-02-20  5:05       ` Jacob MacDonald
     [not found]       ` <CACy6W0AaVRTrrduJPi_ZCWyoMK8KoKDbEyVWEFQ2xtgZxRMgQg@mail.gmail.com>
2022-02-20  5:05         ` Jacob MacDonald
2022-02-21  3:46           ` Jacob MacDonald
2022-02-21  6:00             ` Jacob MacDonald
2022-02-22  4:51               ` Jacob MacDonald
2022-03-04  4:07                 ` Jacob MacDonald [this message]
2022-03-04 13:19                   ` Leo Famulari
2022-03-04 18:19                     ` Jacob MacDonald
2022-03-04 14:07 ` Guillaume Le Vaillant
2022-03-04 20:27   ` bdju via Bug reports for GNU Guix
2022-03-08 14:52     ` Guillaume Le Vaillant

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='CACy6W0CoOVnje0QPXPbjEt-QOo5A_kt2u6k5HhsRH0ayr=23eg@mail.gmail.com' \
    --to=jaccarmac@gmail.com \
    --cc=54033@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 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).