Bug 1189845

Summary:	SeaMonkey: update to 2.53.9
Product:	[openSUSE] openSUSE Distribution	Reporter:	Tristan Miller <psychonaut>
Component:	Firefox	Assignee:	Mozilla Bugs <mozilla-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	Andreas.Stieger, maintenance, meissner, wolfgang.engel
Version:	Leap 15.3
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:	1185349, 1188100, 1188614
Bug Blocks:	1191022, 1192742, 1193668

Description Tristan Miller 2021-08-26 14:41:42 UTC

+++ This bug was initially created as a clone of Bug #1188614 +++

+++ This bug was initially created as a clone of Bug #1188100 +++

+++ This bug was initially created as a clone of Bug #1185349 +++

Please update the SeaMonkey packages in Leap 15.2 to the SeaMonkey 2.53.9 packages provided by the mozilla/seamonkey package on OBS: <https://build.opensuse.org/package/show/mozilla/seamonkey>  Please also include these packages in Leap 15.3, which is currently missing all SeaMonkey packages.

Leap 15.2 currently packages SeaMonkey 2.53.5.1, which uses the same backend as Firefox 60.8 and Thunderbird 60.0 and contains backports of important security fixes from Firefox 78.4 ESR.

The latest version of SeaMonkey, 2.53.9, released on 26 August 2021, is based on these same versions of Firefox and Thunderbird, but has backported all the important security fixes from Firefox 78.13 ESR.

Note that, per Bug 1185349 Comment 1, it may be necessary to first bootstrap a newer Rust repository for Leap, as SeaMonkey needs Rust >= 1.47 to build.

Comment 1 Marcus Meissner 2021-09-03 15:42:33 UTC

done

Comment 2 Tristan Miller 2021-09-09 12:01:06 UTC

(In reply to Marcus Meissner from comment #1)
> done

I still don't see SeaMonkey 2.53.9 in the Leap 15.2 and 15.3 download repositories.

Comment 3 Andreas Stieger 2021-11-16 11:52:28 UTC

let's use one bug

*** This bug has been marked as a duplicate of bug 1191022 ***