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-dev/2012-December/020490.html | 107 +++++++++++++++++++++++++++ 1 file changed, 107 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-December/020490.html (limited to 'zarb-ml/mageia-dev/2012-December/020490.html') diff --git a/zarb-ml/mageia-dev/2012-December/020490.html b/zarb-ml/mageia-dev/2012-December/020490.html new file mode 100644 index 000000000..5ce9007a8 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-December/020490.html @@ -0,0 +1,107 @@ + + + + [Mageia-dev] NOTE: dont upgrade / submit ppl to the bs/mirrors... + + + + + + + + + +

[Mageia-dev] NOTE: dont upgrade / submit ppl to the bs/mirrors...

+ Thomas Backlund + tmb at mageia.org +
+ Sun Dec 2 17:32:25 CET 2012 +

+
+ +
Thomas Backlund skrev 1.12.2012 18:09:
+> Hi,
+>
+> as shown with the recent pcre case, we need to be more verbose on
+> the -dev ml about packages that are WIP and/or known to break bs...
+>
+> I'm in the process of updating ppl from 0.11.2 to 1.0
+> (and cloog-ppl to whatever matching version is)
+>
+> Now, if this package hits the buildsystem & mirrors before it's
+> properly tested it _will_ break atleast gcc, so all builds will
+> come to a full stop in cauldron.
+>
+> So whatever you do... _dont_ touch theese packages until I have
+> tested and submitted them.
+
+
+You can forget about this update ...
+
+I forgot to check what gcc actually supports :/
+
+gcc-4.7 requires ppl-0.11 branch and cloog-ppl-0.15 branch
+
+I've reverted ppl in svn to the state before I started the
+upgrade and updated the warning at top of the spec.
+
+I've also added warning in cloog-ppl spec about the needed
+version match for gcc.
+
+--
+Thomas
+
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

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