blob: ea9b81cc8bdcb0f1aeab6658db52e5c0ab0872ed (
plain)
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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-sysadm] Needs locking iurt chroot tarballs
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Needs%20locking%20iurt%20chroot%20tarballs&In-Reply-To=%3CCA%2BCX%2BbiA%3DBfSfpxPHW_KMA4EsYSgZZQtN0f3J7gks36SS1rZgw%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="004247.html">
<LINK REL="Next" HREF="004249.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-sysadm] Needs locking iurt chroot tarballs</H1>
<B>Pascal Terjan</B>
<A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Needs%20locking%20iurt%20chroot%20tarballs&In-Reply-To=%3CCA%2BCX%2BbiA%3DBfSfpxPHW_KMA4EsYSgZZQtN0f3J7gks36SS1rZgw%40mail.gmail.com%3E"
TITLE="[Mageia-sysadm] Needs locking iurt chroot tarballs">pterjan at gmail.com
</A><BR>
<I>Tue Feb 28 10:43:07 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="004247.html">[Mageia-sysadm] Needs locking iurt chroot tarballs
</A></li>
<LI>Next message: <A HREF="004249.html">[Mageia-sysadm] Needs locking iurt chroot tarballs
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4248">[ date ]</a>
<a href="thread.html#4248">[ thread ]</a>
<a href="subject.html#4248">[ subject ]</a>
<a href="author.html#4248">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Tue, Feb 28, 2012 at 08:02, Thierry Vignaud
<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">thierry.vignaud at gmail.com</A>> wrote:
><i> Hi
</I>><i>
</I>><i> Yesterday evening, iurt chroot was rebuild due to new rpm.
</I>><i> However some packages failed to build:
</I>><i> <A HREF="http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20120228010948.fwang.valstar.11974/log/botcmd.1330391389.jonund.log">http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20120228010948.fwang.valstar.11974/log/botcmd.1330391389.jonund.log</A>
</I>><i>
</I>><i> D: [iurt_root_command] Running iurt_root_command --untar
</I>><i> /home/iurt/chroot_cauldron.x86_64.tar.gz
</I>><i> /home/iurt/chroot_tmp/iurt/chroot_cauldron...
</I>><i> D: [iurt_root_command] Uncompress tarball
</I>><i> gzip: stdin: unexpected end of file
</I>><i> tar: Unexpected EOF in archive
</I>><i> tar: Unexpected EOF in archive
</I>><i> tar: Error is not recoverable: exiting now
</I>><i> I: [iurt_root_command] ERROR: Uncompress tarball
</I>><i>
</I>><i> There're 2 bugs:
</I>><i> 1) build continues despite the tar failure
</I>><i> 2) we should:
</I>><i> - either lock the chroot tarball when rebuilding it and when unpackagint it
</I>><i>  in order to prevent that to happen again
</I>><i> - ensure chroot tarball is updated atomically (temp tarball + single mv)
</I>
There is supposed to be only one iurt per version-arch on a given
machine at a time, so if two iurt run on the same machine they use
different chroot tarballs
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="004247.html">[Mageia-sysadm] Needs locking iurt chroot tarballs
</A></li>
<LI>Next message: <A HREF="004249.html">[Mageia-sysadm] Needs locking iurt chroot tarballs
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4248">[ date ]</a>
<a href="thread.html#4248">[ thread ]</a>
<a href="subject.html#4248">[ subject ]</a>
<a href="author.html#4248">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
mailing list</a><br>
</body></html>
|
