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-February/012435.html | 75 ++++++++++++++++++++++++++++ 1 file changed, 75 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-February/012435.html (limited to 'zarb-ml/mageia-dev/2012-February/012435.html') diff --git a/zarb-ml/mageia-dev/2012-February/012435.html b/zarb-ml/mageia-dev/2012-February/012435.html new file mode 100644 index 000000000..c870597c7 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-February/012435.html @@ -0,0 +1,75 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release evolution-3.3.90-2.mga2 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release evolution-3.3.90-2.mga2

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Feb 29 09:59:03 CET 2012 +

+
+ +
On 29 February 2012 09:55, Kamil Rytarowski <n54 at gmx.com> wrote:
+>> and no need to mention you're bumping the release; if you didn't, the
+>> buildsystem wouldn't allow you to submit
+>>
+> There is one bug. If you are rebuilding, without bumping the release, when
+> the previous build was for mgaX and the current is for mgaY (where Y>X) then
+> BS is allowing to build.
+> Why this is a bug in my opinion? Because then in case of rebuild for mgaX it
+> is changing into ".%{subrel}%{distsuffix}" and mgaX.1 > mgaY; so it's
+> impossible to update.
+
+You got a point.
+But in that case, every gnome package has seen huge version bump anyway
+since mga1, so it's not an issue in _this_ particular case through it
+would be better if BS would enforce bumping release number whatever
+distsuffix is
+
+ + + + + + +
+

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