Re: Help needed: packages in openSUSE:Leap:42.2 project

Yes it's clarifies enough.

Thanks!

=E5=9C=A8 2016=E5=B9=B407=E6=9C=8805=E6=97=A5 17:19, Takashi Iwai =E5=86=99=
=E9=81=93:
> On Tue, 05 Jul 2016 10:30:06 +0200,
> ZhaoQiang wrote:
>>
>> Takashi,
>>
>> hi,
>>
>> These openSUSE Leap 42.2 M17N package is inherit from SUSE:SLE-12-SP2
>>
>> Currently, Integration and update works have been finished.
>> and M17N related functions is being in test.
>> If continue update, a lot of these works need to do again.
>>
>> Generally, SLE will updated only if this is very very very
>> important(or urgent).
>>
>> So, Maybe we can not make openSUSE Leap 42.2 update at this time point=
.
>> The thing we can change is tumbleweed, I think.
>
> Well, it's slightly out of my point.
>
> openSUSE 42.2 takes some M17N packages from SLE12-SP2, yes.  It's
> fine, and it would help decreasing the maintenance cost for Leap.
> These are listed as SUSE:SLE-12-SP2:GA in that meta list in the
> previous mail.
>
> OTOH, the packages that are listed as openSUSE:Leap:42.1 (and
> openSUSE:Leap:42.1:Update) are the already forked packages, and they
> do *not* follow SLE12-SP2 development at all.  They'll stick with the
> old 42.1 version if you don't do any action now!  They are the ones I
> want people reviewing.
>
> Many of such packages have already newer versions or fixes on TW, and
> they can be put to Leap-42.2 as well.  Then we need the manual
> submissions from TW for them.
>
> Or, if some packages that are listed as 42.1 and should be replaced
> with SLE12-SP2 version back, we have to do it properly, too (at first
> submitting SP2 package, then update the meta list).
>
> Hope that clarifies enough.
>
>
> thanks,
>
> Takashi
>
>>
>> Best wishes!
>>
>>
>> =E5=9C=A8 2016=E5=B9=B407=E6=9C=8804=E6=97=A5 23:13, Takashi Iwai =E5=86=
=99=E9=81=93:
>>> On Mon, 04 Jul 2016 17:07:43 +0200,
>>> Fuminobu TAKEYAMA wrote:
>>>>
>>>> Hi,
>>>>
>>>> I have already submitted ibus to 42.2 but it was rejected in order t=
o
>>>> keep ibus from SLED 12 SP2. If you know important ibus problem resol=
ved
>>>> in 1.5.13, please inform me and file a bug report.
>>>
>>> In that case, the meta file should be also updated to follow
>>> SLE12-SP2.  Please mail to Ludwig Nussel <[email protected]>
>>> about that.
>>>
>>>> I know dual monitor issues resolved recently but I cannot test now
>>>> to see how serious it is.
>>>>
>>>>
>>>> I will submit mozc as soon as the latest package is accepted into Fa=
ctory.
>>>
>>> Great, thanks!
>>>
>>>
>>> Takashi
>>>
>>>>
>>>> Fuminobu TAKEYAMA (ftake)
>>>>
>>>>
>>>> On 2016/07/01 19:47, Takashi Iwai wrote:
>>>>> Hi,
>>>>>
>>>>> in the openSUSE conference in the last week, we noticed that lots o=
f
>>>>> packages for openSUSE Leap 42.2 just inherit from openSUSE Leap 42.=
1,
>>>>> and they won't be updated to Tumbleweed / FACTORY version
>>>>> automatically but kept as is.  This is also seen for many M17N
>>>>> packages.  So here is my post.
>>>>>
>>>>> You can check the origin of the openSUSE Leap 42.2 packages by read=
ing
>>>>> 00Meta/lookup.yml file:
>>>>>    % osc less openSUSE:Leap:42.2/00Meta/lookup.yml
>>>>>
>>>>> It'll show each package and its origin in a list.  For example,
>>>>>
>>>>>    ibus: openSUSE:Leap:42.1:Update
>>>>>    ibus-anthy: SUSE:SLE-12-SP2:GA
>>>>>    ....
>>>>>
>>>>> This indicates that ibus itself is taken from 42.1-update while
>>>>> ibus-anthy (actually all ibus modules and tables) are taken from
>>>>> SLE12-SP2.
>>>>>
>>>>> If anyone has some time, please help the following:
>>>>>
>>>>> * Review which M17N packages should be updated to TW version
>>>>>
>>>>> * Check whether any important package is missing in the list
>>>>>
>>>>> If there is such, you can submit it simply like
>>>>>
>>>>>    % osc sr openSUSE:Factory/xxx openSUSE:Leap:42.2
>>>>>
>>>>> where xxx is the package name.  Of course, this assumes that the TW
>>>>> package can be built cleanly and works with oS 42.2 as is.
>>>>>
>>>>>
>>>>> One additional note: submitting TW version to 42.2 means that we'll
>>>>> fork the package and essentially we'll be responsible for maintaini=
ng
>>>>> 42.2 repository in addition to TW and SLE12-* repos.  That is, if t=
he
>>>>> version is as same as SLE12 (up to -SP2), it'd be likely better to
>>>>> leave SLE12, and let SUSE team maintaining the package.
>>>>>
>>>>>
>>>>> thanks,
>>>>>
>>>>> Takashi
>>>>>
>>>> --
>>>> To unsubscribe, e-mail: [email protected]
>>>> To contact the owner, e-mail: [email protected]
>>>>
>>
--=20
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]