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
|
<!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%09like%20--search-media&In-Reply-To=%3C5269757.sYA0OHxq7m%40localhost%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016710.html">
<LINK REL="Next" HREF="016740.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media</H1>
<B>AL13N</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%09like%20--search-media&In-Reply-To=%3C5269757.sYA0OHxq7m%40localhost%3E"
TITLE="[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media">alien at rmail.be
</A><BR>
<I>Thu Jun 21 19:39:25 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016710.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
</A></li>
<LI>Next message: <A HREF="016740.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#16714">[ date ]</a>
<a href="thread.html#16714">[ thread ]</a>
<a href="subject.html#16714">[ subject ]</a>
<a href="author.html#16714">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Op donderdag 21 juni 2012 17:36:58 schreef Thierry Vignaud:
><i> On 21 June 2012 17:27, AL13N <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">alien at rmail.be</A>> wrote:
</I>><i> >> You claim that it's not supported.
</I>><i> >> But cherry picking one backport is usually what people do.
</I>><i> >>
</I>><i> >> Denying the reality won't help you make progress...
</I>><i> >
</I>><i> > well, this time we agreed to have supported backports.
</I>><i> >
</I>><i> > it is true that almost all devs are cherry-picking backports, but are real
</I>><i> > users going to do that? i doubt it, but we don't have any data about this
</I>><i> > in any case.
</I>><i>
</I>><i> End users do not know about urpmi.
</I>><i> They knows about mgaupdate which shows them updates and about
</I>><i> rpmdrake which shows everything.
</I>><i> Thy _ONLY_ way for them to get a backport package installed is to
</I>><i> manually select one.
</I>><i> Period.
</I>
actually, that could change, i think it was stormi who proposed to adjust
mgaapplet to handle "backports for end users".
><i> > the reality is that if you want supported backports, there's literally no
</I>><i> > way of testing if all combinations of cherrypicking will work or not.
</I>><i> > thus, there is no other way solution than to support only having backports
</I>><i> > or not.
</I>><i>
</I>><i> That's bogus.
</I>><i> The truth is and always has been: if you install a backport package, it's
</I>><i> unsupported, it's at your own risks.
</I>><i> Claiming we support backports would be a like: we won't retest all existing
</I>><i> backported packages when pushing a new one.
</I>
this is exactly my point. but it's been decided several times in several
meetings (even since before mga1) that backports would be supported now.
There's even a policy accepted about QA on backports. I guess you didn't
follow the meetings or read up on the meeting logs?
[...]
><i> NACK. That's totally bogus.
</I>><i> Enabling the backport media DOES NOT imply "I want to install every
</I>><i> backports".
</I>><i> You're twisting the reality and the existing experience in order to match
</I>><i> your goals. That won't work...
</I>
i'm not twisting anything.
the only way you ever have supported backports, is that you only support
installing all backports that have packages in release.
If you find another way to support backports, please let us know.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016710.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
</A></li>
<LI>Next message: <A HREF="016740.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#16714">[ date ]</a>
<a href="thread.html#16714">[ thread ]</a>
<a href="subject.html#16714">[ subject ]</a>
<a href="author.html#16714">[ 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>
|
