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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Copying dependencies to Updates (Testing), or changing mgaapplet to use urpmi --auto-update instead of urpmi --update.
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Copying%20dependencies%20to%20Updates%20%28Testing%29%2C%0A%09or%20changing%20mgaapplet%20to%20use%20urpmi%20--auto-update%20instead%20of%20urpmi%0A%09--update.&In-Reply-To=%3C201109051206.40002.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="007773.html">
<LINK REL="Next" HREF="007734.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Copying dependencies to Updates (Testing), or changing mgaapplet to use urpmi --auto-update instead of urpmi --update.</H1>
<B>Samuel Verschelde</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Copying%20dependencies%20to%20Updates%20%28Testing%29%2C%0A%09or%20changing%20mgaapplet%20to%20use%20urpmi%20--auto-update%20instead%20of%20urpmi%0A%09--update.&In-Reply-To=%3C201109051206.40002.stormi%40laposte.net%3E"
TITLE="[Mageia-dev] Copying dependencies to Updates (Testing), or changing mgaapplet to use urpmi --auto-update instead of urpmi --update.">stormi at laposte.net
</A><BR>
<I>Mon Sep 5 12:06:39 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="007773.html">[Mageia-dev] Copying dependencies to Updates (Testing), or changing mgaapplet to use urpmi --auto-update instead of urpmi --update.
</A></li>
<LI>Next message: <A HREF="007734.html">[Mageia-dev] Status report for Mageia 1 updates, and call for help from you packagers
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7801">[ date ]</a>
<a href="thread.html#7801">[ thread ]</a>
<a href="subject.html#7801">[ subject ]</a>
<a href="author.html#7801">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le samedi 3 septembre 2011 02:20:17, David W. Hodgins a écrit :
><i> On Thu, 01 Sep 2011 06:43:17 -0400, Buchan Milne <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bgmilne at staff.telkomsa.net</A>>
</I>wrote:
><i> > On Thursday, 1 September 2011 12:12:46 Samuel Verschelde wrote:
</I>><i> >> Le jeudi 25 août 2011 11:03:42, David W. Hodgins a écrit :
</I>><i> >> > If the Mandriva way is kept, we must ensure all needed dependencies
</I>><i> >> > are available in Updates (Testing too).
</I>><i> >
</I>><i> > I note that the exception given for Mageia 1 to have packages that were
</I>><i> > in Mandriva, but weren't available at Mageia 1 release be available in
</I>><i> > updates makes this more difficult.
</I>><i>
</I>><i> Agreed. What really makes things worse, is the dependencies of the
</I>><i> dependencies. With kipi-plugins-expoblending, a requires was added for the
</I>><i> package hugin.
</I>><i>
</I>><i> Since hugin was only in Core release, the mgaapplet fails to install it.
</I>><i> So, hugin was copied to pushed to Core Updates Testing, and then to
</I>><i> Core Updates.
</I>><i>
</I>><i> But, mgaapplet still couldn't install the update for
</I>><i> kipi-plugins-expoblending, even though hugin was available, as enblend,
</I>><i> required by hugin, is only in Core Release, so the dependencies
</I>><i> dependencies must copied too.
</I>><i>
</I>><i> Identifying which packages must be copied, is going to be difficult.
</I>><i>
</I>><i> Effectively, everything listed by
</I>><i> urpmq --requires-recursive kipi-plugins-expoblending
</I>><i> minus the packages listed by
</I>><i> urpmq --requires-recursive basesystem-minimal
</I>><i> should be copied.
</I>><i>
</I>><i> $ urpmq --requires-recursive kipi-plugins-expoblending|wc -l
</I>><i> 629
</I>><i> $ urpmq --requires-recursive basesystem-minimal|wc -l
</I>><i> 312
</I>><i>
</I>><i> So 317 packages would have to be copied, to be absolutely safe.
</I>><i>
</I>><i> Regards, Dave Hodgins
</I>
I would check it differently :
- for an update to an existing package in mageia 1 you have to compare the
list of dependencies (recursive) to that of the previous package, not to
basesystem-minimal. This will give less results I guess.
- for a package added to Mageia 1 because it was missing but present in
Mandriva 2010.2, it can be trickier. Problems arise when the mdv package is
still present on mageia (from a previous migration) and MageiaUpdate wants to
update it : it can fail if it requires new dependencies.
One way would be to install it in a minimal Mandriva 2010.2, migrate to Mageia
1 and then either :
- check what dependencies of the package have not been migrated
- or install the updated package with urpmi and note what dependencies have
been pulled from release media
Hopefully urpmi --update's behaviour can be changed soon so that QA Team will
be relieved from those tedious checks ?
Best regards
Samuel
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="007773.html">[Mageia-dev] Copying dependencies to Updates (Testing), or changing mgaapplet to use urpmi --auto-update instead of urpmi --update.
</A></li>
<LI>Next message: <A HREF="007734.html">[Mageia-dev] Status report for Mageia 1 updates, and call for help from you packagers
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7801">[ date ]</a>
<a href="thread.html#7801">[ thread ]</a>
<a href="subject.html#7801">[ subject ]</a>
<a href="author.html#7801">[ 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>
|
