blob: 1644091db3c1d6e58951bdc679f7ab4a9d381892 (
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
|
<!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=%3C4FD3A359.2090701%40linux.it%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016320.html">
<LINK REL="Next" HREF="016334.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Backports policy clarification (and discussion)</H1>
<B>Angelo Naselli</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=%3C4FD3A359.2090701%40linux.it%3E"
TITLE="[Mageia-dev] Backports policy clarification (and discussion)">anaselli at linux.it
</A><BR>
<I>Sat Jun 9 21:26:17 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016320.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI>Next message: <A HREF="016334.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16328">[ date ]</a>
<a href="thread.html#16328">[ thread ]</a>
<a href="subject.html#16328">[ subject ]</a>
<a href="author.html#16328">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Il 09/06/2012 12:39, Thomas Backlund ha scritto:
>><i> OK. To backport from Cauldron to mga1, we have to backport from
</I>>><i>
</I>>>><i> Cauldron to mga2, (bumping the revision in cauldron to ensure
</I>>>><i> that is is higher), then backport from mga2 to mga1, ensuring
</I>>>><i> that the revision is lower in mga1 than in mga2. (e.g.
</I>>>><i> revision x.1 in cauldron, x.0.1 in mga2, x.0.0.1 in mga1)
</I>>>><i> Pretty straight forward.
</I>>>><i>
</I>><i> Not needed as 1.mgaX > 1.mga3 > 1.mga2 > 1.mga1
</I>><i>
</I>IIUC the only problem is when in the above situation
we have 1.1.mga1 for any reasons (bug fixing for instance, maybe not
needed in any mgaX > mga1).
I believe in that situation who makes the bug-fixing has to work on
other back-ports/updates because in mgaX > mga1 that package could be
in core and not in bp.
ANgelo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - <A HREF="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</A>
iEYEARECAAYFAk/To1UACgkQqEs9DA4DquCUaACZAbWbqiAWkJ+XYZNXgop/jKz4
IukAoLhCfKvT488tdSia/L/c5HM3gy1N
=CRDk
-----END PGP SIGNATURE-----
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016320.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI>Next message: <A HREF="016334.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16328">[ date ]</a>
<a href="thread.html#16328">[ thread ]</a>
<a href="subject.html#16328">[ subject ]</a>
<a href="author.html#16328">[ 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>
|
