From: chrysos349 <chrysos349@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libsigc++: update to 2.12.1
Date: Tue, 05 Mar 2024 07:42:06 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49098@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
There is a new pull request by chrysos349 against master on the void-packages repository
https://github.com/chrysos349/void-packages libsigc++
https://github.com/void-linux/void-packages/pull/49098
libsigc++: update to 2.12.1
split into a separate pr (https://github.com/void-linux/void-packages/pull/48762#issuecomment-1976502687).
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl x
- armv7l x
- armv6l-musl x
A patch file from https://github.com/void-linux/void-packages/pull/49098.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libsigc++-49098.patch --]
[-- Type: text/x-diff, Size: 1120 bytes --]
From 214d169d934254747de2c5bfb5219cc57f48c9a9 Mon Sep 17 00:00:00 2001
From: chrysos349 <chrysostom349@gmail.com>
Date: Tue, 5 Mar 2024 09:41:15 +0300
Subject: [PATCH] libsigc++: update to 2.12.1
---
srcpkgs/libsigc++/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/libsigc++/template b/srcpkgs/libsigc++/template
index af89ef2db31c6a..d655ce710ef832 100644
--- a/srcpkgs/libsigc++/template
+++ b/srcpkgs/libsigc++/template
@@ -1,6 +1,6 @@
# Template file for 'libsigc++'
pkgname=libsigc++
-version=2.12.0
+version=2.12.1
revision=1
build_style=meson
configure_args="-Dbuild-examples=false -Dwarnings=max"
@@ -10,7 +10,7 @@ maintainer="Enno Boland <gottox@voidlinux.org>"
license="LGPL-2.1-or-later"
homepage="https://libsigcplusplus.github.io/libsigcplusplus/"
distfiles="${GNOME_SITE}/libsigc++/${version%.*}/libsigc++-${version}.tar.xz"
-checksum=1c466d2e64b34f9b118976eb21b138c37ed124d0f61497df2a90ce6c3d9fa3b5
+checksum=a9dbee323351d109b7aee074a9cb89ca3e7bcf8ad8edef1851f4cf359bd50843
if [ -z "$XBPS_CHECK_PKGS" ]; then
configure_args+=" -Dbuild-tests=false"
next reply other threads:[~2024-03-05 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 6:42 chrysos349 [this message]
2024-03-15 7:14 ` oreo639
2024-03-15 7:51 ` [PR PATCH] [Updated] " chrysos349
2024-03-15 7:55 ` chrysos349
2024-03-16 20:08 ` [PR PATCH] [Merged]: " oreo639
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-49098@inbox.vuxu.org \
--to=chrysos349@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).