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/2011-September/007857.html | 100 ++++++++++++++++++++++++++ 1 file changed, 100 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-September/007857.html (limited to 'zarb-ml/mageia-dev/2011-September/007857.html') diff --git a/zarb-ml/mageia-dev/2011-September/007857.html b/zarb-ml/mageia-dev/2011-September/007857.html new file mode 100644 index 000000000..a504ba86b --- /dev/null +++ b/zarb-ml/mageia-dev/2011-September/007857.html @@ -0,0 +1,100 @@ + + + + [Mageia-dev] Copying dependencies from Release to Updates Testing + + + + + + + + + +

[Mageia-dev] Copying dependencies from Release to Updates Testing

+ Samuel Verschelde + stormi at laposte.net +
+ Thu Sep 8 10:39:47 CEST 2011 +

+
+ +
Hi,
+
+During yesterday's packager meeting, it was agreed that the sysadmins will 
+provide a tool allowing packagers to copy packages from Release media to 
+Updates Testing media.
+
+QA Team should be able soon to ask the packagers to provide needed 
+dependencies in Updates Testing so that updates are not blocked by 
+https://bugs.mageia.org/show_bug.cgi?id=2317
+
+Then those dependencies will have to be moved from Updates Testing to Updates, 
+like the other packages submitted by the packagers for the update.
+
+Could someone complete the update procedure wiki page with detailed 
+instructions for packagers to follow, regarding how to identify dependencies 
+that need to be copied to Updates Testing along with an update candidate ?
+
+Until that tool is made available, we can list the needed dependencies in the 
+bug report and ask the sysadmins to move them directly.
+
+Best regards
+
+Samuel Verschelde
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+

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