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: Mon, 21 Feb 2022 00:00:39 -0600	[thread overview]
Message-ID: <CACy6W0D_LPTuO6Lh05+Gtm8xPhFtLqEBzS1jYUxKQz+qGThXTg@mail.gmail.com> (raw)
In-Reply-To: <CACy6W0AQmhc7ZXSyQm5vEtTNfBFGUdRGCUANnHvgmGkyPJS9NQ@mail.gmail.com>

After looking into what I think was core-updates(-frozen), I am
running into a wall in the form of glib-networking, which blocks my
attempts to build Calibre on many commits. However, I did find another
merge which may be of interest:
b029be2ee0f81cdcbc14240ff426408085ab0a40. One side of it,
ffb381856d0c6cc1a557b789f6b377cfa17002a0, contains a working version
of Calibre 5.21. I can't verify that the other side fails due to the
mentioned glib-networking blocker. However, the common ancestor of the
commits in question is 8b1bde7bb3936a64244824500ffe60f123704437, which
has an older but still working version of Calibre: 5.14. I'm out of
ideas for the moment: The differences in the Calibre recipe between
branches are very small, but I don't know how to bisect here more
effectively, get the core-updates-frozen commits to build, or dig into
the Python build process.




  reply	other threads:[~2022-02-21  6:01 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 [this message]
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=CACy6W0D_LPTuO6Lh05+Gtm8xPhFtLqEBzS1jYUxKQz+qGThXTg@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).