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-June/016327.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-June/016327.html')
-rw-r--r-- | zarb-ml/mageia-dev/2012-June/016327.html | 125 |
1 files changed, 125 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016327.html b/zarb-ml/mageia-dev/2012-June/016327.html new file mode 100644 index 000000000..2d563d875 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016327.html @@ -0,0 +1,125 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Backports policy clarification (and discussion) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20clarification%20%28and%20discussion%29&In-Reply-To=%3C4FD39823.2000909%40eesti.ee%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016334.html"> + <LINK REL="Next" HREF="016329.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Backports policy clarification (and discussion)</H1> + <B>Sander Lepik</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20clarification%20%28and%20discussion%29&In-Reply-To=%3C4FD39823.2000909%40eesti.ee%3E" + TITLE="[Mageia-dev] Backports policy clarification (and discussion)">sander.lepik at eesti.ee + </A><BR> + <I>Sat Jun 9 20:38:27 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016334.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI>Next message: <A HREF="016329.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16327">[ date ]</a> + <a href="thread.html#16327">[ thread ]</a> + <a href="subject.html#16327">[ subject ]</a> + <a href="author.html#16327">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>09.06.2012 13:29, andre999 kirjutas: +><i> OK. To backport from Cauldron to mga1, we have to backport from Cauldron to mga2, +</I>><i> (bumping the revision in cauldron to ensure that is is higher), then backport from mga2 to +</I>><i> mga1, ensuring that the revision is lower in mga1 than in mga2. (e.g. revision x.1 in +</I>><i> cauldron, x.0.1 in mga2, x.0.0.1 in mga1) Pretty straight forward. +</I>><i> +</I>><i> - Cherry-picking refers to the users' option to install a backport, which has nothing to +</I>><i> do with the packaging itself. +</I>><i> +</I>><i> - Ensure that upgrades never fail : Properly packaged, there is no reason why any +</I>><i> available backports will not install properly, as long as the tools are appropriately +</I>><i> adjusted. Backports should install just as reliably as regular updates. +</I>><i> Of course, if a particular backport or update is not available, it won't install. +</I>><i> Packages requiring it should not install either, which may not always be the case now. +</I>><i> (This should be verified - for backports and updates.) +</I>I see backports as the way to get some new stuff from cauldron before cauldron is fully +stable. There is no point to backport from cauldron to n-2 (mga1 at the moment). If the user +wants so much newer stuff s/he better upgrade to latest stable. + +To not fail upgrade you must make sure that n-1 backports are not newer than n +n's updates. +You can't enable backports repo at upgrade time or it would upgrade all possible packages +from backports repo. I'm quite sure most users don't want that to happen! Cherry-picking for +me means that i can upgrade some packages from backports and then disable the repo. After +that i'm still able to upgrade to fully stable next release (w/o backports). + +-- +Sander + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016334.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI>Next message: <A HREF="016329.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16327">[ date ]</a> + <a href="thread.html#16327">[ thread ]</a> + <a href="subject.html#16327">[ subject ]</a> + <a href="author.html#16327">[ 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> |