From: Jacob MacDonald <jaccarmac@gmail.com>
To: 54033@debbugs.gnu.org
Subject: bug#54033: Fwd: bug#54033: Calibre's ebook-viewer only shows white-on-white or dark-on-dark.
Date: Sat, 19 Feb 2022 23:05:30 -0600 [thread overview]
Message-ID: <CACy6W0Bdy5sDxZv4VDZCRH6KhVqsiSsF2_66s1RvDjRYbMLUwQ@mail.gmail.com> (raw)
In-Reply-To: <CACy6W0Aj8CAnc47p_R5rHw2d3vNaFEoKaxhRRJRXyhVQekcR7w@mail.gmail.com>
---------- Forwarded message ---------
From: Jacob MacDonald <jaccarmac@gmail.com>
Date: Fri, Feb 18, 2022 at 8:52 PM
Subject: Re: bug#54033: Calibre's ebook-viewer only shows
white-on-white or dark-on-dark.
To: Leo Famulari <leo@famulari.name>
On Thu, Feb 17, 2022 at 5:41 PM Leo Famulari <leo@famulari.name> wrote:
> Did you check if this bug has been reported upstream?
I gave the Launchpad a cursory check but wasn't able to find what I
was looking for.
In addition, I scrolled back through the Git history a ways and found
a commit that seems to have working Calibre at the same version.
$ guix time-machine --commit=9d25ee30b188f9202cc14f7cd25ba8a1c3ec1a72
-- package --show=calibre
name: calibre
version: 5.21.0
,,,
$ guix time-machine --commit=9d25ee30b188f9202cc14f7cd25ba8a1c3ec1a72
-- shell calibre -- ebook-viewer
brings up a working version of the reader.
Thank you for the information about the time-machine command.
I started to do a Git bisect on my copy of the repository, but found
that it was intractable to build the versions of Guix necessary. Part
of that seems to be related to some merges: Some of the candidate
commits had dates from 2020 on them and the candidate set was rather
large. Is there a smarter way to hunt down the commit where Calibre
broke?
next prev parent reply other threads:[~2022-02-20 5:06 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 ` Jacob MacDonald [this message]
[not found] ` <18be745d-10bf-4be9-bef3-c88cc88d9554@www.fastmail.com>
2022-02-20 5:05 ` bug#54033: Fwd: " 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
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=CACy6W0Bdy5sDxZv4VDZCRH6KhVqsiSsF2_66s1RvDjRYbMLUwQ@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).