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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] How broken are RPM dependencies allowed to be?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20broken%20are%20RPM%20dependencies%20allowed%20to%20be%3F&In-Reply-To=%3C20111214092051.GB22114%40coneharvesters.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="010473.html">
<LINK REL="Next" HREF="010439.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] How broken are RPM dependencies allowed to be?</H1>
<B>Dan Fandrich</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20broken%20are%20RPM%20dependencies%20allowed%20to%20be%3F&In-Reply-To=%3C20111214092051.GB22114%40coneharvesters.com%3E"
TITLE="[Mageia-dev] How broken are RPM dependencies allowed to be?">dan at coneharvesters.com
</A><BR>
<I>Wed Dec 14 10:20:57 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="010473.html">[Mageia-dev] How broken are RPM dependencies allowed to be?
</A></li>
<LI>Next message: <A HREF="010439.html">[Mageia-dev] How broken are RPM dependencies allowed to be?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10413">[ date ]</a>
<a href="thread.html#10413">[ thread ]</a>
<a href="subject.html#10413">[ subject ]</a>
<a href="author.html#10413">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Tue, Dec 13, 2011 at 09:04:39PM -0500, Liam R E Quin wrote:
><i> It's really hard to test for dependencies like this, as the person
</I>><i> building the package will have working versions of everything.
</I>
It would be tricky, but entirely possible to be tested automatically.
><i> Worse, in two years' time, perl-base of 5.14.3 will be hopelessly
</I>><i> outdated (we all expect, at least). So it becomes one more thing to
</I>><i> maintain.
</I>
I'm not sure what you mean by this. Are you talking about maintaining
the version numbers in the spec files? I agree that after a few releases
it becomes more and more unlikely that a smooth upgrade could happen at
all, so I would be happy cleaning out the spec files of such versions
after a time.
><i> But it's also a problem worth solving for some of the system-critical
</I>><i> components such as perl, urpmi and drak*. I don't think "wontfix" is a
</I>><i> good answer here.
</I>><i>
</I>><i> My Mandriva Cooker system was unbootable for a while recently because
</I>><i> upgrading udev didn't pull in other required packages; the desktop
</I>><i> wasn't working for similar reasons. You can say, don't stop
</I>><i> mid-upgrade, but a network outage or a power failure can make such
</I>><i> things happen.
</I>
Exactly. That's just the kind of edge case that shows that this isn't merely
a problem with unsupported use cases.
>>><i> Dan
</I></PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="010473.html">[Mageia-dev] How broken are RPM dependencies allowed to be?
</A></li>
<LI>Next message: <A HREF="010439.html">[Mageia-dev] How broken are RPM dependencies allowed to be?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10413">[ date ]</a>
<a href="thread.html#10413">[ thread ]</a>
<a href="subject.html#10413">[ subject ]</a>
<a href="author.html#10413">[ 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>
|
