From: "André Batista" <nandre@riseup.net>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: 68676@debbugs.gnu.org
Subject: [bug#68676] [PATCH v2] gnu: torbrowser: Update to 13.0.9.
Date: Tue, 30 Jan 2024 20:03:53 -0300 [thread overview]
Message-ID: <ZbmAWTUvtLHa_LKm@andel> (raw)
In-Reply-To: <79918fcadc69cb21c91826aa7a815153807def18.1706142731.git.clement@lassieur.org>
Hi Clément,
qui 25 jan 2024 às 01:32:16 (1706157136), clement@lassieur.org enviou:
> * gnu/packages/gnuzilla.scm: Stop exporting ‘all-mozilla-locales’.
> * gnu/packages/tor.scm (mozilla-locale): New procedure copied from
> gnuzilla.scm.
> (mozilla-locales): New macro adapted from gnuzilla.scm.
> (%torbrowser-locales): Add sha256 and changeset for each locale and update
> them all.
> (%moz-build-date): Update to 20240123154553.
Just to be clear: we are not trying to mimic upstream here, right?
Upstream buildID is '20240115174022'. I have no web developing experience
so I'm not sure if this could be used to make guix users apart. From a
quick web search, I've found this two articles:
https://developer.mozilla.org/en-US/docs/Web/API/Navigator/buildID
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/Runtime/getBrowserInfo
Runing the command on the first one in the browser console I get back the
fixed mozilla buildID, not the one that is defined.
The second one appears to be only available to web extensions. At least I
could not run it on the console. I don't know if there are any tricks
that I may be missing to import those APIs and make them available. If
only available to installed extensions, it would be less of a concern to
me.
Other than that, everything looks good to me. Nice job on picking those
locale commit changes, I had missed them entirely.
Cheers,
next prev parent reply other threads:[~2024-01-30 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 16:16 [bug#68676] [PATCH] gnu: torbrowser: Update to 13.0.9 Clément Lassieur
2024-01-23 20:05 ` Clément Lassieur
2024-01-25 0:32 ` [bug#68676] [PATCH v2] " Clément Lassieur
2024-01-26 0:21 ` bug#68676: " Clément Lassieur
2024-01-30 23:03 ` André Batista [this message]
2024-01-31 2:09 ` [bug#68676] " Clément Lassieur
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZbmAWTUvtLHa_LKm@andel \
--to=nandre@riseup.net \
--cc=68676@debbugs.gnu.org \
--cc=clement@lassieur.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).