From: fanyx <fanyx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] nautilus: update to 46.0.
Date: Thu, 21 Mar 2024 15:44:00 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49427@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
There is a new pull request by fanyx against master on the void-packages repository
https://github.com/fanyx/void-packages nautilus
https://github.com/void-linux/void-packages/pull/49427
nautilus: update to 46.0.
#### Testing the changes
- I tested the changes in this PR: **NO**
#### Notes
- Requires `glib>=2.79.0`
#### 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/49427.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-nautilus-49427.patch --]
[-- Type: text/x-diff, Size: 1346 bytes --]
From 50a6e7d7681184df11586808c56b2c913dfce210 Mon Sep 17 00:00:00 2001
From: fanyx <fanyx@posteo.net>
Date: Thu, 21 Mar 2024 14:30:10 +0100
Subject: [PATCH] nautilus: update to 46.0.
---
srcpkgs/nautilus/template | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/nautilus/template b/srcpkgs/nautilus/template
index b9ff7241042445..212a1b86a9ac36 100644
--- a/srcpkgs/nautilus/template
+++ b/srcpkgs/nautilus/template
@@ -1,6 +1,6 @@
# Template file for 'nautilus'
pkgname=nautilus
-version=45.2.1
+version=46.0
revision=1
build_style=meson
build_helper="gir"
@@ -18,10 +18,9 @@ short_desc="GNOME file manager"
maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-or-later, LGPL-2.1-or-later"
homepage="https://wiki.gnome.org/Nautilus"
-#changelog="https://gitlab.gnome.org/GNOME/nautilus/-/raw/master/NEWS"
-changelog="https://gitlab.gnome.org/GNOME/nautilus/-/raw/gnome-45/NEWS"
+changelog="https://gitlab.gnome.org/GNOME/nautilus/-/raw/main/NEWS"
distfiles="${GNOME_SITE}/nautilus/${version%%.*}/nautilus-${version}.tar.xz"
-checksum=ba5d53df39a155562df971ef5e31e827074905d0c48eab1eb2421a10284b990d
+checksum=e6d75ed9f7aa68a00a2a559a0bf7010c6077e158d2d900fa365a8973f6ef11ce
# tests timeout:
# 11/11 test-nautilus-search-engine-tracker TIMEOUT 480.00s
make_check=ci-skip
next reply other threads:[~2024-03-21 14:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 14:44 fanyx [this message]
2024-04-18 4:14 ` [PR REVIEW] " oreo639
2024-04-18 8:27 ` [PR PATCH] [Updated] " fanyx
2024-04-18 8:27 ` fanyx
2024-04-18 8:34 ` fanyx
2024-04-18 8:35 ` oreo639
2024-04-18 8:36 ` oreo639
2024-04-18 8:36 ` fanyx
2024-04-18 8:37 ` fanyx
2024-04-18 8:38 ` oreo639
2024-04-18 8:38 ` oreo639
2024-04-18 8:42 ` oreo639
2024-04-18 8:42 ` oreo639
2024-04-18 8:43 ` fanyx
2024-04-18 8:44 ` fanyx
2024-04-18 8:46 ` oreo639
2024-04-18 8:55 ` fanyx
2024-04-18 8:57 ` oreo639
2024-04-18 9:01 ` oreo639
2024-04-19 8:53 ` [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-49427@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).