From: "André Batista" <nandre@riseup.net>
To: 73998@debbugs.gnu.org
Cc: "André Batista" <nandre@riseup.net>,
jonathan.brielmaier@web.de, mhw@netris.org
Subject: [bug#73998] [PATCH v2 0/2] Update torbrowser and mullvadbrowser to 14.0.3
Date: Sun, 1 Dec 2024 13:05:54 -0300 [thread overview]
Message-ID: <20241201160554.1800-1-nandre@riseup.net> (raw)
In-Reply-To: <20241029224533.2612-1-nandre@riseup.net>
This time around both browsers are on the same upstream ESR version.
Sent together because updating one would break the other as is.
Cheers!
André Batista (2):
gnu: torbrowser: Update to 14.0.3 [security-fixes].
gnu: mullvadbrowser: Update to 14.0.3 [security fixes].
gnu/local.mk | 1 +
.../patches/torbrowser-compare-paths.patch | 24 ++++++++++
gnu/packages/tor-browsers.scm | 44 +++++++++----------
3 files changed, 47 insertions(+), 22 deletions(-)
create mode 100644 gnu/packages/patches/torbrowser-compare-paths.patch
base-commit: 294386674c417355a24586fab5528c643d495b86
--
2.46.0
next prev parent reply other threads:[~2024-12-01 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 21:25 [bug#73998] [PATCH] gnu: torbrowser: Update to 14.0 André Batista
2024-10-29 22:45 ` [bug#73998] [PATCH 0/2] Update torbrowser and mullvadbrowser André Batista
2024-10-29 22:48 ` [bug#73998] [PATCH 1/2] gnu: torbrowser: Update to 14.0.1 [security-fixes] André Batista
2024-10-29 22:49 ` [bug#73998] [PATCH 2/2] gnu: mullvadbrowser: Update to 13.5.9 [security fixes] André Batista
2024-12-01 16:05 ` André Batista [this message]
2024-12-01 16:07 ` [bug#73998] [PATCH v2 1/2] gnu: torbrowser: Update to 14.0.3 [security-fixes] André Batista
2024-12-01 16:08 ` [bug#73998] [PATCH v2 2/2] gnu: mullvadbrowser: Update to 14.0.3 [security fixes] André Batista
2024-12-02 1:59 ` [bug#73998] [PATCH v2 0/2] Update torbrowser and mullvadbrowser to 14.0.3 Zheng Junjie
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=20241201160554.1800-1-nandre@riseup.net \
--to=nandre@riseup.net \
--cc=73998@debbugs.gnu.org \
--cc=jonathan.brielmaier@web.de \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.