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/012437.html | 76 ++++++++++++++++++++++++++++ 1 file changed, 76 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-February/012437.html (limited to 'zarb-ml/mageia-dev/2012-February/012437.html') diff --git a/zarb-ml/mageia-dev/2012-February/012437.html b/zarb-ml/mageia-dev/2012-February/012437.html new file mode 100644 index 000000000..3c22d8429 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-February/012437.html @@ -0,0 +1,76 @@ + + + + [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

+ Kamil Rytarowski + n54 at gmx.com +
+ Wed Feb 29 11:31:55 CET 2012 +

+
+ +
On 29.02.2012 11:26, nicolas vigier wrote:
+> On Wed, 29 Feb 2012, Kamil Rytarowski wrote:
+>
+>> On 29.02.2012 00:10, Olav Vitters 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.
+> That's not a bug, if you are rebuilding the same package on a new mageia
+> release without any change to the spec file, there is no need to bump
+> the release.
+>
+But what will happen if a package will be updated in an old Mageia 
+release? Then it won't be updateable without bumping release for a newer 
+Mga release.
+
+ + + + + + +
+

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