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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-discuss] A possible risk ?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20A%20possible%20risk%20%3F&In-Reply-To=%3Cop.v9dvuloqn7mcit%40hodgins.homeip.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="006456.html">
<LINK REL="Next" HREF="006459.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-discuss] A possible risk ?</H1>
<B>David W. Hodgins</B>
<A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20A%20possible%20risk%20%3F&In-Reply-To=%3Cop.v9dvuloqn7mcit%40hodgins.homeip.net%3E"
TITLE="[Mageia-discuss] A possible risk ?">davidwhodgins at gmail.com
</A><BR>
<I>Thu Feb 9 00:36:11 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="006456.html">[Mageia-discuss] Mageia 2 bootstrap time is 3 times that of Mageia1
</A></li>
<LI>Next message: <A HREF="006459.html">[Mageia-discuss] A possible risk ?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6457">[ date ]</a>
<a href="thread.html#6457">[ thread ]</a>
<a href="subject.html#6457">[ subject ]</a>
<a href="author.html#6457">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Wed, 08 Feb 2012 13:23:58 -0500, nicolas vigier <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">boklm at mars-attacks.org</A>> wrote:
><i> The problem is the bad update, not that it was allowed without root
</I>><i> password. Updates should not hose the system, and that's why there is a
</I>><i> policy on no new versions in update when possible, and qa tests.
</I>
The main problem I've seen with updates breaking a system happens when
there is a large number of updates (such as kde), and the mirror you're
updating from synced in the middle of the main repositories being updated.
I think the best solution would require the primary repositories to have
some sort of a lock, so that they cannot be synced from in the middle of
an update, or better yet, some way to have all updates put into a hidden
directory, until they have all been loaded, and then have a single operation
that puts all of the updates into the active directories without allowing
any downstream mirror to sync while that's happening.
Regards, Dave Hodgins
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006456.html">[Mageia-discuss] Mageia 2 bootstrap time is 3 times that of Mageia1
</A></li>
<LI>Next message: <A HREF="006459.html">[Mageia-discuss] A possible risk ?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6457">[ date ]</a>
<a href="thread.html#6457">[ thread ]</a>
<a href="subject.html#6457">[ subject ]</a>
<a href="author.html#6457">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
mailing list</a><br>
</body></html>
|
