unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Aleksandr Vityazev <avityazev@posteo.org>
Cc: 52721@debbugs.gnu.org
Subject: [bug#52721] [PATCH]v2 gnu: python-pydata-sphinx-theme: Fix build.
Date: Wed, 22 Dec 2021 18:25:55 +0000	[thread overview]
Message-ID: <c2a40cf5fe74db5d508c88bf8bd3d6e455d28d06.camel@telenet.be> (raw)
In-Reply-To: <87r1a433my.fsf_-_@posteo.org>

Aleksandr Vityazev schreef op wo 22-12-2021 om 18:17 [+0000]:
> 
> > > the build fails because a package is required python-docutils <
> > > 0.17.
> > 
> > Is python-docutils<0.17 truly required, or are the version
> > requirements
> > in the source code overly strict? If it's the latter, you could
> > patch
> > the source code to relax the requirements.
> > 
> > The latter happens often, because library developers often don't
> > know
> > in advance whether the library is compatible with future versions
> > of
> > the dependencies.
> 
> For version 0.6.3 there is a file
> pydata-sphinx-theme-0.6.3/docs/requirements.txt where the last line
> contains:
> 
> docutils==0.16 # temporary pin (0.17 broken captions).
> 
> Also, the master version requires "docutils!=0.17.0.
> 
> So I created a patch that adds an extra phase.

In that case, docutil<0.17 appears to be actually required, so the
solution would be to use docutils=0.15 as you did originally, I think?
Preferably with a comment ; captions are broken in 0.17..

Greetings,
Maxime.





  reply	other threads:[~2021-12-22 18:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 22:34 [bug#52721] [PATCH] gnu: python-pydata-sphinx-theme: Fix build Aleksandr Vityazev
2021-12-22 10:53 ` Maxime Devos
2021-12-22 18:17   ` [bug#52721] [PATCH]v2 " Aleksandr Vityazev
2021-12-22 18:25     ` Maxime Devos [this message]
2021-12-23 22:54       ` [bug#52721] [PATCH] " Aleksandr Vityazev
2021-12-25 20:02         ` bug#52721: " Efraim Flashner

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=c2a40cf5fe74db5d508c88bf8bd3d6e455d28d06.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=52721@debbugs.gnu.org \
    --cc=avityazev@posteo.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).