Github messages for voidlinux
 help / color / mirror / Atom feed
From: etech-dev <etech-dev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] autoconf-archive for x86_64
Date: Sun, 23 Jul 2023 15:53:18 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45204@inbox.vuxu.org> (raw)

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

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

https://github.com/etech-dev/void-packages master
https://github.com/void-linux/void-packages/pull/45204

autoconf-archive for x86_64
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

<!--
#### 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-LIBC)



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

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

From 5f7426abf2ebbc3dff592dfc9d70644b69d01dbf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Philippe=20Mar=C3=A9chal?= <philippe@t480.home>
Date: Sun, 23 Jul 2023 15:43:11 +0200
Subject: [PATCH] autoconf-archive for x86_64

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

diff --git a/srcpkgs/autoconf-archive/template b/srcpkgs/autoconf-archive/template
index d791c5cf84c3c..660862c0dd7c4 100644
--- a/srcpkgs/autoconf-archive/template
+++ b/srcpkgs/autoconf-archive/template
@@ -1,13 +1,13 @@
 # Template file for 'autoconf-archive'
 pkgname=autoconf-archive
-version=2022.02.11
+version=2023.02.20
 revision=1
 build_style=gnu-configure
 hostmakedepends="texinfo"
 depends="autoconf"
 short_desc="Collection of freely re-usable Autoconf macros"
-maintainer="Orphaned <orphan@voidlinux.org>"
+maintainer="Philippe Maréchal"
 license="GPL-3.0-or-later"
 homepage="https://www.gnu.org/software/autoconf-archive/"
 distfiles="${GNU_SITE}/${pkgname}/${pkgname}-${version}.tar.xz"
-checksum=78a61b611e2eeb55a89e0398e0ce387bcaf57fe2dd53c6fe427130f777ad1e8c
+checksum=71d4048479ae28f1f5794619c3d72df9c01df49b1c628ef85fde37596dc31a33

             reply	other threads:[~2023-07-23 13:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-23 13:53 etech-dev [this message]
2023-07-23 14:38 ` [PR PATCH] [Updated] " etech-dev
2023-07-23 15:24 ` etech-dev
2023-07-23 15:33 ` [PR PATCH] [Updated] " etech-dev
2023-07-24  9:21 ` etech-dev
2023-07-24 11:43 ` [PR PATCH] [Closed]: " etech-dev

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-45204@inbox.vuxu.org \
    --to=etech-dev@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).