From: Byl3x <Byl3x@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] qutebrowser: update to 2.0.1
Date: Fri, 29 Jan 2021 11:46:28 +0100 [thread overview]
Message-ID: <20210129104628.Im4t9H4GcTX6BR69JiV605L8OX_4WRZmJBBSbvChxWY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28286@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]
There is an updated pull request by Byl3x against master on the void-packages repository
https://github.com/Byl3x/void-packages master
https://github.com/void-linux/void-packages/pull/28286
qutebrowser: update to 2.0.1
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH_LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/28286.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-28286.patch --]
[-- Type: text/x-diff, Size: 1999 bytes --]
From 09f1a250a8625a644b0a03456b611bc997905ec7 Mon Sep 17 00:00:00 2001
From: Byl3x <mbilek06@gmail.com>
Date: Thu, 28 Jan 2021 15:58:46 +0100
Subject: [PATCH] qutebrowser: update to 2.0.1
add checkdepends line
add python3-pytest
update checksum, bump version to 2.0.1
add do_check() patch
remove excess line
---
srcpkgs/qutebrowser/template | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/qutebrowser/template b/srcpkgs/qutebrowser/template
index 3ff0c7da5f0..35fdadee6b1 100644
--- a/srcpkgs/qutebrowser/template
+++ b/srcpkgs/qutebrowser/template
@@ -1,19 +1,20 @@
# Template file for 'qutebrowser'
pkgname=qutebrowser
-version=1.14.1
+version=2.0.1
revision=1
build_style=python3-module
hostmakedepends="python3-setuptools asciidoc"
depends="python3-PyQt5-quick python3-Jinja2 python3-Pygments python3-pyPEG2
python3-yaml python3-attrs python3-PyQt5-opengl python3-PyQt5-sql
qt5-plugin-sqlite python3-setuptools"
+checkdepends="$depends python3-pytest xvfb-run"
short_desc="Keyboard-focused browser with a minimal GUI"
maintainer="Érico Nogueira <ericonr@disroot.org>"
license="GPL-3.0-or-later"
homepage="https://qutebrowser.org/"
changelog="https://raw.githubusercontent.com/qutebrowser/qutebrowser/master/doc/changelog.asciidoc"
distfiles="https://github.com/qutebrowser/qutebrowser/releases/download/v${version}/qutebrowser-${version}.tar.gz"
-checksum=554c145ff64b1a92d4f53e3c624aaad51baafb7cb5b469bc815ae2e0e1958796
+checksum=aa988d61f1a396d7e7101054851291cf57e7cf19e7fc0eeffd30b672570ab242
nostrip=yes
build_options="webengine"
@@ -36,6 +37,12 @@ pre_build() {
a2x -f manpage doc/qutebrowser.1.asciidoc
}
+do_check() {
+ #testing with pytest would be nice, but requires unpackaged plugins:
+ #pytest-bdd, pytest-benchmark, pytest-instafail, pytest-mock, pytest-qt, pytest-rerunfailures
+ :
+}
+
post_install() {
vman doc/qutebrowser.1
vinstall misc/org.qutebrowser.qutebrowser.desktop 644 usr/share/applications
next prev parent reply other threads:[~2021-01-29 10:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 15:06 [PR PATCH] qutebrowser: update to 2.0.0 Byl3x
2021-01-28 15:13 ` ericonr
2021-01-28 15:16 ` [PR PATCH] [Updated] " Byl3x
2021-01-28 15:32 ` Byl3x
2021-01-28 15:36 ` ericonr
2021-01-28 15:39 ` [PR REVIEW] " ericonr
2021-01-28 15:51 ` [PR PATCH] [Updated] " Byl3x
2021-01-28 16:09 ` Byl3x
2021-01-28 16:14 ` Byl3x
2021-01-28 16:21 ` FollieHiyuki
2021-01-28 18:07 ` pbui
2021-01-28 22:29 ` Byl3x
2021-01-29 0:07 ` ericonr
2021-01-29 3:39 ` ahesford
2021-01-29 3:40 ` ahesford
2021-01-29 3:45 ` ericonr
2021-01-29 10:37 ` [PR PATCH] [Updated] " Byl3x
2021-01-29 10:46 ` Byl3x [this message]
2021-01-29 11:00 ` qutebrowser: update to 2.0.1 Byl3x
2021-01-29 12:17 ` ahesford
2021-01-29 18:57 ` Byl3x
2021-01-29 19:47 ` ahesford
2021-01-29 21:27 ` Byl3x
2021-01-29 22:46 ` paper42
2021-01-30 10:18 ` [PR PATCH] [Updated] " Byl3x
2021-01-30 12:25 ` [PR REVIEW] " ahesford
2021-01-30 12:28 ` [PR PATCH] [Updated] " Byl3x
2021-01-31 11:07 ` paper42
2021-01-31 13:11 ` ahesford
2021-02-01 2:55 ` [PR PATCH] [Closed]: " ahesford
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=20210129104628.Im4t9H4GcTX6BR69JiV605L8OX_4WRZmJBBSbvChxWY@z \
--to=byl3x@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).