Opened 17 months ago

Closed 17 months ago

Last modified 17 months ago

#13202 closed enhancement (fixed)

seamonkey-2.53.1

Reported by: Bruce Dubbs Owned by: Douglas R. Reno
Priority: highest Milestone: 9.1
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

New minor version.

Change History (14)

comment:1 by ken@…, 17 months ago

Priority: normalhigh

Quoting https://www.seamonkey-project.org/releases/

If you are using NoScript you might encounter a certificate error when trying to download SeaMonkey from this site. NoScript tries to force an https connection for an http only site. It is not a NoScript problem but how the Mozilla server, from which downloads are delivered, is configured.

In this case please add download.cdn.mozilla.net to the NoScript "Never force secure (HTTPS) connections" options or turn off NoScript for this download only. The settings are located in the NoScript options under "Advanced->HTTPS"

And from the Release Notes at https://www.seamonkey-project.org/releases/seamonkey2.53.1/

The Mozilla backend code SeaMonkey is based on, now usually incorporates breaking changes in every release. This is especially true for the Mozilla Gecko add-ons code and the JavaScript interpreter. Consequently, some older extensions may no longer function properly. If you experience any problems please refer to the troubleshooting section first. Especially try to disable extensions first and check if this makes a difference.

Due to changes in the user profile, if you have set a master password, you will have to remove it before upgrading to SeaMonkey 2.53.1. After a successful upgrade, don't forget to manually remove the files key3.db and cert8.db in your profile afterwards, as they include credentials and passwords no longer protected by a master password. You can find the path to your profile folder entering the special about:support URL in a SeaMonkey browser window.

You can remove you master password by providing an empty password in the "Change Master Password" dialog. Do not use the "Reset Password" function. You will lose all stored passwords this way.

and from the same page

What's New in SeaMonkey 2.53.1

SeaMonkey 2.53.1 contains (among other changes) the following major changes relative to SeaMonkey 2.49.5:

    The Bookmarks Manager has switched its name to Library, and now also includes the History list. When invoking History, the Library will be shown with the History list selected. The extensive modifications were needed because of Mozilla Gecko platform API changes.
    Download Manager has been migrated to a new API. Although it looks pretty much the same as before, the search option is missing and some other minor details work differently. The previous downloads history is removed during the upgrade.
    Added Layout panel to CSS Grid tools.
    TLS 1.3 is the default version now.

SeaMonkey 2.53.1 uses the same backend as Firefox and contains the relevant Firefox 60.3 security fixes.

SeaMonkey 2.53.1 shares most parts of the mail and news code with Thunderbird. Please read the Thunderbird 60.0 release notes for specific changes and security fixes in this release.

Additional important security fixes up to Current Firefox 72 and a few enhancements have been backported. We will continue to enhance SeaMonkey security in subsequent 2.53 beta and release versions as fast as we are able to. 

Note that firefox-72 is no longer current, and neither is thunderbird-60. I'm inclined to mark this as high priority, but I doubt anyone will be motivated to put it into 9.1 before we release.

comment:2 by Douglas R. Reno, 17 months ago

Ken, do you know if this uses rust or not?

in reply to:  2 comment:3 by ken@…, 17 months ago

Replying to renodr:

Ken, do you know if this uses rust or not?

Sorry, no idea - I haven't even downloaded it (still banging my head against cmake|ninja).

comment:4 by Douglas R. Reno, 17 months ago

It looks like it does, but the question is - since it's got 20 Firefox Versions worth of security fixes in it (and the fixes for the 0days that Firefox has had) - should we update to it in 9.1?

comment:5 by Bruce Dubbs, 17 months ago

It's an end program. Nothing depends on it. Go ahead and update for 9.1.

comment:6 by Douglas R. Reno, 17 months ago

Milestone: 9.29.1
Owner: changed from blfs-book to Douglas R. Reno
Priority: highhighest
Status: newassigned

This seems to contain the 0day fixes for Firefox as well, so promoting to highest because of that.

comment:7 by Douglas R. Reno, 17 months ago

The download is extremely large (755 MB), and is 2.7GB when extracted. This seems to be because upstream didn't remove the .git files from their tarball before tarring it up. We can do it manually:

rm -rf .git mozilla/.git

Note that Gecko seems to be a separate checkout.

With that command, the source tree is down to 2.2GB.

I'm going to remove three options from the mozconfig which are no longer valid:

--enable-gio
--enable-safe-browsing
--enable-url-classifier

It also seems to use rust for Gecko (which makes sense), and our current version seems to pass configure OK. Now to see how the build runs...

comment:8 by Douglas R. Reno, 17 months ago

Actually, rust isn't searched for :) No dependency changes (other than removing libvpx) are required. The Development Libraries and Headers information is invalid now though.

comment:9 by Douglas R. Reno, 17 months ago

Never mind, I just found a reference to it in my log. :(

comment:10 by ken@…, 17 months ago

I spent some time looking for how it tests for the rust version, but I failed to find anything. This will be a pain to test when we next have to upgrade rust for firefox.

comment:11 by Douglas R. Reno, 17 months ago

I originally noticed it when it was running configure

It still uses "make -f client.mk", and then eventually kicks off mach to build a small portion of Firefox before continuing the rest of Seamonkey.

comment:12 by Douglas R. Reno, 17 months ago

Look in mozilla/build/moz.config/rust.configure

"rustc_min_version = Version('1.24.0')"

comment:13 by Douglas R. Reno, 17 months ago

Resolution: fixed
Status: assignedclosed

Fixed at r22772

in reply to:  12 comment:14 by ken@…, 17 months ago

Replying to renodr:

Look in mozilla/build/moz.config/rust.configure

"rustc_min_version = Version('1.24.0')"

Thanks. Turned out that what I'm really looking for is "maximum acceptable version" ;-)

I got your instructions working with 1.37.0, and now I can note that rustc-1.41.0 will not build it. Will review whenever we next have to update rustc.

Note: See TracTickets for help on using tickets.