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/20101007/000987.html | 86 +++++++++++++++++++++++++++++++++ 1 file changed, 86 insertions(+) create mode 100644 zarb-ml/mageia-dev/20101007/000987.html (limited to 'zarb-ml/mageia-dev/20101007/000987.html') diff --git a/zarb-ml/mageia-dev/20101007/000987.html b/zarb-ml/mageia-dev/20101007/000987.html new file mode 100644 index 000000000..db0c055f0 --- /dev/null +++ b/zarb-ml/mageia-dev/20101007/000987.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] How will be the realese cycle? + + + + + + + + + +

[Mageia-dev] How will be the realese cycle?

+ Oliver Burger + oliver.bgr at googlemail.com +
+ Thu Oct 7 13:55:09 CEST 2010 +

+
+ +
Marc Paré <marc at marcpare.com> schrieb am 2010-10-07
+> I have to say though, that after having browsed through the Mdv2010.1
+> backports by hand, there is a lot, from a user point of view, that would
+> interest users. All of the sexy upgrades to software are there.
+I have been using the backports as regular repos for years now and some 
+(solvable) version conflicts with kernel modules put aside, I never had any 
+problems with them.
+
+> I think it would be nice to keep as long as it didn't cause major
+> problems with the installation. Maybe an option to "roll-back" a
+> software update would be something to consider for users?
+That would be a nice feature for urpmi. But it's only useful in certain 
+borders. Sometimes newer versions are changing things about the configuration 
+in the user's HOME, the older versions can't work with. So there will be 
+problems with some packages if you do a "rollback upgrade".
+
+Oliver
+
+ + + + + + + + + + + + + + + + +
+

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