Github messages for voidlinux
 help / color / mirror / Atom feed
From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: black: update to 21.12b0.
Date: Mon, 20 Jun 2022 03:21:23 +0200	[thread overview]
Message-ID: <20220620012123.NsfW8MkQKtp3RhA7vvN0mo2v02VJnd_SGUxJPbyixMk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34520@inbox.vuxu.org>

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

New comment by jcgruenhage on void-packages repository

https://github.com/void-linux/void-packages/pull/34520#issuecomment-1159864950

Comment:
Actually, this is horrible.. 

`black` does need to be upgraded at the same time, but with the newer version the jupyter tests for black fail, so more along that probably has to be checked as well.

`fava` has other problems and also doesn't want to build. With `fava` also updated, that problem is resolved, but now it has problems determining it's version after switching to pep517 build style as well.

`gandi-cli` fails over a hundred/a fourth of it's tests. Haven't looked deeper.

`magic-wormhole` is not even able to run it's tests in it's current state. It's complaining about wheel and pip not being available.

`papis` is the same story as `magic-wormhole`.

`python3-Flask` also has 4 of it's tests failing, but at least that's less than a percent. The tests I've seen so far all are related to Pytest deprecations, so nothing to really worry about.

`python3-click-threading` is the first of these that's easy enough: Updating it to 0.5.0 makes all of it's tests pass again :)

`termdown` is the same as `papir` and `magic-wormhole`.

`vdirsyncer` actually builds fine, not sure why that failed earlier.

  parent reply	other threads:[~2022-06-20  1:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14  5:33 [PR PATCH] " Goorzhel
2022-06-18  2:13 ` github-actions
2022-06-19  7:11 ` [PR PATCH] [Updated] " Goorzhel
2022-06-19  7:11 ` Goorzhel
2022-06-19  7:23 ` [PR PATCH] [Updated] " Goorzhel
2022-06-19 17:52 ` paper42
2022-06-20  0:02 ` jcgruenhage
2022-06-20  1:21 ` jcgruenhage [this message]
2022-06-20  3:03 ` Goorzhel
2022-06-20  3:03 ` [PR PATCH] [Updated] black: update to 22.3.0 Goorzhel
2022-06-20  3:05 ` Goorzhel
2022-06-20  8:57 ` paper42
2022-06-23  9:53 ` icp1994
2022-06-23 10:03 ` icp1994
2022-06-23 12:08 ` mhmdanas
2022-06-23 12:09 ` mhmdanas
2022-06-25  0:34 ` Goorzhel
2022-06-25  6:36 ` icp1994
2022-06-25  6:38 ` [PR PATCH] [Closed]: " Goorzhel

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=20220620012123.NsfW8MkQKtp3RhA7vvN0mo2v02VJnd_SGUxJPbyixMk@z \
    --to=jcgruenhage@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).