From: Zyrtula <Zyrtula@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-lsp-server: update to 1.11.0.
Date: Sun, 16 Jun 2024 01:20:52 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50844@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
There is a new pull request by Zyrtula against master on the void-packages repository
https://github.com/Zyrtula/void-packages python-lsp-server
https://github.com/void-linux/void-packages/pull/50844
python3-lsp-server: update to 1.11.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### 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, **x86_64**
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- x86_64-musl
A patch file from https://github.com/void-linux/void-packages/pull/50844.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python-lsp-server-50844.patch --]
[-- Type: text/x-diff, Size: 1218 bytes --]
From 52a2fa017c7919731839dd0467f826159f75c7c0 Mon Sep 17 00:00:00 2001
From: Zyrtula <fk_development@protonmail.com>
Date: Sun, 16 Jun 2024 01:16:55 +0200
Subject: [PATCH] python3-lsp-server: update to 1.11.0.
---
srcpkgs/python3-lsp-server/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/python3-lsp-server/template b/srcpkgs/python3-lsp-server/template
index 41e3d69f897bee..63189e1a2b412d 100644
--- a/srcpkgs/python3-lsp-server/template
+++ b/srcpkgs/python3-lsp-server/template
@@ -1,6 +1,6 @@
# Template file for 'python3-lsp-server'
pkgname=python3-lsp-server
-version=1.10.0
+version=1.11.0
revision=1
build_style=python3-module
hostmakedepends="python3-setuptools python3-setuptools_scm python3-wheel"
@@ -16,7 +16,7 @@ license="MIT"
homepage="https://github.com/python-lsp/python-lsp-server"
changelog="https://raw.githubusercontent.com/python-lsp/python-lsp-server/develop/CHANGELOG.md"
distfiles="${PYPI_SITE}/p/python-lsp-server/python-lsp-server-${version}.tar.gz"
-checksum=0c9a52dcc16cd0562404d529d50a03372db1ea6fb8dfcc3792b3265441c814f4
+checksum=89edd6fb3f7852e4bf5a3d1d95ea41484d1a28fa94b6e3cbff12b9db123b8e86
do_check() {
python3 -m pytest \
next reply other threads:[~2024-06-15 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 23:20 Zyrtula [this message]
2024-06-16 22:28 ` [PR PATCH] [Closed]: " classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50844@inbox.vuxu.org \
--to=zyrtula@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).