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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Trying to solve bug #2317 (was: Re: Meeting tonight)
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Trying%20to%20solve%20bug%20%232317%20%28was%3A%20Re%3A%20Meeting%20tonight%29&In-Reply-To=%3C201109221435.55143.stormi%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="008288.html">
<LINK REL="Next" HREF="008309.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Trying to solve bug #2317 (was: Re: Meeting tonight)</H1>
<B>Samuel Verschelde</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Trying%20to%20solve%20bug%20%232317%20%28was%3A%20Re%3A%20Meeting%20tonight%29&In-Reply-To=%3C201109221435.55143.stormi%40laposte.net%3E"
TITLE="[Mageia-dev] Trying to solve bug #2317 (was: Re: Meeting tonight)">stormi at laposte.net
</A><BR>
<I>Thu Sep 22 14:35:55 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="008288.html">[Mageia-dev] Meeting tonight
</A></li>
<LI>Next message: <A HREF="008309.html">[Mageia-dev] Trying to solve bug #2317 (was: Re: Meeting tonight)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8308">[ date ]</a>
<a href="thread.html#8308">[ thread ]</a>
<a href="subject.html#8308">[ subject ]</a>
<a href="author.html#8308">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le jeudi 15 septembre 2011 16:12:11, Thierry Vignaud a écrit :
[...]
><i> Suggestions:
</I>><i> - investigating using the equivalent of --searchmedia
</I>
That is an interesting option indeed.
><i> - reusing the old connectiva upgrade infrastructure in the drakx installer
</I>><i> and release a patched installed (a mageia 1.1) that list mdv packages,
</I>><i> remove them prior to upgrading"
</I>
This looks like a heavy solution (needs new ISOs, doesn't cover already
migrated systems, means that mdv packages that have no equivalent in mageia
are removed from the system), so it's not my preferred solution.
><i> - patch perl-URPM so that foobar-X-Ymga is always newer than foobar-Z-Wmdv
</I>
I'm sorry, but I don't understand what problems this third option would solve.
Can you explain to me (and maybe I'm not alone) ?
><i>
</I>><i> In the first case, we would go with something like r[1-4].diff
</I>><i> warning: unknown impact on startup time & RAM usage (in fact it's not
</I>><i> even tested)
</I>
I applied those 4 patches to rpmdrake and built a RPM that I installed on my
system, but I haven't seen a difference in behaviour. The msec update candidate
from updates_testing (updates_testing media have the update flag set on my
system) still can't be installed, with the following message:
Sorry, the following package cannot be selected:
- msec-0.80.10-2.2.mga1.i586 (due to unsatisfied sendmail)
It apparently still doesn't use the /release media in MageiaUpdate, if I infer
correctly from the console logs :
[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">root at localhost</A> ~]# LC_ALL=C MageiaUpdate
getting lock on urpmi
using mirror <A HREF="ftp://distrib-">ftp://distrib-</A>
coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/1/i586
retrieved $MIRRORLIST media/core/updates media_info/MD5SUM
comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Core
Updates/MD5SUM
medium "Core Updates" is up-to-date
retrieved $MIRRORLIST media/core/updates_testing media_info/MD5SUM
comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Core Updates
Testing/MD5SUM
medium "Core Updates Testing" is up-to-date
retrieved $MIRRORLIST media/nonfree/updates media_info/MD5SUM
comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Nonfree
Updates/MD5SUM
medium "Nonfree Updates" is up-to-date
retrieved $MIRRORLIST media/nonfree/updates_testing media_info/MD5SUM
comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Nonfree Updates
Testing/MD5SUM
medium "Nonfree Updates Testing" is up-to-date
retrieved $MIRRORLIST media/tainted/updates media_info/MD5SUM
comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Tainted
Updates/MD5SUM
medium "Tainted Updates" is up-to-date
retrieved $MIRRORLIST media/tainted/updates_testing media_info/MD5SUM
comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Tainted Updates
Testing/MD5SUM
medium "Tainted Updates Testing" is up-to-date
unlocking urpmi database
getting lock on urpmi
using mirror <A HREF="ftp://distrib-">ftp://distrib-</A>
coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/1/i586
examining synthesis file [/var/lib/urpmi/Core Updates/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/Core Updates
Testing/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/Nonfree Updates/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/Nonfree Updates
Testing/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/Tainted Updates/synthesis.hdlist.cz]
examining synthesis file [/var/lib/urpmi/Tainted Updates
Testing/synthesis.hdlist.cz]
[...]
><i> >> 1) we know there will be cases where it won't work
</I>><i> >> (see above those with the DVD media and not the full network
</I>><i> >> media, some new dependencies won't be found on the DVD, ...).
</I>><i> >> Multiply by those who have installed 32 DVD, 64 DVD, dual arch DVD,
</I>><i> >> ... There are lots of different scenarios to deal with ...
</I>><i> >
</I>><i> > I think most of us are ready to ask users to add the full media set along
</I>><i> > with updates media.
</I>><i>
</I>><i> And still you won't catch the users that won't ask you, that won't read the
</I>><i> doc, ...
</I>><i> You can increase the % of end users that will be covered but I fear you
</I>><i> won't even cover 50% of them.
</I>
Yes, that is something we will have to decide independently of bug 2137 : do
we still want self-contained updates media in the future (when the mdv=>mga
transition problem will be gone) or not. I don't know, I see drawbacks in both
ways.
If the tools add the whole media set by default (removing the button that
proposes only updates media), and if we add proper warnings and helpers in the
right place (for example have MageiaUpdate and/or rpmdrake detect the lack of
activated release media and propose to add them, the way it does for update
media currently), we should cover much more than 50% of the end-users.
Also, a message such as "Sorry, the following package cannot be selected:
- msec-0.80.10-2.2.mga1.i586 (due to unsatisfied sendmail)" is much more
understandable when you *don't* have release media available on your system
than when you do. Especially when starting the update tool you already got a
message saying that you should activate the release media.
So the main argument that I would keep in favor of copying dependencies to
updates media would be if we want to support the mirroring of updates media
only. But I'm not sure it is worth the extra work (although I may be wrong).
[...]
><i>
</I>><i> > The main difficulty is handling the transition, but this is
</I>><i> > doable too. For people who might disable release media, this may be a
</I>><i> > problem, but is there really an interesting use case for disabling
</I>><i> > release media and activating updates media ?
</I>><i>
</I>><i> Whether it's either interesting or not, some people just do that.
</I>><i>
</I>><i> Or play with /etc/urpmi/skip.list.
</I>><i> Another scenario I didn't bring attention upon..
</I>
Indeed. But those should understand the error message I hope (and if they
don't, well, *they* played with the skip list :) ).
><i> >> Will you provides patches, test scenario and do the testing?
</I>><i> >
</I>><i> > Patches, not sure. Test scenarios is doable, testing too.
</I>><i>
</I>><i> The faillure of the proposed patch should be a scenario for regression
</I>><i> testing btw.
</I>
Indeed.
Best regards
Samuel
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="008288.html">[Mageia-dev] Meeting tonight
</A></li>
<LI>Next message: <A HREF="008309.html">[Mageia-dev] Trying to solve bug #2317 (was: Re: Meeting tonight)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8308">[ date ]</a>
<a href="thread.html#8308">[ thread ]</a>
<a href="subject.html#8308">[ subject ]</a>
<a href="author.html#8308">[ 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>
|
