Comment # 6 on bug 986172 from Lingshan Zhu

(In reply to Roger Zhou from comment #5)
> (In reply to Lee Duncan from comment #4)
> > (In reply to Roger Zhou from comment #3)
> > > It is great to know this bug was fixed in Factory. 
> > > 
> > > However, I would incline to reopen this since openSUSE Leap is not fixed
> > > indeed. Further thinking, it might be worth a discussion with Lee Duncan for
> > > our position in Leap. The question can be:
> > > 
> > > - Whether we incline to be more aggressive to suggest Leap 42.2 Release
> > > Manager to use targetcli 3.0 in Factory, or be more safe and conservative to
> > > stay with targetcli 2.1 the same as SLE?
> > > 
> > > - Also, other than this, in the end of Jun, upstream had moved 3.0 into
> > > github/open-iscsi/targetcli-fb. It makes sense to repackage this instead of
> > > Datera repo. 
> > > 
> > > 
> > > @Lee, What do you think?
> > 
> > Hi Roger:
> > 
> > I am not aware of the goals of Leap 42.2, i.e. whether they want to be
> > conservative, as SLE is, or take chances on new packages as Factory does.
> > 
> > I believe the targetcli-3.0 stuff is a much better version than the 2.1
> > version, and very stable. The targetcli-fb group of packages is fairly new
> > so I'd like to see it get some use in Factory and SLE 12 SP2 before we
> > replace targetcli (and friends). So I suggest adding targetcli-fb and
> > friends to 42.2 as an option, if there is still time. But I think the
> > targetcli there should be updated to 3.0-pre4, as per factory.
> 
> Hi Leeman,
> 
> Great on your feedback for the stable status of targetcli-3.0 stuff. 
> 
> At this moment, I'm not sure how the impact to the related yast modules. How
> the  situation in Thumbleweed? Lingshan, maybe you want to have a look?
> 
> As for Leap 42.2, Alpha 3 just out, Beta 2 will be Sept 20th, two months
> ahead. 
> 
> We don't have time for SLE12 SP2 for sure.
> 
> > 
> > Also, what is the procedure for getting things in Leap? 
> 
> To let Leap Release Manager(ludwig.nussel@suse.de) knows your position on
> the related packages as the role of maintainer in openSUSE. And also the
> public engagement in opensuse-packaging@opensuse.org is good too.
> 
> > I was under the
> > impression we just put updates in Factory and they magically migrated to
> > Leap at some time in the future. I'm guessing now that is incorrect.
> 
> Aha, there are some complexity for Leap ;) Among thousands of Leap packages,
> some are core packages, some are not. The core package has to be from SLE
> code stream. While, there are thousands of user space packages can be from
> openSUSE:Factory code stream directly. In corner case, Leap could maintain
> the code stream on its own. Leap Release team maintains such list.
> 
> More specifically in this case for targetcli-3.0 related packages, we could
> communicate with Leap 42.2 release team to use Factory code stream. Before
> that, targetcli will just follow SLE12 SP2 code stream. Not a magic now, huh
> ;)
> 
> 
> Thanks,
> Roger

Hi Roger,
I think there are no impact to yast target modules, we want to update targetcli
packages, but  yast module is still lio-utils backend now.

Thanks,
Zhu Lingshan