diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-March/013553.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-March/013553.html | 139 |
1 files changed, 139 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-March/013553.html b/zarb-ml/mageia-dev/2012-March/013553.html new file mode 100644 index 000000000..98b23022d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-March/013553.html @@ -0,0 +1,139 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRFC%5D%20How%20to%20proceed%20with%20seamonkey/iceape%20for%0A%20security%20updates%20and%20freeze%20push&In-Reply-To=%3C4F70AB90.4030701%40arcor.de%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="013549.html"> + <LINK REL="Next" HREF="013554.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push</H1> + <B>Florian Hubold</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRFC%5D%20How%20to%20proceed%20with%20seamonkey/iceape%20for%0A%20security%20updates%20and%20freeze%20push&In-Reply-To=%3C4F70AB90.4030701%40arcor.de%3E" + TITLE="[Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push">doktor5000 at arcor.de + </A><BR> + <I>Mon Mar 26 19:46:56 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="013549.html">[Mageia-dev] [soft-commits] [3800] (plog_init) enable perl_checker to check callers +</A></li> + <LI>Next message: <A HREF="013554.html">[Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#13553">[ date ]</a> + <a href="thread.html#13553">[ thread ]</a> + <a href="subject.html#13553">[ subject ]</a> + <a href="author.html#13553">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi all, + +i've taken a look at iceape and locally updated it to 2.7.2¹ after talking with +maintainer +about it, with the intent to at least push this to Mageia 1, because since +initial import +it has not received any security updates (and there are countless security problem) +I've also completed the rebrand to iceape as far as i saw fit (change URL to +release +notes, applied some more debian rebranding patches, removed updater files and +updater menu item, and some more smaller fixes, current svn diff is attached) +and did some cleaning of old and unused stuff. + +¹: I've only updated it to 2.7.2 as 2.8 does require newer NSPR, and that's a no-go +for Mageia 1, which is my primary target. + + + +The biggest problem is: current maintainer does not have enough time to maintain +it properly, and i'm not planning on doing it either, as i don't use it or know +it well. + +There are at least 3 good options on how to proceed, apart from mga1 update: + + +1. +push latest version to cauldron, and hope somebody will maintain it afterwards +(this is the worst IMHO, as we'll probably face the same situation with a de-facto +umaintained package throughout Mageia 2 lifetime, which i want to avoid) + + +2. +drop iceape, package as seamonkey again and sync with Fedora +(this one would at least make maintenance easier, only need to follow Fedora) + + +3. +drop iceape completely +(actually this has the advantage that users can have official upstream binaries, +and take advantage of automatic updates. Current maintainer agrees with this, +as it's simply too fragile for him to maintain it easily. +If somebody is against this, please step up as maintainer or help the current +maintainer) + + +I'm currently in contact with some seamonkey developers, to maybe clear up +why/if the +rebrand is needed, if it's needed like it's currently done, and why Fedora can +simply +ship seamonkey without the need for a rebrand, but the dialog may take some +time, this +would be only relevant for option 2. + + +If nobody responds, i'll push my current work as security update for Mageia 1, +and drop iceape from cauldron so that we won't have an outdated package and +a potential security risk for Mageia 2. + + +Kind regards +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="013549.html">[Mageia-dev] [soft-commits] [3800] (plog_init) enable perl_checker to check callers +</A></li> + <LI>Next message: <A HREF="013554.html">[Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#13553">[ date ]</a> + <a href="thread.html#13553">[ thread ]</a> + <a href="subject.html#13553">[ subject ]</a> + <a href="author.html#13553">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |