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/016888.html | 143 +++++++++++++++++++++++++++++++ 1 file changed, 143 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-June/016888.html (limited to 'zarb-ml/mageia-dev/2012-June/016888.html') diff --git a/zarb-ml/mageia-dev/2012-June/016888.html b/zarb-ml/mageia-dev/2012-June/016888.html new file mode 100644 index 000000000..694a12a75 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016888.html @@ -0,0 +1,143 @@ + + + + [Mageia-dev] Backports Summary + + + + + + + + + +

[Mageia-dev] Backports Summary

+ Angelo Naselli + anaselli at linux.it +
+ Wed Jun 27 11:58:39 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+Il 27/06/2012 10:23, Thomas Backlund ha scritto:
+> It's not supposed to be flagged as an update repo as that would
+> make it upgrade all packages it find in the system with matching
+> backports packages.
+Why not? Just let the user to decide, who does want it, just enable it.
+Who wants cherry-peeking it just enable the bp repo and disable it
+after.
+
+The real problem is how to make people understanding that a bp has
+been released as bug or security fixing of an already backported
+package... No problems if you enable bp as updates, while you
+have problems if you cherry-peek a package...
+
+Angelo
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iEYEARECAAYFAk/q2U8ACgkQqEs9DA4DquCFawCdHTQXC0L4cxQCgEo8a1relOyc
+ZEIAnibkaY/4PAlvpHmfsKCyu2LECDzZ
+=pf4G
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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