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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Missign rebuilds tagged mga1
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Missign%20rebuilds%20tagged%20mga1&In-Reply-To=%3C1545244.lYQ3JackBf%40localhost%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="021628.html">
<LINK REL="Next" HREF="021717.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Missign rebuilds tagged mga1</H1>
<B>AL13N</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Missign%20rebuilds%20tagged%20mga1&In-Reply-To=%3C1545244.lYQ3JackBf%40localhost%3E"
TITLE="[Mageia-dev] Missign rebuilds tagged mga1">alien at rmail.be
</A><BR>
<I>Wed Jan 16 21:22:19 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="021628.html">[Mageia-dev] Missign rebuilds tagged mga1
</A></li>
<LI>Next message: <A HREF="021717.html">[Mageia-dev] Missign rebuilds tagged mga1
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#21711">[ date ]</a>
<a href="thread.html#21711">[ thread ]</a>
<a href="subject.html#21711">[ subject ]</a>
<a href="author.html#21711">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Op dinsdag 15 januari 2013 12:32:27 schreef Johnny A. Solbu:
><i> On Tuesday 15. January 2013 11.43, Colin Guthrie wrote:
</I>><i> > Sounds like one of your media couldn't be updated or something. Not
</I>><i> > directly related to urpmi-proxy per-se but it could certainly confuse
</I>><i> > the issue :)
</I>><i>
</I>><i> Just for good measure, I ran «urpmi.upfdate -a» just now, and the count
</I>><i> didnt change. No media where unable to update, and I only have one repo
</I>><i> configured. (<A HREF="http://ftp-stud.hs-esslingen.de/pub/Mirrors">http://ftp-stud.hs-esslingen.de/pub/Mirrors</A>)
</I>
just mentioning, that the disadvantage to urpmi-proxy, is that it hides
connection errors to repositories, since it will use cache if it fails. you
can look at the logfile if it mentions HIT_AFTER_FAIL (which means it gets you
cache after it failed)
lately, i've been testing with 2 repositories and changing the timeout value
to very low values (5s)
as first repos, i choose one that is fast, and as second repos, i use what is
always up2date. considering MD5SUM would be asked for both repositories (it's
a specially configured file for that), it would get you always up2date results,
since the first would fail to have the file and the second one would be asked
for it.
for me, this gave alot better results especially for cauldron during the mass
rebuild...
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="021628.html">[Mageia-dev] Missign rebuilds tagged mga1
</A></li>
<LI>Next message: <A HREF="021717.html">[Mageia-dev] Missign rebuilds tagged mga1
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#21711">[ date ]</a>
<a href="thread.html#21711">[ thread ]</a>
<a href="subject.html#21711">[ subject ]</a>
<a href="author.html#21711">[ 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>
|
