Hi,
I am thinking of ibus transition 1.4 -> 1.5. (Package is already in
experimental)
I think most of this should be done by binnmu as below but there are
some packages which eventually needs source uploads just like ibus-anthy
by converting python bindings via "gi".
* ibus-el
* ibus-googlepinyin
Please note I am still shipping python-ibus so it is OK for now.
There are many packages build depending on libibus-1.0-dev which
requires binnmu.
$ ben query ".build-depends ~ /libibus-1.0-dev/" Sources |egrep -e '^Package:'
Parsing Sources...
Package: ibus-array
Package: ibus-chewing
Package: ibus-client-clutter
Package: ibus-hangul
Package: ibus-input-pad
Package: ibus-libthai
Package: ibus-m17n
Package: ibus-pinyin
Package: ibus-qt
Package: ibus-rime
Package: ibus-skk
Package: ibus-sunpinyin
Package: ibus-table
Package: ibus-unikey
Package: ibus-xkbc
Package: kdeplasma-addons
Package: mlterm
Package: mozc
Since -dev package does not change ABI structure except adding few ABIs,
I am hoping binnmu shall be sufficient.
Am I correct here?
I think I need to follow:
https://wiki.debian.org/Teams/ReleaseTeam/Transitions
If there is any more thing to be aware, let me know.
I also need to get help from you the maintainers if packages are binnmu
safe:
https://wiki.debian.org/binNMU
Are you sure your packages are OK?
Let me know.
Regards,
Osamu
PS: I will make sourceful upload for ibus-anthy 1.5.3-e since it depends
on gir1.2-ibus-1.0 (not in unstable but experimental has ibus-anthy)
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130903153939.GA15585@goofy.localdomain
