From: baalajimaestro <baalajimaestro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] glibmm2.68: update to 2.76.0.
Date: Fri, 21 Apr 2023 04:33:36 +0200 [thread overview]
Message-ID: <20230421023336.AaZLDoTeyU7CKFDLqUw_mh9mJE263DBYUZNzBwr1hMQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43231@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
There is an updated pull request by baalajimaestro against master on the void-packages repository
https://github.com/baalajimaestro/void-packages update/glibmm2.68/2.76.0
https://github.com/void-linux/void-packages/pull/43231
glibmm2.68: update to 2.76.0.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, glibc, x64
Note: Tested only telegram-desktop, unsure which applications depend on glibmm2.68
A patch file from https://github.com/void-linux/void-packages/pull/43231.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update/glibmm2.68/2.76.0-43231.patch --]
[-- Type: text/x-diff, Size: 1752 bytes --]
From bdf10607cf18d7369240f02eab0a83e98c7fc4a3 Mon Sep 17 00:00:00 2001
From: baalajimaestro <me@baalajimaestro.me>
Date: Mon, 3 Apr 2023 12:12:51 +0530
Subject: [PATCH] glibmm2.68: update to 2.76.0.
Signed-off-by: baalajimaestro <me@baalajimaestro.me>
---
srcpkgs/glibmm2.68/template | 6 ++++--
srcpkgs/glibmm2.68/update | 2 +-
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/glibmm2.68/template b/srcpkgs/glibmm2.68/template
index f6588d954663..d43e796e9954 100644
--- a/srcpkgs/glibmm2.68/template
+++ b/srcpkgs/glibmm2.68/template
@@ -1,8 +1,9 @@
# Template file for 'glibmm2.68'
pkgname=glibmm2.68
-version=2.68.1
+version=2.76.0
revision=1
build_style=meson
+configure_args="-Dbuild-examples=false"
hostmakedepends="glib-devel perl pkg-config"
makedepends="libglib-devel libsigc++3-devel"
checkdepends="glib-networking"
@@ -10,8 +11,9 @@ short_desc="C++ bindings for GLib"
maintainer="Enno Boland <gottox@voidlinux.org>"
license="LGPL-2.1-or-later"
homepage="https://www.gtkmm.org"
+changelog="https://gitlab.gnome.org/GNOME/glibmm/-/raw/master/NEWS"
distfiles="${GNOME_SITE}/glibmm/${version%.*}/glibmm-${version}.tar.xz"
-checksum=6664e27c9a9cca81c29e35687f49f2e0d173a2fc9e98c3428311f707db532f8c
+checksum=8637d80ceabd94fddd6e48970a082a264558d4ab82684e15ffc87e7ef3462ab2
glibmm2.68-devel_package() {
depends="${makedepends} ${sourcepkg}>=${version}_${revision}"
diff --git a/srcpkgs/glibmm2.68/update b/srcpkgs/glibmm2.68/update
index c2768fb0e70f..8173c5f3bac9 100644
--- a/srcpkgs/glibmm2.68/update
+++ b/srcpkgs/glibmm2.68/update
@@ -1,3 +1,3 @@
pkgname=glibmm
site=https://gitlab.gnome.org/GNOME/glibmm/-/tags
-pattern="$pkgname-\K[0-9]\.[0-9]*[02468]\.[0-9.]*[0-9](?=)"
+ignore="*.*[13579].*"
next prev parent reply other threads:[~2023-04-21 2:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 6:46 [PR PATCH] " baalajimaestro
2023-04-11 22:42 ` [PR REVIEW] " mhmdanas
2023-04-14 22:50 ` mhmdanas
2023-04-21 2:33 ` baalajimaestro [this message]
2023-04-24 10:13 ` baalajimaestro
2023-05-07 13:49 ` Johnnynator
2023-05-07 13:49 ` [PR PATCH] [Closed]: " Johnnynator
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=20230421023336.AaZLDoTeyU7CKFDLqUw_mh9mJE263DBYUZNzBwr1hMQ@z \
--to=baalajimaestro@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).