diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2012-April/013906.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2012-April/013906.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-April/013906.html | 138 |
1 files changed, 138 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-April/013906.html b/zarb-ml/mageia-dev/2012-April/013906.html new file mode 100644 index 000000000..2cb4333a2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-April/013906.html @@ -0,0 +1,138 @@ +<!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%09security%20updates%20and%20freeze%20push&In-Reply-To=%3C201204050811.21228.alien%40rmail.be%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="013891.html"> + <LINK REL="Next" HREF="013919.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push</H1> + <B>Maarten Vanraes</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%09security%20updates%20and%20freeze%20push&In-Reply-To=%3C201204050811.21228.alien%40rmail.be%3E" + TITLE="[Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push">alien at rmail.be + </A><BR> + <I>Thu Apr 5 08:11:21 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="013891.html">[Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push +</A></li> + <LI>Next message: <A HREF="013919.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#13906">[ date ]</a> + <a href="thread.html#13906">[ thread ]</a> + <a href="subject.html#13906">[ subject ]</a> + <a href="author.html#13906">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op woensdag 04 april 2012 22:59:30 schreef Florian Hubold: +><i> Am 26.03.2012 19:46, schrieb Florian Hubold: +</I>><i> > Hi all, +</I>><i> > +</I>><i> > i've taken a look at iceape and locally updated it to 2.7.2¹ after +</I>><i> > talking with maintainer +</I>><i> > about it, with the intent to at least push this to Mageia 1, because +</I>><i> > since initial import +</I>><i> > it has not received any security updates (and there are countless +</I>><i> > security problem) I've also completed the rebrand to iceape as far as i +</I>><i> > saw fit (change URL to release +</I>><i> > notes, applied some more debian rebranding patches, removed updater files +</I>><i> > and updater menu item, and some more smaller fixes, current svn diff is +</I>><i> > attached) and did some cleaning of old and unused stuff. +</I>><i> > +</I>><i> > ¹: I've only updated it to 2.7.2 as 2.8 does require newer NSPR, and +</I>><i> > that's a no-go for Mageia 1, which is my primary target. +</I>><i> > +</I>><i> > +</I>><i> > +</I>><i> > The biggest problem is: current maintainer does not have enough time to +</I>><i> > maintain it properly, and i'm not planning on doing it either, as i +</I>><i> > don't use it or know it well. +</I>><i> > +</I>><i> > There are at least 3 good options on how to proceed, apart from mga1 +</I>><i> > update: +</I>><i> > +</I>><i> > +</I>><i> > 1. +</I>><i> > push latest version to cauldron, and hope somebody will maintain it +</I>><i> > afterwards (this is the worst IMHO, as we'll probably face the same +</I>><i> > situation with a de-facto umaintained package throughout Mageia 2 +</I>><i> > lifetime, which i want to avoid) +</I>><i> > +</I>><i> > +</I>><i> > 2. +</I>><i> > drop iceape, package as seamonkey again and sync with Fedora +</I>><i> > (this one would at least make maintenance easier, only need to follow +</I>><i> > Fedora) +</I>><i> > +</I>><i> > +</I>><i> > 3. +</I>><i> > drop iceape completely +</I>><i> > (actually this has the advantage that users can have official upstream +</I>><i> > binaries, and take advantage of automatic updates. Current maintainer +</I>><i> > agrees with this, as it's simply too fragile for him to maintain it +</I>><i> > easily. +</I>><i> > If somebody is against this, please step up as maintainer or help the +</I>><i> > current maintainer) +</I>><i> > +</I>><i> > +</I>><i> > I'm currently in contact with some seamonkey developers, to maybe clear +</I>><i> > up why/if the +</I>><i> > rebrand is needed, if it's needed like it's currently done, and why +</I>><i> > Fedora can simply +</I>><i> > ship seamonkey without the need for a rebrand, but the dialog may take +</I>><i> > some time, this +</I>><i> > would be only relevant for option 2. +</I>><i> > +</I>><i> > +</I>><i> > If nobody responds, i'll push my current work as security update for +</I>><i> > Mageia 1, and drop iceape from cauldron so that we won't have an +</I>><i> > outdated package and a potential security risk for Mageia 2. +</I>><i> > +</I>><i> > +</I>><i> > Kind regards +</I>><i> +</I>><i> As there was no real objection, and no other comments +</I>><i> or votes for iceape, i've dropped it from cauldron. FWIW i'm quite +</I>><i> unhappy with this. Related, i've also not got any reply yet to my +</I>><i> aforementioned inquiry about mozilla branding permissions. +</I> +About the mozilla branding... + +Perhaps this should be a meeting point for packaging/council meeting... + +ie: someone assigned to this point so it's not forgotten. +</PRE> + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="013891.html">[Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push +</A></li> + <LI>Next message: <A HREF="013919.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#13906">[ date ]</a> + <a href="thread.html#13906">[ thread ]</a> + <a href="subject.html#13906">[ subject ]</a> + <a href="author.html#13906">[ 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> |