Github messages for voidlinux
 help / color / mirror / Atom feed
From: TeddyDD <TeddyDD@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] chroma: update to 2.9.1.
Date: Sat, 09 Sep 2023 21:16:11 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45994@inbox.vuxu.org> (raw)

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

There is a new pull request by TeddyDD against master on the void-packages repository

https://github.com/TeddyDD/void-packages-1 update-chroma
https://github.com/void-linux/void-packages/pull/45994

chroma: update to 2.9.1.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/45994.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-chroma-45994.patch --]
[-- Type: text/x-diff, Size: 1213 bytes --]

From 08f66ca3ca237ff6b4561a3666c0142d92b6e552 Mon Sep 17 00:00:00 2001
From: Daniel Lewan <daniel@teddydd.me>
Date: Sat, 9 Sep 2023 21:15:08 +0200
Subject: [PATCH] chroma: update to 2.9.1.

---
 srcpkgs/chroma/template | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/chroma/template b/srcpkgs/chroma/template
index 64e204d6b1406..44d8f63e7e820 100644
--- a/srcpkgs/chroma/template
+++ b/srcpkgs/chroma/template
@@ -1,17 +1,17 @@
 # Template file for 'chroma'
 pkgname=chroma
-version=2.8.0
-revision=2
+version=2.9.1
+revision=1
 build_wrksrc="cmd/chroma"
 build_style=go
 go_import_path="github.com/alecthomas/chroma/v2/cmd/chroma"
 go_ldflags="-X main.version=${version} -X main.date=$(date +%Y.%m.%d)"
 short_desc="General purpose syntax highlighter"
-maintainer="Daniel Lewan <vision360.daniel@gmail.com>"
+maintainer="Daniel Lewan <daniel@teddydd.me>"
 license="MIT"
 homepage="https://github.com/alecthomas/chroma"
 distfiles="https://github.com/alecthomas/chroma/archive/v${version}.tar.gz"
-checksum=d6ddb56fd3cf0d7ae2c592f834aced1be4494f21338a79636743c25305a65a00
+checksum=4f58ad5b33d8a8681b085e57303a85cb39158a62349dfb8bd16e780a049d788b
 
 do_check() {
 	go test -v

             reply	other threads:[~2023-09-09 19:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-09 19:16 TeddyDD [this message]
2023-09-12  5:41 ` [PR PATCH] [Merged]: " 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-45994@inbox.vuxu.org \
    --to=teddydd@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).