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
138
139
140
141
142
143
144
145
146
147
148
149
150
151
|
<!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=%3C2726626.HF8BQzQjrA%40localhost%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="021717.html">
<LINK REL="Next" HREF="021724.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=%3C2726626.HF8BQzQjrA%40localhost%3E"
TITLE="[Mageia-dev] Missign rebuilds tagged mga1">alien at rmail.be
</A><BR>
<I>Wed Jan 16 23:06:18 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="021717.html">[Mageia-dev] Missign rebuilds tagged mga1
</A></li>
<LI>Next message: <A HREF="021724.html">[Mageia-dev] Missign rebuilds tagged mga1
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#21720">[ date ]</a>
<a href="thread.html#21720">[ thread ]</a>
<a href="subject.html#21720">[ subject ]</a>
<a href="author.html#21720">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Op woensdag 16 januari 2013 21:22:22 schreef Colin Guthrie:
><i> 'Twas brillig, and AL13N at 16/01/13 20:22 did gyre and gimble:
</I>><i> > Op dinsdag 15 januari 2013 12:32:27 schreef Johnny A. Solbu:
</I>><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>><i> >
</I>><i> > just mentioning, that the disadvantage to urpmi-proxy, is that it hides
</I>><i> > connection errors to repositories, since it will use cache if it fails.
</I>><i> > you
</I>><i> > can look at the logfile if it mentions HIT_AFTER_FAIL (which means it gets
</I>><i> > you cache after it failed)
</I>><i> >
</I>><i> > lately, i've been testing with 2 repositories and changing the timeout
</I>><i> > value to very low values (5s)
</I>><i> >
</I>><i> > as first repos, i choose one that is fast, and as second repos, i use what
</I>><i> > is always up2date. considering MD5SUM would be asked for both
</I>><i> > repositories (it's a specially configured file for that), it would get
</I>><i> > you always up2date results, since the first would fail to have the file
</I>><i> > and the second one would be asked for it.
</I>><i> >
</I>><i> > for me, this gave alot better results especially for cauldron during the
</I>><i> > mass rebuild...
</I>><i>
</I>><i> Interesting idea. Never thought about using two mirrors in the config.
</I>><i>
</I>><i> I fought with urpmi-proxy today for a while. No matter what I tried,
</I>><i> when downloading a synthesis via the proxy it always ended up too small
</I>><i> and with md5sum failures. Requesting the same file direct from the
</I>><i> mirrors worked every time. I noticed that the file never ended up in the
</I>><i> cache tree, just in the tmp dir. Time wasn't on my side, so I didn't
</I>><i> debug further... one to fight another day.
</I>><i>
</I>><i> (this is with urpmi-proxy-0.3.2-1.mga2 on mga2 FWIW)
</I>><i>
</I>><i>
</I>><i> Col
</I>
so, either a partial file, or out of disk space? better make sure the cache
tree is the same partition as the tmp dir it uses.
in any case, using multiple mirrors isn't supported...
(yet)
i'm just trying them out this way.
i had alot of troubles with cauldron due to mismatches with MD5SUM and the
synthesis files, because the MD5SUM doesn't match the synthesis files
but, sometimes, i do have some oddness in files (i think maybe i need better
error-checking) like if you get a partial result, it doesn't get removed from
cache. so if it does fail, i delete the file from the cache tree for now.
don't forget to do that in all your cascading urpmi-proxy's...
i actually have tested 3 cascading urpmi-proxy's.
in normal usage, i have an urpmi-proxy at my local lan. one at my desktop
itself, and then once i tested urpmi-proxy in a VM on my desktop.
the one on my desktop has an "extra" repository (and changes which ones are
default), and the one on the server has now 2 sources (http mirrors), with
very small timeouts (i may have used 3 or 5 seconds)
since i have an urpmi-proxy at work, my work-laptop had always 2 sources which
i uncommented constantly, but perhaps i should actually set them both, with
very small timeouts... maybe with a 3rd slow one?
/me continues to ponder
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="021717.html">[Mageia-dev] Missign rebuilds tagged mga1
</A></li>
<LI>Next message: <A HREF="021724.html">[Mageia-dev] Missign rebuilds tagged mga1
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#21720">[ date ]</a>
<a href="thread.html#21720">[ thread ]</a>
<a href="subject.html#21720">[ subject ]</a>
<a href="author.html#21720">[ 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>
|
