From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-click: update to 8.1.3.
Date: Fri, 24 Jun 2022 05:04:35 +0200 [thread overview]
Message-ID: <20220624030435.f1ei_A1pGKbe7ap5oklGP8H8g_YEAg24fRLE3DwXguw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37629@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
New comment by Goorzhel on void-packages repository
https://github.com/void-linux/void-packages/pull/37629#issuecomment-1165144869
Comment:
`xbps-src check vdirsyncer` seems to be working on my machine now, with `upstream/HEAD` at 2cecb1efcc. I rebased upon `fce1ba0a35` (`HEAD` when I started this PR) and...`do_check` succeeds there too. I've also lost whatever output I used to determine that `vdirsyncer` had regressed. 🤡
That's all the regressions dealt with, anyway. I took a shot at the "Can't test" packages but `papis` sent me down a yak trail that sapped all my energy:
* `ModuleNotFoundError: No module named 'pytest'`, so I added it to `checkdepends`
* Then `error: unrecognized arguments: --cov=papis`, so I added `python3-pytest-cov`
* Then it complained about `whoosh` missing, so I added `python3-Whoosh`
* Then [this](https://0x0.st/oScX.txt) happened
next prev parent reply other threads:[~2022-06-24 3:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 0:14 [PR PATCH] " Goorzhel
2022-06-21 0:14 ` Goorzhel
2022-06-21 0:38 ` Goorzhel
2022-06-22 2:28 ` Goorzhel
2022-06-22 2:39 ` Goorzhel
2022-06-22 2:39 ` Goorzhel
2022-06-22 3:46 ` Goorzhel
2022-06-22 11:53 ` leahneukirchen
2022-06-22 12:11 ` leahneukirchen
2022-06-24 1:05 ` Goorzhel
2022-06-24 1:06 ` [PR PATCH] [Updated] " Goorzhel
2022-06-24 2:50 ` Goorzhel
2022-06-24 3:03 ` Goorzhel
2022-06-24 3:04 ` Goorzhel [this message]
2022-06-24 15:36 ` ahesford
2022-06-24 16:48 ` [PR PATCH] [Updated] " leahneukirchen
2022-06-24 18:45 ` paper42
2022-06-24 18:49 ` leahneukirchen
2022-06-24 19:28 ` icp1994
2022-06-24 19:38 ` [PR PATCH] [Updated] " leahneukirchen
2022-06-24 19:52 ` [PR PATCH] [Merged]: " leahneukirchen
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=20220624030435.f1ei_A1pGKbe7ap5oklGP8H8g_YEAg24fRLE3DwXguw@z \
--to=goorzhel@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).