blob: 4ab10b052b72dde07193af5a66ad930258c8f58b (
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
|
<!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=%3C4FE307C5.3080705%40eesti.ee%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016696.html">
<LINK REL="Next" HREF="016700.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media</H1>
<B>Sander Lepik</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=%3C4FE307C5.3080705%40eesti.ee%3E"
TITLE="[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media">sander.lepik at eesti.ee
</A><BR>
<I>Thu Jun 21 13:38:45 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016696.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
</A></li>
<LI>Next message: <A HREF="016700.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#16697">[ date ]</a>
<a href="thread.html#16697">[ thread ]</a>
<a href="subject.html#16697">[ subject ]</a>
<a href="author.html#16697">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>21.06.2012 14:30, Maarten Vanraes kirjutas:
><i> IF the update cannot work with the backported new dependency, it should be
</I>><i> strict required in the update. in that case, the one from release will be
</I>><i> used.
</I>><i>
</I>><i> if the update does work with the backport, then i don't see why you
</I>><i> wouldn't want that, since you enabled backports.
</I>><i> ==> this sounds like cherry-picking backports.
</I>><i>
</I>><i> in other words, you're advanced enough to find out what you want, because
</I>><i> i don't think we can support all forms of cherry-picking backports.
</I>Well, AFAIK there is still no stance on backports policy (are we backporting from cauldron
(n) to n-2 or not - if we do, we break upgradability here!). Cherry-picking backports is
needed. And i don't think that the packager who is creating update should check all possible
backports. What if that backport comes into play later? When the update is already released?
I still think that backports should not be used during updates. And it doesn't make QA work
any easier here. This is what we are trying to achieve.
--
Sander
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016696.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
</A></li>
<LI>Next message: <A HREF="016700.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#16697">[ date ]</a>
<a href="thread.html#16697">[ thread ]</a>
<a href="subject.html#16697">[ subject ]</a>
<a href="author.html#16697">[ 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>
|
