From: fanyx <fanyx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] gnome-keyring: update to 46.1.
Date: Mon, 25 Mar 2024 22:49:24 +0100 [thread overview]
Message-ID: <20240325214924.314C32044E@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49422@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
There is an updated pull request by fanyx against master on the void-packages repository
https://github.com/fanyx/void-packages gnome-keyring
https://github.com/void-linux/void-packages/pull/49422
gnome-keyring: update to 46.1.
#### Testing the changes
- I tested the changes in this PR: **NO**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/49422.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gnome-keyring-49422.patch --]
[-- Type: text/x-diff, Size: 1358 bytes --]
From ea85dbec101a9a2c2ad751d5edf82dd0ecb166e5 Mon Sep 17 00:00:00 2001
From: fanyx <fanyx@posteo.net>
Date: Thu, 21 Mar 2024 12:10:48 +0100
Subject: [PATCH] gnome-keyring: update to 46.1.
---
srcpkgs/gnome-keyring/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/gnome-keyring/template b/srcpkgs/gnome-keyring/template
index d3726bb966bca0..484438e8356954 100644
--- a/srcpkgs/gnome-keyring/template
+++ b/srcpkgs/gnome-keyring/template
@@ -1,6 +1,6 @@
# Template file for 'gnome-keyring'
pkgname=gnome-keyring
-version=42.1
+version=46.1
revision=1
build_style=gnu-configure
configure_args="--with-pam-dir=/usr/lib/security --disable-schemas-compile"
@@ -13,8 +13,8 @@ maintainer="Érico Nogueira <ericonr@disroot.org>"
license="GPL-2.0-or-later, LGPL-2.1-or-later"
homepage="https://wiki.gnome.org/Projects/GnomeKeyring/"
changelog="https://gitlab.gnome.org/GNOME/gnome-keyring/-/raw/master/NEWS"
-distfiles="${GNOME_SITE}/$pkgname/${version%.*}/$pkgname-$version.tar.xz"
-checksum=c7f4d040cc76a6b7fe67e08ef9106911c3c80d40fc88cbfc8e2684a4c946e3e6
+distfiles="${GNOME_SITE}/gnome-keyring/${version%.*}/gnome-keyring-${version}.tar.xz"
+checksum=b1d3ae9132ff2f8b3f25a190790892968e3d0acf952a487e40f644a8550ce3f6
lib32disabled=yes
make_check_pre="dbus-run-session xvfb-run"
make_check=ci-skip # times out
next prev parent reply other threads:[~2024-03-25 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 11:11 [PR PATCH] " fanyx
2024-03-21 11:14 ` fanyx
2024-03-25 21:31 ` [PR REVIEW] " oreo639
2024-03-25 21:49 ` fanyx [this message]
2024-04-16 23:28 ` oreo639
2024-04-16 23:29 ` oreo639
2024-04-16 23:30 ` oreo639
2024-04-16 23:30 ` oreo639
2024-04-17 1:53 ` oreo639
2024-04-17 1:59 ` oreo639
2024-04-17 2:03 ` oreo639
2024-04-17 11:25 ` [PR PATCH] [Updated] " fanyx
2024-04-17 23:41 ` [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=20240325214924.314C32044E@inbox.vuxu.org \
--to=fanyx@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).