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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] missing upload lib64edataserverui4-3.5.3.1-2.mga3
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20missing%20upload%20lib64edataserverui4-3.5.3.1-2.mga3&In-Reply-To=%3C4FF0B074.7050008%40colin.guthr.ie%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="017069.html">
<LINK REL="Next" HREF="017062.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] missing upload lib64edataserverui4-3.5.3.1-2.mga3</H1>
<B>Colin Guthrie</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20missing%20upload%20lib64edataserverui4-3.5.3.1-2.mga3&In-Reply-To=%3C4FF0B074.7050008%40colin.guthr.ie%3E"
TITLE="[Mageia-dev] missing upload lib64edataserverui4-3.5.3.1-2.mga3">mageia at colin.guthr.ie
</A><BR>
<I>Sun Jul 1 22:17:56 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="017069.html">[Mageia-dev] missing upload lib64edataserverui4-3.5.3.1-2.mga3
</A></li>
<LI>Next message: <A HREF="017062.html">[Mageia-dev] Slowly pushing GNOME 3.5.3
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#17075">[ date ]</a>
<a href="thread.html#17075">[ thread ]</a>
<a href="subject.html#17075">[ subject ]</a>
<a href="author.html#17075">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>'Twas brillig, and Thomas Backlund at 01/07/12 20:48 did gyre and gimble:
><i> 01.07.2012 22:44, Jani Välimaa skrev:
</I>>><i> On 01.07.2012 22:37, Thomas Backlund wrote:
</I>>>><i> 01.07.2012 22:33, Jani Välimaa skrev:
</I>>>>><i> On 01.07.2012 22:20, Olav Vitters wrote:
</I>>>>>><i> On Sun, Jul 01, 2012 at 08:41:15PM +0300, Jani Välimaa wrote:
</I>>>>>>><i> I guess the .spec needs some cleaning as there's more unneeded
</I>>>>>>><i> obsoletes/defines. E.g. 'Obsoletes: %oldlibname2006' obsoletes lib which
</I>>>>>>><i> was available in mdv 2006.0.
</I>>>>>><i>
</I>>>>>><i> Only cleaned the Obsoletes thing for lib64edataserverui4. Still facing
</I>>>>>><i> issues :-(
</I>>>>>><i>
</I>>>>>><i> Installation failed: lib64edataserverui4 is obsoleted by (installed)
</I>>>>>><i> lib64edataserverui1-3.4.3-1.mga3.x86_64
</I>>>>>><i>
</I>>>>>><i>
</I>>>>>><i> How can I avoid that?
</I>>>>>><i>
</I>>>>><i>
</I>>>>><i> I guess that's because the old obsoletes wasn't versioned. If the old
</I>>>>><i> lib isn't needed by any other pkg, you could remove it first.
</I>>>>><i>
</I>>>>><i>
</I>>>><i>
</I>>>><i> Trouble is it will hit us during upgrade from mga2 to mga3.
</I>>>><i>
</I>>>><i> So I guess it need a versioned conflict to force the upgrade
</I>>>><i>
</I>>><i>
</I>>><i> Another possible solution would be an updated mga2 pkg to core/updates.
</I>>><i>
</I>><i>
</I>><i> Indeed, and with the planned GNOME updates for mga2, this can be fixed
</I>><i>
</I>><i>
</I>>><i> However that doesn't fix the update problem if user doesn't update
</I>>><i> his/hers mga2 up-to-date before ugrading to mga3.
</I>>><i>
</I>><i>
</I>><i> True, but most will probably jump on the update for mga2,
</I>><i> for the rest we need to add a versioned conflict.
</I>
Just for reference (I'll post full details once I've got them worked
out), the upgrade process from mga2 (or earlier) to mga3 will likely be
interesting due to the planned usr move.
It will probably require a "preparation" step which will involve booting
with a special initrd. This will likely need updated packages.
So while we can't guarantee users upgrade *this* package, we might have
to mandate that users will install at least some updates!
The process itself is actually relatively simple, but I think personally
it would be nice to get the base bits done before the big rebuild after
the new glibc comes along as we can use the opportunity to add some
extra lint rules and tidy up some specs.
Col
--
Colin Guthrie
colin(at)mageia.org
<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
Day Job:
Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>
Open Source:
Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A>
PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>
Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="017069.html">[Mageia-dev] missing upload lib64edataserverui4-3.5.3.1-2.mga3
</A></li>
<LI>Next message: <A HREF="017062.html">[Mageia-dev] Slowly pushing GNOME 3.5.3
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#17075">[ date ]</a>
<a href="thread.html#17075">[ thread ]</a>
<a href="subject.html#17075">[ subject ]</a>
<a href="author.html#17075">[ 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>
|
