Bug 24300 - Rename iceape back to seamonkey
Summary: Rename iceape back to seamonkey
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker normal
Target Milestone: ---
Assignee: Christiaan Welvaart
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-02 20:18 CET by Morgan Leijström
Modified: 2020-02-08 19:55 CET (History)
3 users (show)

See Also:
Source RPM: iceape-2.49.4-1.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Morgan Leijström 2019-02-02 20:18:43 CET
Seamonkey is by us called iceape.
But with Debian dropping the alternate naming we really should rename it back to seamonkey.
Stig-Ørjan Smelror 2019-02-02 20:45:50 CET

Assignee: bugsquad => cjw
CC: (none) => smelror

Comment 2 David Walser 2019-02-02 23:22:57 CET
Yes, we're aware of the historical issues, but Debian was the one that spearheaded the renaming of all of the Mozilla packages, and they've more recently determined that it's no longer an issue and renamed back to their upstream names.  We should follow suit.
Comment 3 Lewis Smith 2019-02-03 22:17:33 CET
This bug was started because of complaints about Kompozer being being beyond hope (and to drop), and what to replace it with for HTML editing. Whence the suggestion for Iceape=SeaMonkey for this task. Except that I thought SeaMonkey was a suite including e-mail as well, while Iceape (which I use routinely) was just the browser componenet of that suite.
I also want to remind that we offer the long-standing Bluefish HTML editor, often installed out-of-the box. David suggested yet another one. That is nothing to do with package names; sorry!

CC: (none) => lewyssmith

Comment 4 Lewis Smith 2019-02-05 11:07:08 CET
I happen to have a bug 24021 open on Iceape, which might become relevant to this one.
Comment 5 Christiaan Welvaart 2019-04-29 19:54:13 CEST
I agree, let's do what debian did and remove iceape from the distro. I don't have time to port all firefox security updates and I don't expect anyone else to do this either (AFAICT upstream does not currently provide such security updates).
Comment 6 Keith Bowes 2020-02-08 03:37:54 CET
I've wondered for a long time why Mageia just gets the SeaMonkey source and then applies patches to rebrand it, instead of using the source as-is.  I personally use upstream SeaMonkey, because I got tired of all the warnings about using an outdated version when using Mageia's Iceape.

Anyway, the future of SeaMonkey is quite uncertain.  As of writing, the current version is 2.49.5 (based on Firefox 52), and they're working on SeaMonkey 2.53 (based on Firefox 56) and SeaMonkey 2.57 (based on Firefox 60), but due to Firefox constantly removing APIs and the small base of SeaMonkey developers (most of the developers have left), it takes a while to catch up and it's widely assumed (and almost admitted by the SeaMonkey developers) that 2.57.x will be the final version (or at the very best that post-2.57.x versions will be based on their fork of the Firefox 60 source code). <http://www.seamonkey-project.org/news#2019-09-04>

CC: (none) => zooplah

Comment 7 Keith Bowes 2020-02-08 03:42:35 CET
(In reply to Lewis Smith from comment #3)
> I thought
> SeaMonkey was a suite including e-mail as well, while Iceape (which I use
> routinely) was just the browser componenet of that suite.
Actually, the suite is called SeaMonkey and the browser component is called Navigator.  Iceape is just Debian's (dropped) rebranding of SeaMonkey, like Iceweasel was their rebranding on Firefox, etc.  (Iceape's browser component is still called Navigator.)
Comment 8 David Walser 2020-02-08 19:55:48 CET
Yes, we should not keep a browser that isn't being maintained upstream and kept up to date with security fixes.  Even our package maintainer said to drop it.  I think the correct technical solution would be to have the firefox package in Cauldron obsolete iceape.

Priority: Normal => release_blocker


Note You need to log in before you can comment on or make changes to this bug.