blob: 3ebedbd2c9020ea7315f0cfa45fb5d9b88b8c43d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
|
<!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=%3C201206081038.06735.stormi%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016441.html">
<LINK REL="Next" HREF="016267.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Backports policy clarification (and discussion)</H1>
<B>Samuel Verschelde</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=%3C201206081038.06735.stormi%40laposte.net%3E"
TITLE="[Mageia-dev] Backports policy clarification (and discussion)">stormi at laposte.net
</A><BR>
<I>Fri Jun 8 10:38:06 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016441.html">[Mageia-dev] Proposed Feature:Backports_update_applet
</A></li>
<LI>Next message: <A HREF="016267.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16265">[ date ]</a>
<a href="thread.html#16265">[ thread ]</a>
<a href="subject.html#16265">[ subject ]</a>
<a href="author.html#16265">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>I re-read the backports policy, and there's a part I think needs to be pointed
out before people start to backport packages.
"We need to ensure that upgrades never fail: cauldron must always have a
higher version/release than in stable releases."
This statement is true, but implies more than what it says. It means that we
can't backport a package for Mageia 1 with a higher version than what we have
in Mageia 2 release (and updates?) media. And this, until we are able to take
backports into account during upgrades.
Example :
- Mageia 2 has wesnoth 1.10.2 in core/release
- Mageia 1 can't get a higher version in its backports media
Do you all agree with my understanding of the policy ?
This is a serious limitation to our ability to backport to Mageia (n-1) and
even to our ability to provide security fixes to backports there (will not
prevent it, but will prevent to do it by a version upgrade, which is the
common way to fix that kind of issue in backports).
Maybe we shouldn't open backports for Mageia 1, and make sure upgrade to
Mageia 3 can take backports from Mageia 2 into account so that backports to
Mageia 2 are not stopped when Mageia 3 is released. Then we'll be safe.
Samuel
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016441.html">[Mageia-dev] Proposed Feature:Backports_update_applet
</A></li>
<LI>Next message: <A HREF="016267.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16265">[ date ]</a>
<a href="thread.html#16265">[ thread ]</a>
<a href="subject.html#16265">[ subject ]</a>
<a href="author.html#16265">[ 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>
|
