From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] mpd: fails to build docs
Date: Mon, 21 Mar 2022 04:00:19 +0100 [thread overview]
Message-ID: <20220321030019.u1hvotFyi2LmyfJM0wYPrX3_OnUeiFkewp_2eFFTEKw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36227@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
Closed issue by tibequadorian on void-packages repository
https://github.com/void-linux/void-packages/issues/36227
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
`Void 5.15.28_1 x86_64 GenuineIntel notuptodate rrrrmmnFFFFFFFFFFFFF`
* package:
`mpd-0.23.6_1`
### Expected behavior
Build is successful
### Actual behavior
```
[656/657] Generating doc/Manpage documentation with a custom command
FAILED: doc/mpd.1 doc/mpd.conf.5
/usr/bin/sphinx-build -q -b man -d doc/man_doctrees /builddir/mpd-0.23.6/doc doc
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 579, in _build_master
ws.require(__requires__)
File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 897, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 788, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (docutils 0.18.1 (/usr/lib/python3.10/site-packages), Requirement.parse('docutils<0.18,>=0.14'), {'Sphinx'})
```
### Steps to reproduce the behavior
`./xbps-src pkg mpd`
Probably related to #36066
prev parent reply other threads:[~2022-03-21 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 19:18 [ISSUE] mpd: fails to build tibequadorian
2022-03-21 3:00 ` sgn [this message]
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=20220321030019.u1hvotFyi2LmyfJM0wYPrX3_OnUeiFkewp_2eFFTEKw@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).