From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-language-server: fix compatibility with jedi 0.18.0
Date: Sun, 27 Jun 2021 03:11:33 +0200 [thread overview]
Message-ID: <20210627011133.MACrQYRDxWOi1FomRlcp5EDeqitg8hEzDgUnXi9m74w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31650@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/31650#issuecomment-869082693
Comment:
Looks like nothing depends on this package, so moving to a more active upstream seems OK if we have to keep patching. It would be good to get some kind of blessing from the original upstream if possible.
Also, because `make_check=no`, this should have not had any `checkdepends`; all of those packages get installed when building with `-Q` or `-K`, but they aren't actually used because tests are skipped for this template.
prev parent reply other threads:[~2021-06-27 1:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 8:13 [PR PATCH] " not-chicken
2021-06-25 8:49 ` [PR PATCH] [Updated] " not-chicken
2021-06-26 21:34 ` ericonr
2021-06-26 21:35 ` [PR PATCH] [Merged]: " ericonr
2021-06-27 1:11 ` ahesford [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=20210627011133.MACrQYRDxWOi1FomRlcp5EDeqitg8hEzDgUnXi9m74w@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).