Github messages for voidlinux
 help / color / mirror / Atom feed
From: xuoe <xuoe@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] nicotine+: update to 3.2.0.
Date: Tue, 18 Jan 2022 23:36:18 +0100	[thread overview]
Message-ID: <20220118223618.uKJx3DOvNOeYguiAam7lI_AE4Q5eNEyxjrfDvMAmoSg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35085@inbox.vuxu.org>

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

There is an updated pull request by xuoe against master on the void-packages repository

https://github.com/xuoe/void-packages master
https://github.com/void-linux/void-packages/pull/35085

nicotine+: update to 3.2.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

A patch file from https://github.com/void-linux/void-packages/pull/35085.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-35085.patch --]
[-- Type: text/x-diff, Size: 1557 bytes --]

From 479cc2ed173f77dd348a3add8c2250ef9f36d16e Mon Sep 17 00:00:00 2001
From: Alex Diaconu <xuoe@pm.me>
Date: Sun, 16 Jan 2022 23:16:26 +0200
Subject: [PATCH] nicotine+: update to 3.2.0.

python3-setuptools is now a build dependency and xvfb is required to
test the package.

Also slightly adjusted the package description to match the official
one.
---
 srcpkgs/nicotine+/template | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/nicotine+/template b/srcpkgs/nicotine+/template
index 039e1d7ffc1e..2bcd08383e4e 100644
--- a/srcpkgs/nicotine+/template
+++ b/srcpkgs/nicotine+/template
@@ -1,15 +1,16 @@
 # Template file for 'nicotine+'
 pkgname=nicotine+
-version=3.1.1
+version=3.2.0
 revision=1
 wrksrc="nicotine-plus-${version}"
 build_style=python3-module
-hostmakedepends="python3 gettext"
+hostmakedepends="python3 python3-setuptools gettext"
 depends="gspell gtk+3 python3-gobject"
-short_desc="Graphical client for the Soulseek file sharing network"
+checkdepends="$depends python3-pytest python3-pytest-xvfb"
+short_desc="Graphical client for the Soulseek peer-to-peer network"
 maintainer="doggone <doggone@airmail.cc>"
 license="GPL-3.0-or-later"
 homepage="https://nicotine-plus.org"
 changelog="https://raw.githubusercontent.com/nicotine-plus/nicotine-plus/master/NEWS.md"
 distfiles="https://github.com/Nicotine-Plus/nicotine-plus/archive/${version}.tar.gz"
-checksum=d02f374eaf4cf8cebb2b4068ed5dd36f5774d5ea72b61715ff39bfd6936252d0
+checksum=ec3a90ca9a791e7724bbb6504defe0b4104a21dd7da3f20fdc7a50519f90228e

  reply	other threads:[~2022-01-18 22:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-16 21:28 [PR PATCH] " xuoe
2022-01-18 22:36 ` xuoe [this message]
2022-01-19  9:45 ` xuoe
2022-01-19  9:46 ` xuoe
2022-01-19 17:14 ` xuoe
2022-01-19 21:42 ` [PR PATCH] [Updated] " xuoe
2022-01-19 21:48 ` [PR PATCH] [Merged]: " leahneukirchen

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=20220118223618.uKJx3DOvNOeYguiAam7lI_AE4Q5eNEyxjrfDvMAmoSg@z \
    --to=xuoe@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).