From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [tracking] Drop mozjs78
Date: Wed, 11 Oct 2023 23:02:39 +0200 [thread overview]
Message-ID: <20231011210239.qfO9iyQWJz3nP0y2fygXXMDUeJ18mcncukHd3birTcU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39226@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
Closed issue by JamiKettunen on void-packages repository
https://github.com/void-linux/void-packages/issues/39226
Description:
As per https://endoflife.date/firefox 78 ESR has been EoL for nearly a year soon. According to a quick `grep -r` only the following consumers remain:
- [ ] [`0ad`](https://github.com/void-linux/void-packages/pull/46525)
- [x] [`cjs`](https://github.com/linuxmint/cjs/compare/5.6.1...1ef6934)
- [x] [`polkit`](https://github.com/void-linux/void-packages/pull/39203)
This would also contribute to #38229 ([`mozjs78`](https://github.com/void-linux/void-packages/blob/master/srcpkgs/mozjs78/template#L11) has `python-devel` in `makedepends`).
We should also keep in mind what happened with `mozjs60`: [5121c0f](https://github.com/void-linux/void-packages/commit/5121c0f) (`mozjs60: re-add as meta to allow people to upgrade their systems`) so the same thing doesn't happen again with the removal of `mozjs78`.
prev parent reply other threads:[~2023-10-11 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 10:24 [ISSUE] " JamiKettunen
2022-09-11 10:33 ` paper42
2022-09-11 15:02 ` CameronNemo
2022-09-11 15:03 ` CameronNemo
2022-09-11 15:05 ` CameronNemo
2022-09-23 16:40 ` [tracking] " CameronNemo
2022-09-24 23:03 ` classabbyamp
2023-05-09 11:27 ` JamiKettunen
2023-08-13 16:43 ` mhmdanas
2023-10-11 21:02 ` classabbyamp [this message]
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=20231011210239.qfO9iyQWJz3nP0y2fygXXMDUeJ18mcncukHd3birTcU@z \
--to=classabbyamp@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).