summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-June/016922.html
blob: 083fa19286c43ee9b281f856aec52d55bf9ab0c5 (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
137
138
139
140
141
142
143
144
145
146
<!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=%3C4FEB1A85.8090307%40laposte.net%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="016920.html">
   <LINK REL="Next"  HREF="016927.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Backports Summary</H1>
    <B>andre999</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C4FEB1A85.8090307%40laposte.net%3E"
       TITLE="[Mageia-dev] Backports Summary">andre999mga at laposte.net
       </A><BR>
    <I>Wed Jun 27 16:36:53 CEST 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="016920.html">[Mageia-dev] Backports Summary
</A></li>
        <LI>Next message: <A HREF="016927.html">[Mageia-dev] Backports Summary
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16922">[ date ]</a>
              <a href="thread.html#16922">[ thread ]</a>
              <a href="subject.html#16922">[ subject ]</a>
              <a href="author.html#16922">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>nicolas vigier a &#233;crit :
&gt;<i> On Wed, 27 Jun 2012, andre999 wrote:
</I>&gt;<i>
</I>&gt;<i>    
</I>&gt;&gt;<i> Thomas Backlund a &#233;crit :
</I>&gt;&gt;<i>      
</I>&gt;&gt;&gt;<i> andre999 skrev 27.6.2012 14:40:
</I>&gt;&gt;&gt;<i>        
</I>&gt;&gt;&gt;&gt;<i> Thomas Backlund a &#233;crit :
</I>&gt;&gt;&gt;&gt;<i>          
</I>&gt;&gt;&gt;&gt;&gt;<i> andre999 skrev 27.6.2012 10:47:
</I>&gt;&gt;&gt;&gt;&gt;<i>            
</I>&gt;&gt;&gt;<i>        
</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> I would favour adding the requirement that the dependancies of the
</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> backport must be available in the next release.  So that we would
</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> expect
</I>&gt;&gt;&gt;&gt;&gt;&gt;<i>              
</I>&gt;&gt;&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;&gt;&gt;<i> This is esentially stating that we cant backport any bigger version to
</I>&gt;&gt;&gt;&gt;&gt;<i> mga2 /backports than mga3 will havein /release wich means when we hit
</I>&gt;&gt;&gt;&gt;&gt;<i> version freeze for mga3, it also freezes mga2 /backports...
</I>&gt;&gt;&gt;&gt;&gt;<i>            
</I>&gt;&gt;&gt;&gt;<i> I'm not following this point.
</I>&gt;&gt;&gt;&gt;<i> What I mean is that if backport xx for mga1 requires yy version 12 in
</I>&gt;&gt;&gt;&gt;<i> mga1, but yy is version 13 in mga2, we would define the requires for yy
</I>&gt;&gt;&gt;&gt;<i> to accept versions 12 to 13 (or maybe wider).
</I>&gt;&gt;&gt;&gt;<i>          
</I>&gt;&gt;&gt;<i> Point is what if you backport version 14 to mga1, and mga2 has version 13,
</I>&gt;&gt;&gt;<i> then upgrade path breaks.
</I>&gt;&gt;&gt;<i>        
</I>&gt;&gt;<i> No problem.  If the requirements of version 14 are present in mga2, then
</I>&gt;&gt;<i> the backport will (very likely) continue to work normally.  If the versions
</I>&gt;&gt;<i> of the required packages change, they will be updated with the upgrade.
</I>&gt;&gt;<i> Since version 13 of mga2 is less than the version 14 of the backport, it
</I>&gt;&gt;<i> won't be installed.
</I>&gt;&gt;<i>      
</I>&gt;<i> There is no guaranty that requirements of version 14 mga1 backports are
</I>&gt;<i> all available in mageia 2. If it is linked with libsomething.so.1, but
</I>&gt;<i> mageia 2 only has libsomething.so.2, then there is a problem.
</I>&gt;<i>
</I>&gt;<i>    
</I>That was my point.
I was suggesting that it be required that backport requires be 
compatible with newer releases.
In your example, cauldron would probably require the libsomething.so.2, 
so if the backport requires could be adjusted to work with 
libsomething.so.1, we would keep the requires compatible with 
libsomething.so.2.  If that isn't possible, then it wouldn't be accepted.
I'm no expert of course, but it seems to me that it would be generally 
possible as long as there weren't important code changes made to make 
the backport work.
So it would largely be a question of appropriately adjusting the 
specified requires.

-- 
Andr&#233;

</PRE>



































<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="016920.html">[Mageia-dev] Backports Summary
</A></li>
	<LI>Next message: <A HREF="016927.html">[Mageia-dev] Backports Summary
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16922">[ date ]</a>
              <a href="thread.html#16922">[ thread ]</a>
              <a href="subject.html#16922">[ subject ]</a>
              <a href="author.html#16922">[ 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>