blob: fa46b0cdb13ecf32d0236c18715057c9671b02c7 (
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
|
<!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=%3C4FE36618.50708%40gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016718.html">
<LINK REL="Next" HREF="016721.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media</H1>
<B>Claire Robinson</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=%3C4FE36618.50708%40gmail.com%3E"
TITLE="[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media">eeeemail at gmail.com
</A><BR>
<I>Thu Jun 21 20:21:12 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016718.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
</A></li>
<LI>Next message: <A HREF="016721.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#16719">[ date ]</a>
<a href="thread.html#16719">[ thread ]</a>
<a href="subject.html#16719">[ subject ]</a>
<a href="author.html#16719">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>
><i> actually, it doesn't need to be.
</I>><i>
</I>><i> you already test twice before validating updates, right?
</I>><i>
</I>><i> so, there's 2 options:
</I>><i>
</I>><i> - testing i586 with backports enabled
</I>><i> - testing x86_64 without backports enabled
</I>><i>
</I>><i> this is still 2 tests, and this is sufficient.
</I>
QA backports testing procedure has not yet been agreed, we can't really
without knowing what packager policy is and that is not even close yet.
They will be our lowest priority though obviously.
It is very likely we will test backports the same as an update. ie. i586
and x86_64.
In the case where an update has a tainted build we test the tainted
build x86_64 and i586 aswell as the core build x86_64 and i586.
Your suggestion adds further complexity and work to a team already
swamped and struggling to cope, this without backports even being open.
That is not sustainable. It would be remiss of me to pretend otherwise,
sorry.
We would be using a workaround for the solution to the workaround for
the bug.
There has to be another solution..
Claire
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016718.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
</A></li>
<LI>Next message: <A HREF="016721.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#16719">[ date ]</a>
<a href="thread.html#16719">[ thread ]</a>
<a href="subject.html#16719">[ subject ]</a>
<a href="author.html#16719">[ 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>
|
