Github messages for voidlinux
 help / color / mirror / Atom feed
From: clyhtsuriva <clyhtsuriva@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] chuck: update to 1.4.1.1
Date: Wed, 25 May 2022 00:21:36 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37281@inbox.vuxu.org> (raw)

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

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

https://github.com/clyhtsuriva/void-packages chuck-update
https://github.com/void-linux/void-packages/pull/37281

chuck: update to 1.4.1.1
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-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 (crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl



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

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

From 5f589d7f417f40e379e2a2e1a28b342af1bf5883 Mon Sep 17 00:00:00 2001
From: clyhtsuriva <aimeric@adjutor.xyz>
Date: Wed, 25 May 2022 00:18:30 +0200
Subject: [PATCH] chuck: update to 1.4.1.1

---
 srcpkgs/chuck/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/chuck/template b/srcpkgs/chuck/template
index 9c6c8be9364a..d3e8b67c77a6 100644
--- a/srcpkgs/chuck/template
+++ b/srcpkgs/chuck/template
@@ -1,6 +1,6 @@
 # Template file for 'chuck'
 pkgname=chuck
-version=1.4.1.0
+version=1.4.1.1
 revision=1
 build_wrksrc=src
 build_style=gnu-makefile
@@ -14,7 +14,7 @@ license="GPL-2.0-or-later"
 homepage="http://chuck.cs.princeton.edu"
 changelog="https://chuck.cs.princeton.edu/release/VERSIONS"
 distfiles="http://chuck.cs.princeton.edu/release/files/$pkgname-$version.tgz"
-checksum=74bf99ad515e3113c55b833152936fad02a3cf006a54105ff11777c473194928
+checksum=4459ee6f151da72dcde1525e0afe05329d61086356b168ecfc0bc3a570290f63
 
 
 post_extract() {

             reply	other threads:[~2022-05-24 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 22:21 clyhtsuriva [this message]
2022-08-27  7:45 ` clyhtsuriva
2022-08-27  7:45 ` [PR PATCH] [Closed]: " clyhtsuriva

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-37281@inbox.vuxu.org \
    --to=clyhtsuriva@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).