[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1024540: marked as done (transition: libpinyin)

Your message dated Mon, 28 Nov 2022 16:41:19 +0100
with message-id <0bca0de8-3f51-8ca1-768e-7477b1596d86@debian.org>
and subject line Re: Bug#1024540: transition: libpinyin
has caused the Debian Bug report #1024540,
regarding transition: libpinyin
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1024540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024540
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
X-Debbugs-Cc: debian-input-method@lists.debian.org

Hello Release Team,
libpinyin upstream made a SOVERSION bump from 13 to 15, and the Debian packaging has been changed accordingly in libpinyin 2.7.92-1 in experimental. These are the packages affected by the transition: 

 fcitx-libpinyin
 fcitx5-zhuyin
 ibus-libpinyin
 ibus-libzhuyin
 maliit-keyboard
I have changed the sources as appropriate and successfully test built the packages against the new libpinyin.
As regards maliit-keyboard I plan to ping the maintainer (aka submit a bug) and possibly do an NMU. The other affected packages are maintained by Debian's IME team, and as a team member I plan to upload them myself. 

The autogenerated ben tracker looks as expected:

https://release.debian.org/transitions/html/auto-libpinyin.html

Please consider libpinyin for transition.

--
Cheers,

Gunnar Hjalmarsson

--- End Message ---
--- Begin Message --- 
The transition has completed in testing, so closing.

--- End Message ---
Reply to: