diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016880.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016880.html | 156 |
1 files changed, 156 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016880.html b/zarb-ml/mageia-dev/2012-June/016880.html new file mode 100644 index 000000000..ffb5f6827 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016880.html @@ -0,0 +1,156 @@ +<!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=%3C4FEAC2F7.4060808%40mageia.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016900.html"> + <LINK REL="Next" HREF="016883.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Backports Summary</H1> + <B>Thomas Backlund</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C4FEAC2F7.4060808%40mageia.org%3E" + TITLE="[Mageia-dev] Backports Summary">tmb at mageia.org + </A><BR> + <I>Wed Jun 27 10:23:19 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016900.html">[Mageia-dev] Backports Summary +</A></li> + <LI>Next message: <A HREF="016883.html">[Mageia-dev] Backports Summary +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16880">[ date ]</a> + <a href="thread.html#16880">[ thread ]</a> + <a href="subject.html#16880">[ subject ]</a> + <a href="author.html#16880">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Sander Lepik skrev 26.6.2012 23:15: +><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". Currently we can +</I>><i> "support" backport with a newer version of the backport. But i don't think it's a wise move +</I>><i> to mark backports repo as an updates repo. So i don't see how we can _support_ backports. +</I>><i> And QA has no time to deal with updates for backports (i mean to search for security holes +</I>><i> in backports). But this can be discussed tomorrow. +</I> +Well, + +It's the backporters job to make sure its fixed for security issues as +stated by: + +* if you backport anything, (regardless if you are the real + maintainer or not) you accept the responsibility of + handling the bugreports against the backport and make sure + it gets patched (or upgraded) to get security fixes. + + +It's not supposed to be flagged as an update repo as that would make it +upgrade all packages it find in the system with matching backports packages. + +So we need to either create a "backports update applet" or extend +current update applet. + +(or "worst case" until we get it automated tell the user of backported + packages to make sure they check if a new/fixed rpm is available in + backports) + +And there will still be some advisory notifying people of new backports, +just like we do for security and bugfix updates now. + +-- +Thomas +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016900.html">[Mageia-dev] Backports Summary +</A></li> + <LI>Next message: <A HREF="016883.html">[Mageia-dev] Backports Summary +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16880">[ date ]</a> + <a href="thread.html#16880">[ thread ]</a> + <a href="subject.html#16880">[ subject ]</a> + <a href="author.html#16880">[ 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> |