Discussion:
[opensuse-m17n] Help needed: packages in openSUSE:Leap:42.2 project
Takashi Iwai
2016-07-01 10:47:06 UTC
Permalink
Hi,

in the openSUSE conference in the last week, we noticed that lots of
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 reading
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 maintaining
42.2 repository in addition to TW and SLE12-* repos. That is, if the
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: opensuse-m17n+***@opensuse.org
To contact the owner, e-mail: opensuse-m17n+***@opensuse.org
Marguerite Su
2016-07-02 09:46:17 UTC
Permalink
Post by Takashi Iwai
* 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 maintaining
42.2 repository in addition to TW and SLE12-* repos. That is, if the
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 be precise, here's a list that needs some love:

VFlib3: SUSE:SLE-12:GA
anthy: openSUSE:Leap:42.1
bdfresize: SUSE:SLE-12:GA
brise: SUSE:SLE-12-SP2:GA
cairo: SUSE:SLE-12-SP2:GA
canna: openSUSE:Leap:42.1
canna-yubin: openSUSE:Leap:42.1
cannadic: openSUSE:Leap:42.1
cedict: openSUSE:Leap:42.1
cedilla: openSUSE:Leap:42.1
chasen: openSUSE:Leap:42.1
check: SUSE:SLE-12-SP2:GA
cmake: SUSE:SLE-12-SP2:GA
cmuclmtk: openSUSE:Leap:42.1
convmv: SUSE:SLE-12:GA
darts: openSUSE:Leap:42.1
ddskk: openSUSE:Leap:42.1
doc-gnu-ko: openSUSE:Leap:42.1
eb: openSUSE:Leap:42.1
eblook: openSUSE:Leap:42.1
eekboard: SUSE:SLE-12:GA
emacs-apel: openSUSE:Leap:42.1
emacs-flim: openSUSE:Leap:42.1
engdic: openSUSE:Leap:42.1
extra-cmake-modules: openSUSE:Leap:42.1:Update
fbterm: openSUSE:Leap:42.1
fcitx: openSUSE:Leap:42.1:Update
fcitx-anthy: openSUSE:Leap:42.1
fcitx-chewing: openSUSE:Leap:42.1
fcitx-cloudpinyin: openSUSE:Leap:42.1
fcitx-configtool: SUSE:SLE-12:GA
fcitx-fbterm: openSUSE:Leap:42.1
fcitx-googlepinyin: openSUSE:Leap:42.1
fcitx-hangul: openSUSE:Leap:42.1
fcitx-kkc: openSUSE:Leap:42.1
fcitx-libpinyin: openSUSE:Leap:42.1
fcitx-m17n: openSUSE:Leap:42.1
fcitx-pylogger: openSUSE:Leap:42.1
fcitx-qt5: openSUSE:Leap:42.1:Update
fcitx-rime: openSUSE:Leap:42.1
fcitx-sayura: openSUSE:Leap:42.1
fcitx-skk: openSUSE:Leap:42.1
fcitx-sunpinyin: SUSE:SLE-12:GA
fcitx-table-extra: openSUSE:Leap:42.1
fcitx-table-other: openSUSE:Leap:42.1
fcitx-ui-light: openSUSE:Leap:42.1
fcitx-unikey: openSUSE:Leap:42.1
fcitx-zhuyin: openSUSE:Leap:42.1
flim-xemacs: openSUSE:Leap:42.1
fondu: openSUSE:Leap:42.1
font-specimen: openSUSE:Leap:42.1
fontconfig: SUSE:SLE-12:GA
fontforge: SUSE:SLE-12:Update
fontpackages: SUSE:SLE-12:Update
fonts-config: SUSE:SLE-12-SP2:GA
fonttools: SUSE:SLE-12:Update
freetype: SUSE:SLE-12:GA
freetype2: SUSE:SLE-12:Update
fribidi: SUSE:SLE-12:GA
ft2demos: subpackage of freetype2
fwnn: openSUSE:Leap:42.1
gbdfed: openSUSE:Leap:42.1
gcin: openSUSE:Leap:42.1
gcin-branding-openSUSE: openSUSE:Leap:42.1
ghostscript-cjk: SUSE:SLE-12:GA
gnugo: openSUSE:Leap:42.1
google-glog: SUSE:SLE-12-SP2:GA
googletest: openSUSE:Leap:42.1
groff: SUSE:SLE-12:GA
groff-full: subpackage of groff
handedict: SUSE:SLE-12:GA
hcode: openSUSE:Leap:42.1
hmconv: openSUSE:Leap:42.1
i18nspector: openSUSE:Leap:42.1
ibus: openSUSE:Leap:42.1:Update
ibus-anthy: SUSE:SLE-12-SP2:GA
ibus-chewing: SUSE:SLE-12-SP2:GA
ibus-googlepinyin: SUSE:SLE-12-SP2:GA
ibus-hangul: SUSE:SLE-12-SP2:GA
ibus-input-pad: SUSE:SLE-12-SP2:GA
ibus-kkc: SUSE:SLE-12-SP2:GA
ibus-libpinyin: SUSE:SLE-12-SP2:GA
ibus-libzhuyin: SUSE:SLE-12-SP2:GA
ibus-m17n: SUSE:SLE-12:GA
ibus-pinyin: SUSE:SLE-12-SP2:GA
ibus-qt: openSUSE:Leap:42.1
ibus-rime: SUSE:SLE-12-SP2:GA
ibus-skk: SUSE:SLE-12-SP2:GA
ibus-sunpinyin: SUSE:SLE-12:GA
ibus-table: SUSE:SLE-12-SP2:GA
ibus-table-chinese: SUSE:SLE-12-SP2:GA
ibus-table-extraphrase: SUSE:SLE-12-SP2:GA
ibus-table-others: SUSE:SLE-12-SP2:GA
ibus-table-zhengma: openSUSE:Leap:42.1
ibus-table-zhuyin: SUSE:SLE-12-SP2:GA
ibus-table-ziranma: SUSE:SLE-12-SP2:GA
ibus-unikey: SUSE:SLE-12:GA
imhangul: SUSE:SLE-12:GA
input-pad: SUSE:SLE-12-SP2:GA
ipadic: openSUSE:Leap:42.1
jfbterm: openSUSE:Leap:42.1
kakasi: openSUSE:Leap:42.1
kanjipad: openSUSE:Leap:42.1
kasumi: openSUSE:Leap:42.1
kcm-fcitx: openSUSE:Leap:42.1
kcm5-fcitx: openSUSE:Leap:42.1:Update
kf5-filesystem: openSUSE:Leap:42.1
kinput2: SUSE:SLE-12:GA
kterm: openSUSE:Leap:42.1
kyotocabinet: SUSE:SLE-12-SP2:GA
lcdf-typetools: openSUSE:Leap:42.1
libchewing: openSUSE:Leap:42.1
libgooglepinyin: SUSE:SLE-12-SP2:GA
libhangul: openSUSE:Leap:42.1
libkkc: SUSE:SLE-12-SP2:GA
libotf: SUSE:SLE-12:GA
libpinyin: SUSE:SLE-12-SP2:GA
librime: SUSE:SLE-12-SP2:GA
libskk: SUSE:SLE-12-SP2:GA
libstroke: SUSE:SLE-12:GA
libuninameslist: SUSE:SLE-12:GA
libxkbcommon: openSUSE:Factory
libzhuyin: SUSE:SLE-12-SP2:GA
lv: SUSE:SLE-12:GA
m17n-db: SUSE:SLE-12:GA
m17n-lib: SUSE:SLE-12:GA
man-pages-zh_CN: openSUSE:Leap:42.1
marisa: SUSE:SLE-12-SP2:GA
mined: openSUSE:Leap:42.1
motif: openSUSE:Leap:42.1
mozc: openSUSE:Leap:42.1
namazu: openSUSE:Leap:42.1
nh2ps: openSUSE:Leap:42.1
nkf: openSUSE:Leap:42.1
opencc: SUSE:SLE-12-SP2:GA
oto: openSUSE:Leap:42.1
perl-File-MMagic: openSUSE:Leap:42.1
perl-Font-FreeType: openSUSE:Factory
perl-Text-CharWidth: SUSE:SLE-12:GA
poedit: openSUSE:Leap:42.1:Update
presage: openSUSE:Leap:42.1
python-utidy: openSUSE:Leap:42.1
pyzy: SUSE:SLE-12-SP2:GA
qemacs: openSUSE:Leap:42.1
qgo: openSUSE:Leap:42.1
rfbplaymacro: openSUSE:Leap:42.1
rfbproxy: openSUSE:Leap:42.1
scim: openSUSE:Factory
scim-anthy: openSUSE:Factory
scim-sunpinyin: openSUSE:Factory
sunpinyin: openSUSE:Leap:42.1
t1utils: SUSE:SLE-12:GA
tamago: openSUSE:Leap:42.1
tamil-gtk2im: openSUSE:Leap:42.1
texlive-cjk-latex-extras: SUSE:SLE-12:GA
tomoe: SUSE:SLE-12:GA
tomoe-gtk: SUSE:SLE-12:GA
translate-toolkit: openSUSE:Leap:42.1
ucm: openSUSE:Leap:42.1
ungifsicle: openSUSE:Leap:42.1
utf8proc: openSUSE:Leap:42.1
virtaal: openSUSE:Leap:42.1
wm-icons: SUSE:SLE-12:GA
wordcut: SUSE:SLE-12:GA
x11-tools: SUSE:SLE-12-SP1:GA
xemacs: openSUSE:Leap:42.1
xemacs-packages: openSUSE:Leap:42.1
xiterm: SUSE:SLE-12:GA
xmanja: openSUSE:Leap:42.1
yaml-cpp: openSUSE:Leap:42.1:Update
yudit: SUSE:SLE-12:GA
zinnia: openSUSE:Leap:42.1
zinnia-tomoe: openSUSE:Leap:42.1

Marguerite
--
To unsubscribe, e-mail: opensuse-m17n+***@opensuse.org
To contact the owner, e-mail: opensuse-m17n+***@opensuse.org
Fuminobu TAKEYAMA
2016-07-04 15:07:43 UTC
Permalink
Hi,

I have already submitted ibus to 42.2 but it was rejected in order to
keep ibus from SLED 12 SP2. If you know important ibus problem resolved
in 1.5.13, please inform me and file a bug report.

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 Factory.


Fuminobu TAKEYAMA (ftake)
Post by Takashi Iwai
Hi,
in the openSUSE conference in the last week, we noticed that lots of
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 reading
% 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.
* 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 maintaining
42.2 repository in addition to TW and SLE12-* repos. That is, if the
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: opensuse-m17n+***@opensuse.org
To contact the owner, e-mail: opensuse-m17n+***@opensuse.org
Takashi Iwai
2016-07-04 15:13:23 UTC
Permalink
On Mon, 04 Jul 2016 17:07:43 +0200,
Post by Fuminobu TAKEYAMA
Hi,
I have already submitted ibus to 42.2 but it was rejected in order to
keep ibus from SLED 12 SP2. If you know important ibus problem resolved
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 <***@suse.de>
about that.
Post by Fuminobu TAKEYAMA
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 Factory.
Great, thanks!


Takashi
Post by Fuminobu TAKEYAMA
Fuminobu TAKEYAMA (ftake)
Post by Takashi Iwai
Hi,
in the openSUSE conference in the last week, we noticed that lots of
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 reading
% 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.
* 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 maintaining
42.2 repository in addition to TW and SLE12-* repos. That is, if the
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: opensuse-m17n+***@opensuse.org
To contact the owner, e-mail: opensuse-m17n+***@opensuse.org
ZhaoQiang
2016-07-05 08:30:06 UTC
Permalink
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.

Best wishes!
Post by Takashi Iwai
On Mon, 04 Jul 2016 17:07:43 +0200,
Post by Fuminobu TAKEYAMA
Hi,
I have already submitted ibus to 42.2 but it was rejected in order to
keep ibus from SLED 12 SP2. If you know important ibus problem resolved
in 1.5.13, please inform me and file a bug report.
In that case, the meta file should be also updated to follow
about that.
Post by Fuminobu TAKEYAMA
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 Factory.
Great, thanks!
Takashi
Post by Fuminobu TAKEYAMA
Fuminobu TAKEYAMA (ftake)
Post by Takashi Iwai
Hi,
in the openSUSE conference in the last week, we noticed that lots of
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 reading
% 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.
* 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 maintaining
42.2 repository in addition to TW and SLE12-* repos. That is, if the
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: opensuse-m17n+***@opensuse.org
To contact the owner, e-mail: opensuse-m17n+***@opensuse.org
Takashi Iwai
2016-07-05 09:19:16 UTC
Permalink
On Tue, 05 Jul 2016 10:30:06 +0200,
Post by ZhaoQiang
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
Post by ZhaoQiang
Best wishes!
Post by Takashi Iwai
On Mon, 04 Jul 2016 17:07:43 +0200,
Post by Fuminobu TAKEYAMA
Hi,
I have already submitted ibus to 42.2 but it was rejected in order to
keep ibus from SLED 12 SP2. If you know important ibus problem resolved
in 1.5.13, please inform me and file a bug report.
In that case, the meta file should be also updated to follow
about that.
Post by Fuminobu TAKEYAMA
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 Factory.
Great, thanks!
Takashi
Post by Fuminobu TAKEYAMA
Fuminobu TAKEYAMA (ftake)
Post by Takashi Iwai
Hi,
in the openSUSE conference in the last week, we noticed that lots of
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 reading
% 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.
* 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 maintaining
42.2 repository in addition to TW and SLE12-* repos. That is, if the
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: opensuse-m17n+***@opensuse.org
To contact the owner, e-mail: opensuse-m17n+***@opensuse.org
ZhaoQiang
2016-07-05 10:02:19 UTC
Permalink
Yes it's clarifies enough.

Thanks!
Post by Takashi Iwai
On Tue, 05 Jul 2016 10:30:06 +0200,
Post by ZhaoQiang
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
Post by ZhaoQiang
Best wishes!
Post by Takashi Iwai
On Mon, 04 Jul 2016 17:07:43 +0200,
Post by Fuminobu TAKEYAMA
Hi,
I have already submitted ibus to 42.2 but it was rejected in order to
keep ibus from SLED 12 SP2. If you know important ibus problem resolved
in 1.5.13, please inform me and file a bug report.
In that case, the meta file should be also updated to follow
about that.
Post by Fuminobu TAKEYAMA
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 Factory.
Great, thanks!
Takashi
Post by Fuminobu TAKEYAMA
Fuminobu TAKEYAMA (ftake)
Post by Takashi Iwai
Hi,
in the openSUSE conference in the last week, we noticed that lots of
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 reading
% 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.
* 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 maintaining
42.2 repository in addition to TW and SLE12-* repos. That is, if the
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: opensuse-m17n+***@opensuse.org
To contact the owner, e-mail: opensuse-m17n+***@opensuse.org
Loading...