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-June/005796.html | 103 +++++++++++++++++++++++++++++++ 1 file changed, 103 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-June/005796.html (limited to 'zarb-ml/mageia-dev/2011-June/005796.html') diff --git a/zarb-ml/mageia-dev/2011-June/005796.html b/zarb-ml/mageia-dev/2011-June/005796.html new file mode 100644 index 000000000..99927ef95 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005796.html @@ -0,0 +1,103 @@ + + + + [Mageia-dev] Question about backports: calibre (bug 1659) + + + + + + + + + +

[Mageia-dev] Question about backports: calibre (bug 1659)

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Jun 17 11:24:22 CEST 2011 +

+
+ +
On 13 June 2011 11:51, Radu-Cristian FOTESCU <beranger5ca at yahoo.ca> wrote:
+> Therefore, I strongly believe that all calibre updates be packaged into updates, not backports, especially as there isn't any Mageia 2.0 as of yet. Once Mageia 2.0 is released, whatever newer calibre releases will be available might go into backports instead -- if at all. (Although I'd say that it should still be updated to updates for the whole supported time of 1.0.)
+>
+> What do you think?
+
+I think that before thinking of updating or backporting that new version,
+you could start by actually update the package in cauldron so that:
+1) it can be tested...
+2) we're sure we won't have packages in mga1/updates newer that those
+of mga2/release
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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