diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016896.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016896.html | 193 |
1 files changed, 193 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016896.html b/zarb-ml/mageia-dev/2012-June/016896.html new file mode 100644 index 000000000..37be8879a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016896.html @@ -0,0 +1,193 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Backports Summary + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3Ce50cea20a7d0db27ecd3ed47a498286b.squirrel%40mail.rmail.be%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016883.html"> + <LINK REL="Next" HREF="016888.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Backports Summary</H1> + <B>AL13N</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3Ce50cea20a7d0db27ecd3ed47a498286b.squirrel%40mail.rmail.be%3E" + TITLE="[Mageia-dev] Backports Summary">alien at rmail.be + </A><BR> + <I>Wed Jun 27 12:36:25 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016883.html">[Mageia-dev] Backports Summary +</A></li> + <LI>Next message: <A HREF="016888.html">[Mageia-dev] Backports Summary +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16896">[ date ]</a> + <a href="thread.html#16896">[ thread ]</a> + <a href="subject.html#16896">[ subject ]</a> + <a href="author.html#16896">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>><i> Thomas Backlund a écrit : +</I>>><i> Sander Lepik skrev 26.6.2012 23:15: +</I>>>><i> 26.06.2012 22:25, Thomas Backlund kirjutas: +</I>>>>><i> * backports is supported as long as the rest of the release +</I>>>>><i> +</I>>>>><i> +</I>>>>><i> Comments? Questions ? +</I>>>><i> I think we should change the wording from "supported" to "tested". +</I>>>><i> Currently we can +</I>>>><i> "support" backport with a newer version of the backport. But i don't +</I>>>><i> think it's a wise move +</I>>>><i> to mark backports repo as an updates repo. So i don't see how we can +</I>>>><i> _support_ backports. +</I>>>><i> And QA has no time to deal with updates for backports (i mean to +</I>>>><i> search for security holes +</I>>>><i> in backports). But this can be discussed tomorrow. +</I>>><i> +</I>>><i> Well, +</I>>><i> +</I>>><i> It's the backporters job to make sure its fixed for security issues as +</I>>><i> stated by: +</I>>><i> +</I>>><i> * if you backport anything, (regardless if you are the real +</I>>><i> maintainer or not) you accept the responsibility of +</I>>><i> handling the bugreports against the backport and make sure +</I>>><i> it gets patched (or upgraded) to get security fixes. +</I>>><i> +</I>>><i> +</I>>><i> It's not supposed to be flagged as an update repo as that would make +</I>>><i> it upgrade all packages it find in the system with matching backports +</I>>><i> packages. +</I>>><i> +</I>>><i> So we need to either create a "backports update applet" or extend +</I>>><i> current update applet. +</I>><i> +</I>><i> I would favour extending the current update tools, and then flagging +</I>><i> backport repos as updates, so that newer backports would be treated as +</I>><i> updates to already installed backports at the same time as other updates. +</I> +actually, since the applet will have to works like this: (cf bug 2317) + +1. mark media to get updates from +2. mark seachmedia to get it's dependencies from (release) +3. do updates + +extending this to backports does the following: + +1. mark update media + backport media +2. mark search media to get it's dependencies from (release) +3. do updates + +With regard to dependencies, this means we'd be including backports too, +which means we could use my patch for bug 2317 anyway. + +If you don't want this, you'd have to do the updates and backports +separately. which is again quite some complexity. + +(besides, if we do have strict requires, to make cherry-picking work, the +problems we'd get from using the patch would go away anyway. + +>><i> (or "worst case" until we get it automated tell the user of backported +</I>>><i> packages to make sure they check if a new/fixed rpm is available in +</I>>><i> backports) +</I>>><i> +</I>>><i> And there will still be some advisory notifying people of new backports, +</I>>><i> just like we do for security and bugfix updates now. +</I>><i> +</I>><i> +1 +</I>>><i> +</I>>><i> -- +</I>>><i> Thomas +</I>>><i> +</I>><i> +</I>><i> +</I>><i> -- +</I>><i> André +</I>><i> +</I>><i> +</I> +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016883.html">[Mageia-dev] Backports Summary +</A></li> + <LI>Next message: <A HREF="016888.html">[Mageia-dev] Backports Summary +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16896">[ date ]</a> + <a href="thread.html#16896">[ thread ]</a> + <a href="subject.html#16896">[ subject ]</a> + <a href="author.html#16896">[ 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> |