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

Pascal Terjan pterjan at gmail.com
Wed Feb 29 12:06:46 CET 2012


On Wed, Feb 29, 2012 at 10:40, Oliver Burger <oliver.bgr at googlemail.com> wrote:
> Am 29.02.2012 11:31, schrieb Kamil Rytarowski:
>>
>> 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.
>
> No, because updating is done using subrel
> And e.g. 2.1.mga1 < 2.mga2

Sadly, no, 2.1.mga1 > 2.mga2
But I would expect that an update to a stable release also needs to be
done on newer ones if the package was not changed.


More information about the Mageia-dev mailing list