blob: a50fc4a00a392ab022a7e7d43a13b5819c5b3198 (
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
|
<!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=%3C4FEAF355.7000501%40mageia.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016906.html">
<LINK REL="Next" HREF="016917.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Backports Summary</H1>
<B>Thomas Backlund</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C4FEAF355.7000501%40mageia.org%3E"
TITLE="[Mageia-dev] Backports Summary">tmb at mageia.org
</A><BR>
<I>Wed Jun 27 13:49:41 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016906.html">[Mageia-dev] Backports Summary
</A></li>
<LI>Next message: <A HREF="016917.html">[Mageia-dev] Backports Summary
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16909">[ date ]</a>
<a href="thread.html#16909">[ thread ]</a>
<a href="subject.html#16909">[ subject ]</a>
<a href="author.html#16909">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>andre999 skrev 27.6.2012 14:40:
><i> Thomas Backlund a écrit :
</I>>><i> andre999 skrev 27.6.2012 10:47:
</I>
>>><i> I would favour adding the requirement that the dependancies of the
</I>>>><i> backport must be available in the next release. So that we would expect
</I>>><i>
</I>>><i>
</I>>><i> This is esentially stating that we cant backport any bigger version to
</I>>><i> mga2 /backports than mga3 will havein /release wich means when we hit
</I>>><i> version freeze for mga3, it also freezes mga2 /backports...
</I>><i>
</I>><i> I'm not following this point.
</I>><i> What I mean is that if backport xx for mga1 requires yy version 12 in
</I>><i> mga1, but yy is version 13 in mga2, we would define the requires for yy
</I>><i> to accept versions 12 to 13 (or maybe wider).
</I>
Point is what if you backport version 14 to mga1, and mga2 has version
13, then upgrade path breaks.
--
Thomas
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016906.html">[Mageia-dev] Backports Summary
</A></li>
<LI>Next message: <A HREF="016917.html">[Mageia-dev] Backports Summary
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16909">[ date ]</a>
<a href="thread.html#16909">[ thread ]</a>
<a href="subject.html#16909">[ subject ]</a>
<a href="author.html#16909">[ 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>
|
