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-August/018361.html | 112 +++++++++++++++++++++++++++++ 1 file changed, 112 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-August/018361.html (limited to 'zarb-ml/mageia-dev/2012-August/018361.html') diff --git a/zarb-ml/mageia-dev/2012-August/018361.html b/zarb-ml/mageia-dev/2012-August/018361.html new file mode 100644 index 000000000..c2c8327b0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018361.html @@ -0,0 +1,112 @@ + + + + [Mageia-dev] Association between SRPMs and bug reports in Mageia App Db + + + + + + + + + +

[Mageia-dev] Association between SRPMs and bug reports in Mageia App Db

+ Samuel Verschelde + stormi at laposte.net +
+ Wed Aug 29 23:35:30 CEST 2012 +

+
+ +
Hi,
+
+In Mageia App Db [1], there was a page that listed all packages from 
+updates_testing media, named "Update candidates" in the menu.
+
+This page now gives for each package the link to its bug report in bugzilla, 
+if it can find one. 
+
+Example: update candidates for Mageia 2, source packages:
+http://mageia.madb.org/rpm/list/listtype/updates_testing/application/0/source/1
+
+When a bug report has been found to match the update candidate, an additional 
+piece of information is added right to it:
+- QA = exact SRPM name match (anywhere in the bug report), bug assigned to QA
+- QA in CC = exact SRPM name match, QA is in CC of the bug (probably waiting 
+for the packager to do something)
+- no QA = exact SRPM match, but QA was not involved (yet?)
+- partial match, QA = partial SRPM name match with the bug report's RPM field, 
+bug assigned to QA
+- partial match, QA in CC = partial SRPM name match with the bug report's RPM 
+field, bug assigned to QA.
+
+RPMs and bug reports are not matched in real time (too much time consuming), 
+but most new links should appear rather quickly though.
+
+It can happen that it takes up to 24 hours for an update candidate to appear 
+in the list, due to Sophie [2] (which Mageia App Db queries) having some 
+difficulties to detect that a new package was added in updates_testing and 
+updates media (it looks like their addition doesn't trigger the right event, 
+so we have to wait for sophie to perform its full scan to see them in the 
+list, which happens once a day IIRC). Olivier Thauvin can probably correct me 
+if I'm wrong.
+
+[1] http://mageia.madb.org
+[2] http://sophie.zarb.org
+
+Best regards
+
+Samuel Verschelde
+
+ + + + + + + + + + + + + + + + + + + + +
+

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