Github messages for voidlinux
 help / color / mirror / Atom feed
From: baalajimaestro <baalajimaestro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] glibmm2.68: update to 2.76.0.
Date: Mon, 03 Apr 2023 08:46:35 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43231@inbox.vuxu.org> (raw)

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

There is a new 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: **NO**

#### Local build testing
- I built this PR locally for my native architecture, glibc, x64

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: 1151 bytes --]

From b3222e8ffb9241709b1aba9f73c9f92145d22364 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 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/glibmm2.68/template b/srcpkgs/glibmm2.68/template
index f6588d954663..1eb983c85f64 100644
--- a/srcpkgs/glibmm2.68/template
+++ b/srcpkgs/glibmm2.68/template
@@ -1,6 +1,6 @@
 # Template file for 'glibmm2.68'
 pkgname=glibmm2.68
-version=2.68.1
+version=2.76.0
 revision=1
 build_style=meson
 hostmakedepends="glib-devel perl pkg-config"
@@ -11,7 +11,7 @@ maintainer="Enno Boland <gottox@voidlinux.org>"
 license="LGPL-2.1-or-later"
 homepage="https://www.gtkmm.org"
 distfiles="${GNOME_SITE}/glibmm/${version%.*}/glibmm-${version}.tar.xz"
-checksum=6664e27c9a9cca81c29e35687f49f2e0d173a2fc9e98c3428311f707db532f8c
+checksum=8637d80ceabd94fddd6e48970a082a264558d4ab82684e15ffc87e7ef3462ab2
 
 glibmm2.68-devel_package() {
 	depends="${makedepends} ${sourcepkg}>=${version}_${revision}"

             reply	other threads:[~2023-04-03  6:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03  6:46 baalajimaestro [this message]
2023-04-11 22:42 ` [PR REVIEW] " mhmdanas
2023-04-14 22:50 ` mhmdanas
2023-04-21  2:33 ` [PR PATCH] [Updated] " baalajimaestro
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43231@inbox.vuxu.org \
    --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).