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
|
<!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=%3C201206081956.52219.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="016294.html">
<LINK REL="Next" HREF="016302.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=%3C201206081956.52219.stormi%40laposte.net%3E"
TITLE="[Mageia-dev] Backports policy clarification (and discussion)">stormi at laposte.net
</A><BR>
<I>Fri Jun 8 19:56:52 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016294.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI>Next message: <A HREF="016302.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16295">[ date ]</a>
<a href="thread.html#16295">[ thread ]</a>
<a href="subject.html#16295">[ subject ]</a>
<a href="author.html#16295">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le vendredi 8 juin 2012 19:35:28, Sander Lepik a écrit :
><i> I don't think that we need to support backports that much. It should be
</I>><i> clear that backports might not get all security updates. We should
</I>><i> guarantee that it's possible to upgrade to next stable release and that's
</I>><i> about it. We really don't have resources for more.
</I>
That backports are supported is the key point of the policy, which was
discussed and validated months ago. It's not a "let's throw in random
packages" media, it's part of the distribution. Resources will limit the
number of different packages we are able to backport AND maintain, not the
quality of our support.
So I'd like us to discuss the way to attain this objective rather than try to
force users needs to fit with what's simpler for us. Solutions probably revolve
around taking backports into account during upgrade, which is doable. Hard,
maybe, but doable:
- online upgrade can use backports media for packages not coming from release.
If we don't know where a package comes from we can start storing that
information somewhere, or guess (any package with higher version installed
than that in target distro's updates should be updated using backports media).
- DVD could detect packages which can't be updated (in fact, it should do it
already since there are already, DVDs having limited space), and warn about
them. DVD upgrade should also, if possible, detect dependency problems
*before* actually upgrading. Then if network is available ask the user if they
want to use online media for safer upgrade.
Samuel
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016294.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI>Next message: <A HREF="016302.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16295">[ date ]</a>
<a href="thread.html#16295">[ thread ]</a>
<a href="subject.html#16295">[ subject ]</a>
<a href="author.html#16295">[ 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>
|