Github messages for voidlinux
 help / color / mirror / Atom feed
From: hazen2215 <hazen2215@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gcompat: update to 1.1.0.
Date: Wed, 28 Jun 2023 05:20:11 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44673@inbox.vuxu.org> (raw)

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

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

https://github.com/hazen2215/void-packages gcompat
https://github.com/void-linux/void-packages/pull/44673

gcompat: update to 1.1.0.
<!-- 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.
-->
- I built this PR locally for my native architecture, (x86_64-musl)


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

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

From 22e8f62bb924a539ea8526aa90b0bc6f3386f704 Mon Sep 17 00:00:00 2001
From: hazen2215 <haz@disroot.org>
Date: Wed, 28 Jun 2023 12:17:25 +0900
Subject: [PATCH] gcompat: update to 1.1.0.

---
 srcpkgs/gcompat/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/gcompat/template b/srcpkgs/gcompat/template
index 3988a933a5a2..dc7a4c3134ba 100644
--- a/srcpkgs/gcompat/template
+++ b/srcpkgs/gcompat/template
@@ -1,7 +1,7 @@
 # Template file for 'gcompat'
 pkgname=gcompat
-version=1.0.0
-revision=2
+version=1.1.0
+revision=1
 build_style=gnu-makefile
 hostmakedepends="pkg-config"
 makedepends="musl-obstack-devel"
@@ -11,7 +11,7 @@ license="ISC"
 homepage="https://code.foxkit.us/adelie/gcompat"
 changelog="https://code.foxkit.us/adelie/gcompat/-/raw/current/CHANGELOG.rst"
 distfiles="https://distfiles.AdelieLinux.org/source/${pkgname}/${pkgname}-${version}.tar.xz"
-checksum=5bcf8bbe4b417bc66b22a7a3675273aa8834480144338172bbd8e81eaf41a7c4
+checksum=4e8c9cbf0615f1ce5d56ce02d84ac9c0a3d38b5bed32e8e02e2105e9658c9d57
 
 build_options="libucontext"
 desc_option_libucontext="Build with ucontext support via libucontext"

             reply	other threads:[~2023-06-28  3:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28  3:20 hazen2215 [this message]
2023-06-28  3:21 ` [PR REVIEW] " classabbyamp
2023-06-28  3:23 ` classabbyamp
2023-06-28  3:44 ` [PR PATCH] [Updated] " hazen2215
2023-06-28  3:45 ` hazen2215
2023-06-28 13:12 ` [PR PATCH] [Updated] " hazen2215
2023-06-29 20:26 ` [PR PATCH] [Merged]: " Duncaen
  -- strict thread matches above, loose matches on Subject: below --
2023-02-22  8:56 [PR PATCH] " varuld

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