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
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
|
<!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=%3C11667604.lVdD1QXP42%40localhost%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016889.html">
<LINK REL="Next" HREF="016911.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Backports Summary</H1>
<B>AL13N</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C11667604.lVdD1QXP42%40localhost%3E"
TITLE="[Mageia-dev] Backports Summary">alien at rmail.be
</A><BR>
<I>Wed Jun 27 08:26:16 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016889.html">[Mageia-dev] Backports Summary
</A></li>
<LI>Next message: <A HREF="016911.html">[Mageia-dev] Backports Summary
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16869">[ date ]</a>
<a href="thread.html#16869">[ thread ]</a>
<a href="subject.html#16869">[ subject ]</a>
<a href="author.html#16869">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Op dinsdag 26 juni 2012 22:25:10 schreef Thomas Backlund:
><i> So,
</I>><i> we have been discussing this many times, and not gotten any
</I>><i> satisfactory decision to go ahead yet...
</I>[...]
><i> Now a point that got raised during discussion of bug 2317:
</I>><i> * if a backport break because of something ending up in /updates
</I>><i> it's a bug to be reported against the backport (and not against
</I>><i> the released update) as packages ending up in /updates are only
</I>><i> validated against /release and /updates (and rightfully so as
</I>><i> thats how they are built too)
</I>
* in the rare event that an update breaks because of something ending up in
/backports before the update was done, the users who had installed that
backport, will either need to install the new dependency that's in /release,
by replacing it with it's backported version manually. or will have to remove
the backport manually to allow the update to be installed.
I'm just giving this for reference, it should be added to the policy imho.
[...]
><i> And since we can continue this what/if discussion forever,
</I>><i> and thereby delay backports even more here is my take on it:
</I>><i>
</I>><i> my suggestions to decide on question 1 and 2:
</I>><i> 1. backporting bigger version to mga1 than mga2 has is
</I>><i> allowed as it will otherwise restrict backporting
</I>><i> too much. (and since its leaf packages, it should
</I>><i> not break (too much)). Lets just make it clear to
</I>><i> everyone using backports.
</I>><i>
</I>><i> 2. we cant really require that as the one backporting
</I>><i> the package to mga1 has to backport it to mga2 too
</I>><i> as he/she might not be using mga2 at all. if someone
</I>><i> wants/needs the backport for mga2, they need to
</I>><i> request that. (in reality, going by how backports
</I>><i> got handled in mdv most backports will end up in
</I>><i> all supported releases anyway)
</I>
I agree either way here. your suggestion is fine for me, another solution is
also fine
><i> If we can agree on this as a start, we can open backports
</I>><i> soon so we get actual facts of how backports policy and
</I>><i> process works.
</I>><i>
</I>><i> Then we rewiew backports policy and process in ~6 months,
</I>><i> and adjust it if needed.
</I>
I agree with you fully, except for the addendum and bug 2317. iinm QA
requested that bug 2317 would be fixed before backports opens, because it'll
make their job harder.
the patch i proposed was not good enough, so someone with more in-depth
knowledge of perl-urpm than myself needs to take a look at things.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016889.html">[Mageia-dev] Backports Summary
</A></li>
<LI>Next message: <A HREF="016911.html">[Mageia-dev] Backports Summary
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16869">[ date ]</a>
<a href="thread.html#16869">[ thread ]</a>
<a href="subject.html#16869">[ subject ]</a>
<a href="author.html#16869">[ 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>
|
