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

Bug#753079: transition: librime



On Tue, Jul 1, 2014 at 8:02 AM, Emilio Pozuelo Monfort <pochu@debian.org> wrote:
>
> On 29/06/14 19:31, Guo Yixuan wrote:
> > Hi,
> >
> > On Sun, Jun 29, 2014 at 3:23 AM, Niels Thykier <niels@thykier.net> wrote:
> >> On 2014-06-29 05:34, Guo Yixuan (郭溢譞) wrote:
> >>> Package: release.debian.org
> >>> Severity: normal
> >>> User: release.debian.org@packages.debian.org
> >>> Usertags: transition
> >>>
> >>> Dear Release Team,
> >>>
> >>> We're planning to upload a new version of librime, which has ABI/API
> >>> breaks. The affected packages are few, and all under IME team's
> >>> maintenance, and we're mostly ready to have sourceful upload for
> >>> these packages:
> >>>
> >>> Source: fcitx-rime
> >>> Source: ibus-rime
> >>>
> >>> Ben file:
> >>>
> >>> [...]
> >>>
> >>>
> >>
> >> Hi,
> >>
> >> Could you please upload the new version of librime to experimental?
> >> This should automatically generate a simple tracker for your (called
> >> auto-librime).
> >>
> >> ~Niels
> >
> > Osamu just helped to upload it (to unstable), so it's now in the new
> > queue. [1]
>
> Please next time upload to experimental when you're asked to do so. In this case
> it's fine, I verified that there are no conflicts with other transitions, so
> there's no need to cancel the upload.

Thank you!

> Why did you rename the -dev package from librime-dev to librime1-dev? Having an
> unversioned -dev package (e.g. librime-dev) is generally preferred. A versioned
> one makes sense when there are two versions of the library simultaneously, but
> that is not the case here.

The renaming is due to a backward-incompatible API change in 
librime 1.0, where some struct members changed types. So I
followed the recommendation here.[1]

[1] https://wiki.debian.org/TransitionBestPractices

Yixuan

Reply to: