summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-June/016289.html
blob: b521b7b7d4f7e5c0d98614d9488e8e5fca1a1857 (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
133
134
135
136
<!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=%3C201206081622.41169.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="016288.html">
   <LINK REL="Next"  HREF="016290.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=%3C201206081622.41169.stormi%40laposte.net%3E"
       TITLE="[Mageia-dev] Backports policy clarification (and discussion)">stormi at laposte.net
       </A><BR>
    <I>Fri Jun  8 16:22:41 CEST 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="016288.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
        <LI>Next message: <A HREF="016290.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16289">[ date ]</a>
              <a href="thread.html#16289">[ thread ]</a>
              <a href="subject.html#16289">[ subject ]</a>
              <a href="author.html#16289">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Le vendredi 8 juin 2012 16:11:07, andre999 a &#233;crit :
&gt;<i> Sander Lepik a &#233;crit :
</I>&gt;<i> &gt; 08.06.2012 11:38, Samuel Verschelde kirjutas:
</I>&gt;<i> &gt;&gt; I re-read the backports policy, and there's a part I think needs to be
</I>&gt;<i> &gt;&gt; pointed out before people start to backport packages.
</I>&gt;<i> &gt;&gt; 
</I>&gt;<i> &gt;&gt; &quot;We need to ensure that upgrades never fail: cauldron must always have a
</I>&gt;<i> &gt;&gt; higher version/release than in stable releases.&quot;
</I>&gt;<i> &gt;&gt; 
</I>&gt;<i> &gt;&gt; This statement is true, but implies more than what it says. It means
</I>&gt;<i> &gt;&gt; that we can't backport a package for Mageia 1 with a higher version
</I>&gt;<i> &gt;&gt; than what we have in Mageia 2 release (and updates?) media. And this,
</I>&gt;<i> &gt;&gt; until we are able to take backports into account during upgrades.
</I>&gt;<i> &gt;&gt; 
</I>&gt;<i> &gt;&gt; Example :
</I>&gt;<i> &gt;&gt; - Mageia 2 has wesnoth 1.10.2 in core/release
</I>&gt;<i> &gt;&gt; - Mageia 1 can't get a higher version in its backports media
</I>&gt;<i> &gt;&gt; 
</I>&gt;<i> &gt;&gt; Do you all agree with my understanding of the policy ?
</I>&gt;<i> 
</I>&gt;<i> I see your point.
</I>&gt;<i> In most cases, a backport for mga1 would be essentially identical for
</I>&gt;<i> mga2 (except package file name and corresponding changes in the spec file).
</I>&gt;<i> It would only differ if dependancies differ, which I suspect is unlikely
</I>&gt;<i> for wesnoth or most other games, for example.
</I>&gt;<i> So this means that for a backport to mga1, we should first do one to mga2.
</I>&gt;<i> This would more than likely be done at the same time by the same
</I>&gt;<i> packager, so not much more work.
</I>&gt;<i> The demand for backports to mga1 is not likely to be very high, and
</I>&gt;<i> would depend on a willing packager.
</I>
I think you missed my point. If Mageia 1 &quot;backports&quot; has higher versions than 
Mageia 2 &quot;release&quot; (not backports), upgrade can fail because currently our 
tools do not take backports from the target release (mageia 2) into account 
when upgrading a distro.

Samuel
</PRE>













































<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="016288.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
	<LI>Next message: <A HREF="016290.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16289">[ date ]</a>
              <a href="thread.html#16289">[ thread ]</a>
              <a href="subject.html#16289">[ subject ]</a>
              <a href="author.html#16289">[ 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>