From: daniel-eys <daniel-eys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] torbrowser-launcher: update to 0.3.6.
Date: Sun, 18 Dec 2022 12:43:53 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41161@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
There is a new pull request by daniel-eys against master on the void-packages repository
https://github.com/daniel-eys/void-packages torbrowser-launcher
https://github.com/void-linux/void-packages/pull/41161
torbrowser-launcher: update to 0.3.6.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- 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/41161.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-torbrowser-launcher-41161.patch --]
[-- Type: text/x-diff, Size: 3234 bytes --]
From cb6812c77d2eda8e52f93b0ae70fc9aad60a002a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Ey=C3=9Fer?= <daniel.eysser@gmail.com>
Date: Sun, 18 Dec 2022 12:30:55 +0100
Subject: [PATCH] torbrowser-launcher: update to 0.3.6.
---
.../torbrowser-launcher/patches/python310.patch | 12 ------------
srcpkgs/torbrowser-launcher/patches/wayland.diff | 14 --------------
srcpkgs/torbrowser-launcher/template | 6 +++---
3 files changed, 3 insertions(+), 29 deletions(-)
delete mode 100644 srcpkgs/torbrowser-launcher/patches/python310.patch
delete mode 100644 srcpkgs/torbrowser-launcher/patches/wayland.diff
diff --git a/srcpkgs/torbrowser-launcher/patches/python310.patch b/srcpkgs/torbrowser-launcher/patches/python310.patch
deleted file mode 100644
index 2c0485dc12d7..000000000000
--- a/srcpkgs/torbrowser-launcher/patches/python310.patch
+++ /dev/null
@@ -1,12 +0,0 @@
---- a/torbrowser_launcher/__init__.py
-+++ b/torbrowser_launcher/__init__.py
-@@ -90,8 +90,8 @@ def main():
- desktop = app.desktop()
- window_size = gui.size()
- gui.move(
-- (desktop.width() - window_size.width()) / 2,
-- (desktop.height() - window_size.height()) / 2,
-+ (desktop.width() - window_size.width()) // 2,
-+ (desktop.height() - window_size.height()) // 2,
- )
- gui.show()
diff --git a/srcpkgs/torbrowser-launcher/patches/wayland.diff b/srcpkgs/torbrowser-launcher/patches/wayland.diff
deleted file mode 100644
index 3553d5d53017..000000000000
--- a/srcpkgs/torbrowser-launcher/patches/wayland.diff
+++ /dev/null
@@ -1,14 +0,0 @@
-diff --git a/apparmor/torbrowser.Browser.firefox b/apparmor/torbrowser.Browser.firefox
-index 6882f9d..365b073 100644
---- a/apparmor/torbrowser.Browser.firefox
-+++ b/apparmor/torbrowser.Browser.firefox
-@@ -115,6 +115,9 @@ profile torbrowser_firefox @{torbrowser_firefox_executable} {
- owner /{dev,run}/shm/org.chromium.* rw,
- owner /dev/shm/org.mozilla.ipc.[0-9]*.[0-9]* rw, # for Chromium IPC
-
-+ # Required for Wayland display protocol support
-+ owner /dev/shm/wayland.mozilla.ipc.[0-9]* rw,
-+
- # Deny access to DRM nodes, that's granted by the X abstraction, which is
- # sourced by the gnome abstraction, that we include.
- deny /dev/dri/** rwklx,
diff --git a/srcpkgs/torbrowser-launcher/template b/srcpkgs/torbrowser-launcher/template
index d2b44ddd79bf..c9b09fe9f41b 100644
--- a/srcpkgs/torbrowser-launcher/template
+++ b/srcpkgs/torbrowser-launcher/template
@@ -1,7 +1,7 @@
# Template file for 'torbrowser-launcher'
pkgname=torbrowser-launcher
-version=0.3.5
-revision=5
+version=0.3.6
+revision=1
archs="i686 x86_64" # limited by Tor Browser itself
build_style=python3-module
hostmakedepends="gettext python3-distro python3-setuptools"
@@ -15,7 +15,7 @@ license="MIT"
homepage="https://github.com/micahflee/torbrowser-launcher"
changelog="https://raw.githubusercontent.com/micahflee/torbrowser-launcher/master/CHANGELOG.md"
distfiles="https://github.com/micahflee/torbrowser-launcher/archive/v${version}.tar.gz"
-checksum=623cd77c6095711f371fee5b5cc521ecd8dd89d964b75fad6449633d10925089
+checksum=39db8bd936502bc6d9adf3a628fba13a728c7b1aa2b5bac148454c8718863654
post_install() {
vlicense LICENSE
next reply other threads:[~2022-12-18 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 11:43 daniel-eys [this message]
2022-12-18 13:38 ` [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-41161@inbox.vuxu.org \
--to=daniel-eys@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).