From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: python3-rich: update dependencies
Date: Wed, 01 Feb 2023 15:58:23 +0100 [thread overview]
Message-ID: <20230201145823.vUGLvut6XZ2QP9Kzf7AACK0El03yvm1LGQSGRXxFeDI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42011@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2397 bytes --]
There's a merged pull request on the void-packages repository
python3-rich: update dependencies
https://github.com/void-linux/void-packages/pull/42011
Description:
- New package: python3-mdurl-0.1.2
- New package: python3-markdown-it-2.1.0
- python3-rich: update dependencies
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
I ran into a problem with this today:
```
Traceback (most recent call last):
File "/usr/bin/ansible-lint", line 5, in <module>
from ansiblelint.__main__ import _run_cli_entrypoint
File "/usr/lib/python3.11/site-packages/ansiblelint/__main__.py", line 40, in <module>
from ansiblelint import cli
File "/usr/lib/python3.11/site-packages/ansiblelint/cli.py", line 26, in <module>
from ansiblelint.yaml_utils import clean_json
File "/usr/lib/python3.11/site-packages/ansiblelint/yaml_utils.py", line 44, in <module>
from ansiblelint.utils import get_action_tasks, normalize_task
File "/usr/lib/python3.11/site-packages/ansiblelint/utils.py", line 56, in <module>
from ansiblelint.app import get_app
File "/usr/lib/python3.11/site-packages/ansiblelint/app.py", line 16, in <module>
from ansiblelint.color import console, console_stderr, render_yaml
File "/usr/lib/python3.11/site-packages/ansiblelint/color.py", line 7, in <module>
import rich.markdown
File "/usr/lib/python3.11/site-packages/rich/markdown.py", line 5, in <module>
from markdown_it import MarkdownIt
ModuleNotFoundError: No module named 'markdown_it'
```
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2023-02-01 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 12:08 [PR PATCH] " jcgruenhage
2023-02-01 12:56 ` [PR REVIEW] " sgn
2023-02-01 14:08 ` [PR PATCH] [Updated] " jcgruenhage
2023-02-01 14:58 ` 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=20230201145823.vUGLvut6XZ2QP9Kzf7AACK0El03yvm1LGQSGRXxFeDI@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).