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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Missing packages in Mageia 1. How to backport?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Missing%20packages%20in%20Mageia%201.%20How%20to%20backport%3F&In-Reply-To=%3C201106111314.29979.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="005398.html">
<LINK REL="Next" HREF="005404.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Missing packages in Mageia 1. How to backport?</H1>
<B>Samuel Verschelde</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Missing%20packages%20in%20Mageia%201.%20How%20to%20backport%3F&In-Reply-To=%3C201106111314.29979.stormi%40laposte.net%3E"
TITLE="[Mageia-dev] Missing packages in Mageia 1. How to backport?">stormi at laposte.net
</A><BR>
<I>Sat Jun 11 13:14:29 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="005398.html">[Mageia-dev] Missing packages in Mageia 1. How to backport?
</A></li>
<LI>Next message: <A HREF="005404.html">[Mageia-dev] Missing packages in Mageia 1. How to backport?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#5400">[ date ]</a>
<a href="thread.html#5400">[ thread ]</a>
<a href="subject.html#5400">[ subject ]</a>
<a href="author.html#5400">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le samedi 11 juin 2011 12:06:55, Christiaan Welvaart a écrit :
><i> On Fri, 10 Jun 2011, Michael Scherer wrote:
</I>><i> > We can agree that everybody want something newer for some rpms, but few
</I>><i> > people want everything to be newer ( ie, now one run backports as a
</I>><i> > update media, I think ). So as much as I am against asking to users
</I>><i> > questions, we must show them the choice somewhere, in a non obstrusive
</I>><i> > way.
</I>><i>
</I>><i> Maybe, but how would be "support" this? We must be able to reproduce a
</I>><i> reported problem. This becomes complicated when we don't know what is
</I>><i> installed on the user's system. A guideline for bug reporters is (or
</I>><i> should be) "make sure you installed the latest updates". What would be the
</I>><i> equivalent for backports? I'm afraid it should be "if you installed any
</I>><i> backports, make sure you installed all backports that are relevant for
</I>><i> your system". If someone has a problem with any other combination, the bug
</I>><i> report might be rejected. How would QA even work when only selected
</I>><i> packages are upgraded from backports, or integration testing:
</I>><i> integration with what?
</I>><i>
</I>><i> So the only combinations we can support are:
</I>><i> - release + updates
</I>><i> - release + updates + backports
</I>><i>
</I>><i> More practical: for mga1 I have a VM that I can keep updated. For mga1
</I>><i> backports I can install another VM with backports enabled. But for bugs
</I>><i> reported with only selected backports installed I suppose I would have to
</I>><i> install a new VM with mga1, update it, and install only those backports -
</I>><i> for each bug report. But maybe I'm missing something, please explain. (:
</I>><i>
</I>
If we suppose that either updates or backports are supported (with a support
level to be defined), the situation is simpler to me : a good backport must
work with all its dependencies coming from updates or release OR it must
explicitly require higher versions, found only in the backports media and so
automatically pulled.
So I don't think that having picked up only certain backported packages is a
problem for the maintainer's support. Maybe I over-simplified the situation,
but I don't think it will be as complex as you say.
Samuel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/mageia-dev/attachments/20110611/976fba78/attachment.html>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="005398.html">[Mageia-dev] Missing packages in Mageia 1. How to backport?
</A></li>
<LI>Next message: <A HREF="005404.html">[Mageia-dev] Missing packages in Mageia 1. How to backport?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#5400">[ date ]</a>
<a href="thread.html#5400">[ thread ]</a>
<a href="subject.html#5400">[ subject ]</a>
<a href="author.html#5400">[ 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>
|
