From: someone13574 <someone13574@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] nautilus: update to 44.0.
Date: Thu, 23 Mar 2023 03:06:01 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42939@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
There is a new pull request by someone13574 against master on the void-packages repository
https://github.com/someone13574/void-packages nautilus-44.0
https://github.com/void-linux/void-packages/pull/42939
nautilus: update to 44.0.
#### 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-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-*
- armv7l-*
- armv6l-*
- x86_64-musl
- i686
A patch file from https://github.com/void-linux/void-packages/pull/42939.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-nautilus-44.0-42939.patch --]
[-- Type: text/x-diff, Size: 1277 bytes --]
From c3d8548de6c8706383b183d37ef9b1c94e72ba8a Mon Sep 17 00:00:00 2001
From: Owen Law <owenlaw222@gmail.com>
Date: Wed, 22 Mar 2023 22:03:28 -0400
Subject: [PATCH] nautilus: update to 44.0.
---
srcpkgs/nautilus/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/nautilus/template b/srcpkgs/nautilus/template
index bf934b66f63c..d8d242e0235b 100644
--- a/srcpkgs/nautilus/template
+++ b/srcpkgs/nautilus/template
@@ -1,6 +1,6 @@
# Template file for 'nautilus'
pkgname=nautilus
-version=43.2
+version=44.0
revision=1
build_style=meson
build_helper="gir"
@@ -18,9 +18,9 @@ short_desc="GNOME file manager"
maintainer="Michal Vasilek <michal@vasilek.cz>"
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/gnome-43/NEWS"
+changelog="https://gitlab.gnome.org/GNOME/nautilus/-/raw/44.0/NEWS"
distfiles="${GNOME_SITE}/nautilus/${version%%.*}/nautilus-${version}.tar.xz"
-checksum=a86a9aa7a455511b029ce49a1d8b4659c3c355b5d81d7360bb4d0de637afede0
+checksum=57b99ebb8e2b9c1512d381e53096188c087b33410d6c52d87a27bd60ee76ac7f
# tests timeout:
# 11/11 test-nautilus-search-engine-tracker TIMEOUT 480.00s
make_check=extended
next reply other threads:[~2023-03-23 2:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 2:06 someone13574 [this message]
2023-03-23 8:39 ` [PR REVIEW] " paper42
2023-03-23 17:32 ` paper42
2023-03-23 19:08 ` [PR PATCH] [Updated] " someone13574
2023-03-23 19:09 ` someone13574
2023-03-23 19:37 ` someone13574
2023-03-23 19:52 ` [PR REVIEW] " someone13574
2023-03-23 19:53 ` someone13574
2023-03-23 19:54 ` someone13574
2023-03-23 19:59 ` [PR PATCH] [Updated] " someone13574
2023-03-23 20:34 ` [PR REVIEW] " paper42
2023-03-23 21:50 ` [PR PATCH] [Updated] " someone13574
2023-03-23 22:23 ` [PR PATCH] [Merged]: " paper42
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-42939@inbox.vuxu.org \
--to=someone13574@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).