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
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Bug 2317.
</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.&In-Reply-To=%3Cop.v1t9xuehn7mcit%40hodgins.homeip.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="008197.html">
<LINK REL="Next" HREF="008081.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Bug 2317.</H1>
<B>David W. Hodgins</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Bug%202317.&In-Reply-To=%3Cop.v1t9xuehn7mcit%40hodgins.homeip.net%3E"
TITLE="[Mageia-dev] Bug 2317.">davidwhodgins at gmail.com
</A><BR>
<I>Thu Sep 15 09:33:19 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="008197.html">[Mageia-dev] systemd vs dm
</A></li>
<LI>Next message: <A HREF="008081.html">[Mageia-dev] Bug 2317.
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8079">[ date ]</a>
<a href="thread.html#8079">[ thread ]</a>
<a href="subject.html#8079">[ subject ]</a>
<a href="author.html#8079">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>
It's very clear from the reply in bug 2720 that some packagers still do not
understand the scope of bug 2317. Hence I've decided to post my reply
to one comment here.
(In reply to comment #8)
><i> Well the first step here would be that the packager & the QA team after to
</I>><i> install package from testing withurpmi --use-media "Core Testing" yourpackage
</I>
Ever since bug 2317 was opened, qa have been watching for packages
being installed from the Release repositories.
The problem is, that the only way to recreate this problem is to start
with a Mandriva 2010.2 system, with task-kde4 installed AND the package
called root.
When the op upgraded from Mandriva, the version specific dependencies
of the package called root (or one of it's dependencies) prevented the
Mandriva versions of libiodbc2 from being upgraded.
Now, when an upgrade of task-kde4 is being installed using mgaapplet,
it (or one of it's dependencies) has a version specific requires, or
selects the package because it has a higher release, or version, for
a package that is only in Core Release, so the update fails.
This didn't happen during beta testing, as none of the people doing
the beta testing had the package called root installed from Mandriva.
I may be wrong about which package prevented the dependencies from
being installed, but that doesn't matter. Some Mandriva package
(not available in Mageia 1) has version specific requires, which
blocked the update during the upgrade to Mageia.
The only possible methods of dealing with this (as I see it) ...
- Alter MegeiaUpdate to do the equivalent of urpmi --auto-select
- link all of the Release packages in the Release repositories
in corresponding Updates Testing and Updates repositories.
(Massive synthesis.hdlist.cz files)
- Create installations of Mandriva 2010.2 with all possible combinations
of packages, and test every update on each installation.
(Not possible with time/diskspace)
- For each update, get a list of every dependency, then get a list of
every package that requires that dependency on Mandriva 2010.2, and
check each of the .spec files for version dependant requires, and
link those packages only, to both Updates Testing, and Updates.
(Very time consuming for QA).
While changing MageiaUpdate to do the equivalent of urpmi --auto-select
will have an impact on speed, it is the only reasonable solution, in
my opinion.
I tried to provide a patch to fix the problem, it failed, as it also
picked up suggestions from non-enabled repositories. While I can usually
figure out what perl code does, I'm not a perl programmer. We need
someone who knows perl and urpmi, to fix this, and quickly.
Regards, Dave Hodgins
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="008197.html">[Mageia-dev] systemd vs dm
</A></li>
<LI>Next message: <A HREF="008081.html">[Mageia-dev] Bug 2317.
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8079">[ date ]</a>
<a href="thread.html#8079">[ thread ]</a>
<a href="subject.html#8079">[ subject ]</a>
<a href="author.html#8079">[ 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>
|
