Mailinglist Archive: yast-devel (127 mails)

< Previous Next >
Re: [yast-devel] yast2-users not synchronized
On Fri, Nov 13, 2015 at 08:15:25AM +0100, Lukas Ocilka wrote:
Hash: SHA1

On 12.11.2015 17:37, Imobach González Sosa wrote:
Hi all,

I've detected that in yast2-users the SLE-12-GA branch and the IBS
package are not synchronized. According to the repo, the latest
version for SLE 12 (P0) should be[1]. However, in IBS I
found the latest version to be 3.1.37[2].

If I'm right, maybe cherry-picking the needed changes from
SLE-12-SP1 into SLE-12-GA should be enough. Or do you prefer
another approach?

Let's see what can we do about it...

1. This can't change:
so SLE-12-GA branch must contain 3.1.37
- - the latest version that seems to be released is 3.1.35 - but that's
not true, time of this entry needs fixing to match BS
3. The newest package including updates released in SLE-12-GA is here
- - 3.1.37 seems to be the latest released version

Looks like that cherry-picking will solve it.

Anyway, this brings another set of questions: How to prevent from such

I wondered what actually happened there and it seems it was a
mistake done by Leonardo. See
An update for 3.1.35 took so long, by the time it was supposed to be
released, he took 3.1.37 from Devel:Yast:Head(?) even though we had
correct 3.1.35 in Devel:YaST:SLE-12

Had we been vigilant, we would spot this in where it says
that .37 went for SLE 12 GA Updates

Isn't the current workflow too complicated so it confuses
developers? Should we really ask everyone to submit manually to
maintenance OBS from maintenance branches? Would automatic submission
help? Can we at least check that we submit from->to correct location?

No, Yes, No, Um probably not.
Martin Vidner, YaST Team

Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
< Previous Next >