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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] [changelog] [RPM] cauldron core/release meta-task-2-21.mga2
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bchangelog%5D%20%5BRPM%5D%20cauldron%20core/release%0A%09meta-task-2-21.mga2&In-Reply-To=%3CCAONrEtbPzrihbkp3UWVLoGO9Hq%3DxJXcQhsC6M623gMo%3DPB342g%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="011391.html">
<LINK REL="Next" HREF="011394.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] [changelog] [RPM] cauldron core/release meta-task-2-21.mga2</H1>
<B>Thierry Vignaud</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bchangelog%5D%20%5BRPM%5D%20cauldron%20core/release%0A%09meta-task-2-21.mga2&In-Reply-To=%3CCAONrEtbPzrihbkp3UWVLoGO9Hq%3DxJXcQhsC6M623gMo%3DPB342g%40mail.gmail.com%3E"
TITLE="[Mageia-dev] [changelog] [RPM] cauldron core/release meta-task-2-21.mga2">thierry.vignaud at gmail.com
</A><BR>
<I>Mon Jan 16 11:41:34 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="011391.html">[Mageia-dev] [changelog] [RPM] cauldron core/release meta-task-2-21.mga2
</A></li>
<LI>Next message: <A HREF="011394.html">[Mageia-dev] [changelog] [RPM] cauldron core/release meta-task-2-21.mga2
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11392">[ date ]</a>
<a href="thread.html#11392">[ thread ]</a>
<a href="subject.html#11392">[ subject ]</a>
<a href="author.html#11392">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 16 January 2012 10:37, Thomas Backlund <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">tmb at mageia.org</A>> wrote:
>>>><i> This is wrong, you're just introducing two different behaviors:
</I>>>>><i> - new installations will got drakcut&    systemd
</I>>>>><i> - updated ones will keep mkinitrd&    sysvinit
</I>>>><i>
</I>>>><i>
</I>>>><i> How about enhancing urpmi to read prefer.vendor.list during distro
</I>>>><i> upgrade? That would solve this issue.
</I>>>><i> either by a specific --upgrade flag,
</I>>>><i> or automatically when mageia-release-common bumps version, would that
</I>>>><i> work ?
</I>>><i>
</I>>><i>
</I>>><i> This is already done. But prefer choice only apply to initial package
</I>>><i> installation.
</I>><i>
</I>><i>
</I>><i> Which is why I asked if it should do it during upgrade too ?
</I>
OK, there's obviously some confusion here.
There's two different things:
- preferred apps (read: what is the default choice when several packages
answer the some "virtual" require)
- provides & obsolete tags
That's totally orthogonal and preferred apps just don't apply to upgrading...
If you install a package requesting eg "web_server" which would provided
by say both apache & nginx, whatever you choose one manually or through
automatically (preferred apps) doesn't change that after inital install, only
provides & obsolete tags matter for upgrading.
What's more, even if that was possible, what you're asking is basically
replace "forcing systemd & drakcut through requires/obsoletes tags" by
"forcing them through adding special urpmi code".
Either way, you would force them...
Anyway, urpmi's preferred packages is not a super obsolete/require
tags as explained above.
>><i> Hard requires are not an issue:
</I>>><i> - for systemd if systemd-sysvinit isn't hard required, which was
</I>>><i> already the case
</I>><i>
</I>><i> Doh, I forgot about that it was sysvinit vs systemd-sysvinit and not systemd
</I>><i> itself :(
</I>><i>
</I>><i> so systemd can/must be readded as requires.
</I>
Indeed.
>><i> - for drakcut, as alternatives are used
</I>><i>
</I>><i>
</I>><i> Yep. useful as long as there is a mkinitrd on the mirrors.
</I>
I think the clean way to go would be to:
1) rename mkinitrd & sysvinit as mkinitrd-old & sysvinit-old:
2) having both sysvinit-old & systemd-sysvinit provides/obsoletes sysvinit
(dito for mkinitrd-old & dracut)
Then on upgrade, as mkinitrd & sysvinit would be obsoleted by new packages
(eg: systemd-sysvinit & sysvini-old), urpmi would have to choose one,
choosing dracut & systemd by default due to prefered list.
Thus we would achieve both:
- having dracut & systemd on upgrade too
- being able to fallback to mkinitrd and/or sysvinit by manually requesting
their installation.
Other ways would be to:
1) have mkinitrd & sysvinit requesting drakcut & systemd-sysvinit
& adding alternatives to systemd/sysvinit :-(
2) manually adding greater provides to systemd-sysvinit & mkinitrd
(error prone & fallback involves manually editing skip.list which may
break further upgrading from mga2 to mga3 when mkinitrd & sysvinit
will be really dead)
>>><i> If both dracut and mkinitrd provides mkinitrd, the prefer list must
</I>>>><i> contain the one we want by default, wich is what I did here.
</I>>><i>
</I>>><i>
</I>>><i> Yes but you also remove all of the obsolete/provides tag, which prevents
</I>>><i> drakcut
</I>>><i> to replace mkinitrd on upgrade.
</I>>><i>
</I>><i>
</I>><i> Check again. I only removed Obsoletes, the Provides is still there:
</I>><i> <A HREF="http://svnweb.mageia.org/packages/cauldron/dracut/current/SPECS/dracut.spec?r1=194858&r2=196541">http://svnweb.mageia.org/packages/cauldron/dracut/current/SPECS/dracut.spec?r1=194858&r2=196541</A>
</I>
Which is useless w/o the obsolete tag.
Have you checked what happens on upgrade? Does drakcut replace mkinitrd if some
repo still has mkinitrd?
Anyway it won't work for systemd as its provide tag is smaller in
systemd-sysvinit than sysvinit
And it's error prone.
Also see above, fallbacking involves playing with skip.list which may
break next upgrade
(mga2 -> mga3)
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="011391.html">[Mageia-dev] [changelog] [RPM] cauldron core/release meta-task-2-21.mga2
</A></li>
<LI>Next message: <A HREF="011394.html">[Mageia-dev] [changelog] [RPM] cauldron core/release meta-task-2-21.mga2
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11392">[ date ]</a>
<a href="thread.html#11392">[ thread ]</a>
<a href="subject.html#11392">[ subject ]</a>
<a href="author.html#11392">[ 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>
|
