Github messages for voidlinux
 help / color / mirror / Atom feed
From: varuld <varuld@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gcompat: update to 1.1.0
Date: Wed, 22 Feb 2023 09:56:44 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42393@inbox.vuxu.org> (raw)

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

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

https://github.com/varuld/void-packages gcompat_version_update_to_1.1.0
https://github.com/void-linux/void-packages/pull/42393

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:**NO** 
(I do not use this package on a daily basis and I therefore do not know what to test it with.)

<!--
#### 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,-musl), with '-Q' flag




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

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

From a3900c825173e0a0565041d7ce54d1ddee9dc575 Mon Sep 17 00:00:00 2001
From: varuld <redinkunicorn@gmail.com>
Date: Tue, 21 Feb 2023 15:08:33 +0100
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-02-22  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22  8:56 varuld [this message]
2023-05-25  1:53 ` github-actions
2023-06-08  2:04 ` [PR PATCH] [Closed]: " github-actions
2023-06-28  3:20 [PR PATCH] " hazen2215

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