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-June/016516.html | 78 ++++++++++++++++++++++++++++++++ 1 file changed, 78 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-June/016516.html (limited to 'zarb-ml/mageia-dev/2012-June/016516.html') diff --git a/zarb-ml/mageia-dev/2012-June/016516.html b/zarb-ml/mageia-dev/2012-June/016516.html new file mode 100644 index 000000000..0ce75e774 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016516.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] Proposed Feature:Backports_update_applet + + + + + + + + + +

[Mageia-dev] Proposed Feature:Backports_update_applet

+ David W. Hodgins + davidwhodgins at gmail.com +
+ Fri Jun 15 09:29:48 CEST 2012 +

+
+ +
On Fri, 15 Jun 2012 01:07:20 -0400, andre999 <andre999mga at laposte.net> wrote:
+
+
+> If the fact it is a backport is ignored, then every backport would be,
+> by definition, an update.  Even packages newly imported to Mageia.
+
+It depends on whether the user has set the backport repsository
+as an update repository, or not.
+
+> Backports are considered separately because they are much more at risk
+> to not function properly, since they weren't tested with the rest of the
+> release, being added afterwards.  So we have to be much more careful
+
+Thats why qa will be testing backports, to ensure they install cleanly, and
+the main features work.  As a qa member, I will not validate a backport that
+either requires --allow-force, or that doesn't at least run.
+
+Regards, Dave Hodgins
+
+ + + + + + + +
+

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