From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-sysadm/2011-September/003948.html | 121 +++++++++++++++++++++++ 1 file changed, 121 insertions(+) create mode 100644 zarb-ml/mageia-sysadm/2011-September/003948.html (limited to 'zarb-ml/mageia-sysadm/2011-September/003948.html') diff --git a/zarb-ml/mageia-sysadm/2011-September/003948.html b/zarb-ml/mageia-sysadm/2011-September/003948.html new file mode 100644 index 000000000..998de818d --- /dev/null +++ b/zarb-ml/mageia-sysadm/2011-September/003948.html @@ -0,0 +1,121 @@ + + + + [Mageia-sysadm] [Mageia-dev] What's wrong with BS? + + + + + + + + + +

[Mageia-sysadm] [Mageia-dev] What's wrong with BS?

+ Michael Scherer + misc at zarb.org +
+ Mon Sep 19 15:16:41 CEST 2011 +

+
+ +
Le lundi 19 septembre 2011 à 14:45 +0200, Michael Scherer a écrit :
+> Le lundi 19 septembre 2011 à 20:29 +0800, Funda Wang a écrit :
+> > http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20110919121040.fwang.valstar.7596/log/botcmd.1316434263.ecosse.log
+> > 
+> > It seems %distro_section is wrongly set?
+> 
+> In a iurt chroot, that's ok. 
+> 
+
+So, the problem should be fixed now.
+
+The root cause is the upgrade of puppet that started sooner than planned
+
+For some reason, puppet 2.7.X was installed on rabbit.mageia.org since
+the main node, valstar, was not upgraded first ( and so rabbit was
+complainging about "post support" ). So I upgraded it after doing a
+quick test on my vm to check if some problem would arise. I am running
+it on my own servers since some time and didn't notice anything ( or
+forgot ), so I went with the upgrade route.
+
+However, just before the BS broke, I noticed that bcd.mageia.org was not
+working anymore, due to a weird apache error. Then the build system
+broke, and the website on valstar too ( like pkgsubmit, etc ), due to
+the same error. Since buildsystem need apache to be running for package
+installation, everything stopped working.
+
+Since a problem never appear alone, the upgrade of puppet also broke our
+svn hook that check puppet syntax, so I had to disable it, and to
+migrate to the new scheme ( which make me wonder why it didn't explode
+on my own servers ).
+
+( and alamut was not broken due to a breakage in postgresql module that
+prevented puppet from doing anything, so a breakage that prevented
+another breakage. It is fixed now I think. )
+
+The error was that before, in a puppet manifest, you could write :
+$foo = "$bar-stuff"
+
+and the content of $foo is $bar , with -stuff in the end
+and now, that the content of bar-stuff variable.
+
+So we have to use ${bar}-stuff.
+
+So in the end, I guess that's my fault from not warning to not do a
+version upgrade of puppet, sorry about that.
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ -- cgit v1.2.1