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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20bug%202317%20revisited%3A%20--update%20option%20should%20behave%0A%20like%20--search-media&In-Reply-To=%3C4FE5024E.7050304%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016766.html">
<LINK REL="Next" HREF="016783.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media</H1>
<B>andre999</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20bug%202317%20revisited%3A%20--update%20option%20should%20behave%0A%20like%20--search-media&In-Reply-To=%3C4FE5024E.7050304%40laposte.net%3E"
TITLE="[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media">andre999mga at laposte.net
</A><BR>
<I>Sat Jun 23 01:39:58 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016766.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
</A></li>
<LI>Next message: <A HREF="016783.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16768">[ date ]</a>
<a href="thread.html#16768">[ thread ]</a>
<a href="subject.html#16768">[ subject ]</a>
<a href="author.html#16768">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>AL13N a écrit :
><i> Op vrijdag 22 juni 2012 18:14:50 schreef David W. Hodgins:
</I>><i>
</I>>><i> On Fri, 22 Jun 2012 14:11:58 -0400, AL13N<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">alien at rmail.be</A>> wrote:
</I>>><i>
</I>>>><i> ok, i guess when people said, supported, i immediately assumed full
</I>>>><i> support. that kind of misled me.
</I>>>><i>
</I>>><i> My understanding, is that backports will have minimal testing.
</I>>><i>
</I>>><i> We ensure the backport will install, on a system that currently
</I>>><i> only has release + updates, and that the basic functions of the
</I>>><i> package work, where it's possible for us to test.
</I>>><i>
</I>>><i> We cannot possibly test every possible combination of selected
</I>>><i> backports, and will not attempt to.
</I>>><i>
</I>>><i> What I don't want to see, which I did with Mandriva backports,
</I>>><i> is cases where unsigned rpm packages were in the repositories,
</I>>><i> or installation required the use of --allow-nodeps or --allow-force,
</I>>><i> due to file conflicts with release or updates packages. Those
</I>>><i> problems were rare, but often enough, that I wouldn't let the end
</I>>><i> users I support install backports themselves.
</I>>><i>
</I>><i> well, imho even with this testing it's still possible, allthough likely rarer
</I>><i> that the user would have to use these or any other manual procedures. even
</I>><i> with updates.
</I>><i>
</I>><i> (unsigned rpms should be caught by the build process, even though it still
</I>><i> sometimes fails for reasons unbeknownst)
</I>><i>
</I>><i> in any case, i don't think of this as supported and won't suggest backports to
</I>><i> any user who doesn't have the necessary skills to fix it himself.
</I>><i>
</I>
Note that it depends what we mean by support.
In terms of support that would be provided by an expensive commercial
entity that specializes in support, some might argue that our release
packages aren't supported.
For backports, there is the understanding that in addition to being
tested by QA (after initial packager and end-user tests), that the
packager would commit to providing security updates as necessary. This
is much more than "no support at all", as happened with mdv backports.
Considering that each backport will be a leaf package (or exceptionally,
a leaf group of related packages), any breakage that would occur should
only affect the backport (or backport group) in question.
In terms of updates to backports, which I think is a good idea for
security fixes, any conflicts introduced should be rare. In those
cases, indeed updates could fail. But I don't think it is much more
likely than with packages from release or update repos.
Note that an end-user installing the occasional backport, to provide a
specific function desired, should not generally cause any problems.
Even for an end-user with minimal skills. As long as the user
understands that backports have a lower level of support. We have the
discuss list and the forum to help the end-user in the case of problems.
In sum, I like the idea of saying "tested by QA", as Claire proposed,
which suggests the lower level of support we propose for backports.
My 2 cents :)
--
André
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016766.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
</A></li>
<LI>Next message: <A HREF="016783.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16768">[ date ]</a>
<a href="thread.html#16768">[ thread ]</a>
<a href="subject.html#16768">[ subject ]</a>
<a href="author.html#16768">[ 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>
|
