[FFE] Update gjs to 1.78.0 and switch mozjs102 to mozjs115

Bug #2034276 reported by Jeremy Bícha
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gjs (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Explanation of FeatureFreeze exception
=======================================
gjs 1.78.0 is part of GNOME 45. gjs 1.78 switches from mozjs102 to mozjs115.

mozjs is the SpiderMonkey JavaScript engine from Firefox (ESR). The Firefox 102 ESR branch is no longer supported by Mozilla later this month; 115 is the new Firefox ESR series. We did not finish packaging mozjs115 before Mantic Feature Freeze.

This feature freeze request includes promoting mozjs115 from universe to main and demoting mozjs102 to universe. The only other user of mozjs* in Mantic is cjs, Cinnamon's fork of gjs. Cinnamon will not be ready to switch to mozjs115 in time for Ubuntu 23.10.

As a minor note, we will also need to add mozjs115 to the list of packages to build on i386.

Upstream changes
================
https://gitlab.gnome.org/GNOME/gjs/-/blob/1.78.0/NEWS

Changelog entries since current mantic version 1.76.2-4:
========================================================
gjs (1.78.0-0ubuntu1) mantic; urgency=medium

  * New upstream release
  * Switch from mozjs102 to 115 (LP: #2034276)
  * Drop all patches: applied in new release
  * debian/libgjs0g.symbols: Add new symbol

 -- Jeremy Bícha Tue, 26 Sep 2023 13:48:35 -0400

Testing Done
============
Successful builds for 1.77.90:
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+packages

autopkgtest:
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ubuntu-desktop-ppa/mantic/amd64/g/gjs/20230905_185208_5e448@/log.gz

I have successfully completed the manual test case at
https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs

Jeremy Bícha (jbicha)
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote :

From a maintenance perspective, I think there's not much argument for bumping to mozjs115 despite mozjs102 being EOL, because you say Cinnamon isn't ready to switch and that means the Security Team will still be supporting both (one under ESM). If anything, this appears to mean a net increase in security maintenance work since there will now be two source packages. And we still have 3 months beyond October of security support for mozjs102 in main, via lunar.

In terms of tracking GNOME 45 upstream, this sounds sensible. When is the final gjs 1.78 due out?

Changed in gjs (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Sorry for the delay in responding.

gjs 1.78.0 was released on September 16 which was exactly on schedule for inclusion in GNOME 45.0 released September 20.

gjs follows the GNOME schedule.

I'm going to upload gjs 1.78 now since it will get held in the mantic unapproved queue now that we are past Ubuntu 23.10 Beta.

Changed in gjs (Ubuntu):
status: Incomplete → New
Revision history for this message
Jeremy Bícha (jbicha) wrote :

I have been running gjs 1.77.90 locally on my primary mantic computer since early September and I haven't noticed any issues because of it.

Honestly, I don't expect the Ubuntu Security Team to provide any further support for mozjs102 after we upload the final mozjs102 update.

Jeremy Bícha (jbicha)
summary: - [FFE] Update gjs to 1.77.90 and switch mozjs102 to mozjs115
+ [FFE] Update gjs to 1.78.0 and switch mozjs102 to mozjs115
description: updated
description: updated
Jeremy Bícha (jbicha)
tags: added: update-excuse
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gjs - 1.78.0-0ubuntu1

---------------
gjs (1.78.0-0ubuntu1) mantic; urgency=medium

  * New upstream release
  * Switch from mozjs102 to 115 (LP: #2034276)
  * Drop all patches: applied in new release
  * debian/libgjs0g.symbols: Add new symbol

 -- Jeremy Bícha <email address hidden> Tue, 26 Sep 2023 13:21:46 -0400

Changed in gjs (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.