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-May/015941.html | 84 +++++++++++++++++++++++++++++++++ 1 file changed, 84 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-May/015941.html (limited to 'zarb-ml/mageia-dev/2012-May/015941.html') diff --git a/zarb-ml/mageia-dev/2012-May/015941.html b/zarb-ml/mageia-dev/2012-May/015941.html new file mode 100644 index 000000000..41aac1bf6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-May/015941.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] packages pushed to cauldron updates_testing before release + + + + + + + + + +

[Mageia-dev] packages pushed to cauldron updates_testing before release

+ Thomas Backlund + tmb at mageia.org +
+ Tue May 29 19:49:29 CEST 2012 +

+
+ +
29.05.2012 19:48, David Walser skrev:
+> Packagers,
+> 
+> If you pushed a package to updates_testing in Cauldron before Mageia 2 was released, please make sure you re-push it if you want the fix/update included in Mageia 2.  The change should already be in the SVN, so all you need to do is resubmit it to the build system (and file a bug with an advisory and assign it to QA of course).
+> 
+
+Nope.
+
+SVN was branched according on what was tagged and uploaded on mirrors as
+that's the only way to make sure svn updates tree matches release tree,
+meaning no unwanted/unplanned changes get queued in updates tree.
+
+So if yo want to submit anything to updates_testing, you need to commit
+the changes in updates tree and then submit.
+
+--
+Thomas
+
+
+ + + + + + + + + + + + + +
+

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