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/2013-February/022480.html | 93 ++++++++++++++++++++++++++++ 1 file changed, 93 insertions(+) create mode 100644 zarb-ml/mageia-dev/2013-February/022480.html (limited to 'zarb-ml/mageia-dev/2013-February/022480.html') diff --git a/zarb-ml/mageia-dev/2013-February/022480.html b/zarb-ml/mageia-dev/2013-February/022480.html new file mode 100644 index 000000000..c2f2551f7 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-February/022480.html @@ -0,0 +1,93 @@ + + + + [Mageia-dev] Packager's meeting + + + + + + + + + +

[Mageia-dev] Packager's meeting

+ Pascal Terjan + pterjan at gmail.com +
+ Tue Feb 5 12:04:58 CET 2013 +

+
+ +
On Tue, Feb 5, 2013 at 9:03 AM, Anne Nicolas <ennael1 at gmail.com> wrote:
+> Hi there
+>
+> We will have our meeting tonight focused on release critical bugs review.
+> Please have a look before on
+> https://bugs.mageia.org/buglist.cgi?cmdtype=runnamed&namedcmd=release_blocker
+
+I am wondering how to handle packages failing to build, especially the
+ones with different version in svn
+Should I open individual bugs?
+
+I am planning to try building failing packages with -j4 instead of
+-j12 to get a list of the ones which are "really" broken but I don't
+know how to handle the discussion on which ones to drop and which ones
+really need to be fixed
+
+$ ls /distrib/bootstrap/distrib/cauldron/SRPMS/core/release/ | sed -n
+'s/.*mga\([0-9]\).src.rpm/\1/p' | sort | uniq -c
+     34 1
+    119 2
+  10869 3
+
+(for those not familiar with sed, this means 34 packages still have a
+mga1 tag which mean they haven't been rebuilt since Mageia 1 was
+released and 119 have not been rebuilt since Mageia 2 was released)
+
+ + + + + + + + + + + + + + + +
+

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