Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-yaml: update to 6.0.
Date: Tue, 22 Feb 2022 19:49:43 +0100	[thread overview]
Message-ID: <20220222184943.Z4MVr4FCeDeW-9L5hmKJSh6XPZl8B91qvrs5270sqgU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35743@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/35743#issuecomment-1047247626

Comment:
I've hesitated to update this package because it has a lot of dependants. In particular, I'm worried that some version restrictions in the dependant requirements may prohibit 6.0 or greater, and I'm also concerned about the change https://github.com/yaml/pyyaml/pull/561 (always require `Loader` arg to `yaml.load()`) hard-breaking some of these packages. Before merging this, we should attempt to verify that the following packages won't break and don't place undue version restrictions on `python3-yaml`:

- [ ] Solaar
- [ ] ansible-core
- [ ] aws-cli
- [ ] awsume
- [ ] bandit
- [x] beets
- [x] gandi-cli
- [ ] gnuradio
- [ ] jrnl
- [ ] kapidox
- [ ] lutris
- [ ] papis
- [ ] pass-import
- [ ] peru
- [ ] picard
- [ ] podman-compose
- [ ] pre-commit
- [ ] python3-ansible-lint
- [ ] python3-bokeh
- [x] python3-confuse
- [ ] python3-kaptan
- [ ] python3-pgmigrate
- [ ] python3-pyinfra
- [ ] python3-scruffy
- [ ] python3-vint
- [ ] python3-watchdog
- [ ] python3-yamllint
- [x] qutebrowser
- [ ] rednotebook
- [ ] ripe-atlas-tools
- [ ] salt
- [ ] synapse
- [ ] terminal_markdown_viewer
- [ ] udiskie
- [ ] unknown-horizons
- [ ] urlwatch
- [ ] yq

  parent reply	other threads:[~2022-02-22 18:49 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 21:33 [PR PATCH] " tibequadorian
2022-02-21 21:42 ` ahesford
2022-02-22 18:21 ` TinfoilSubmarine
2022-02-22 18:49 ` ahesford
2022-02-22 18:49 ` ahesford
2022-02-22 18:49 ` ahesford
2022-02-22 18:49 ` ahesford [this message]
2022-02-22 18:49 ` ahesford
2022-02-22 18:52 ` ahesford
2022-02-22 21:06 ` motorto
2022-02-22 21:08 ` ahesford
2022-02-23 12:19 ` tibequadorian
2022-02-25 16:52 ` TinfoilSubmarine
2022-02-25 16:54 ` ahesford
2022-02-25 16:54 ` ahesford
2022-02-25 16:54 ` ahesford
2022-02-25 16:58 ` ahesford
2022-02-25 21:02 ` TinfoilSubmarine
2022-02-25 21:21 ` ahesford
2022-02-25 21:21 ` ahesford
2022-02-25 21:21 ` ahesford
2022-02-25 21:21 ` ahesford
2022-02-25 21:21 ` ahesford
2022-02-25 21:21 ` ahesford
2022-02-25 21:21 ` ahesford
2022-02-25 21:21 ` ahesford
2022-02-25 21:21 ` ahesford
2022-02-26  0:00 ` ahesford
2022-02-26  2:05 ` TinfoilSubmarine
2022-02-26  2:07 ` ahesford
2022-02-26  2:08 ` ahesford
2022-02-26  2:08 ` ahesford
2022-02-26  2:08 ` ahesford
2022-02-26  3:21 ` TinfoilSubmarine
2022-02-26 16:37 ` ahesford
2022-02-27  0:18 ` TinfoilSubmarine
2022-02-27  1:42 ` ahesford
2022-02-27  1:42 ` ahesford
2022-02-27  1:42 ` ahesford
2022-02-27  1:42 ` ahesford
2022-02-27  1:43 ` ahesford
2022-02-27  1:43 ` ahesford
2022-02-27  1:43 ` ahesford
2022-02-27  1:43 ` ahesford
2022-02-27  1:48 ` ahesford
2022-02-27  1:48 ` [PR PATCH] [Merged]: " ahesford

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=20220222184943.Z4MVr4FCeDeW-9L5hmKJSh6XPZl8B91qvrs5270sqgU@z \
    --to=ahesford@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).