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

Bug#693468: unblock: ibus-table-chinese/1.4.0.20121008-1



Control: tag -1 + moreinfo

Hi,

(disclaimer: I'm not part of the release team, just trying to help.)

Xiaojun Ma wrote (16 Nov 2012 19:21:51 GMT) :
> Please unblock package ibus-table-chinese version 1.4.0.20121008-1.

This package is not in unstable, so it cannot be unblocked.

> What changed?
> The upstream added some meta-data to text files to enable some new features in recent ibus-table.

I'm afraid enabling new features does not fit the current
freeze policy.

> ibus-table just ignores unknown meta-data some we need to build this package with recent ibus-table.

I'm not sure I understand what you mean here. What is a "recent
ibus-table"?

> There is also some build system change from upstream, which should not bother us at all.

Do you mean they are not used when building the Debian package,
or something else?

> I got large (30M) debdiff by running "debdiff ibus-table-chinese_1.3.5-2.dsc ibus-table-chinese_1.4.0.20121008-1.dsc"
> It seems to be because of that the directory structure of packaging
> is changed.

Unfortunately, changing the directory structure of the packaging is
not something that fits the current freeze policy:
  http://release.debian.org/wheezy/freeze_policy.html
(... and I'm pretty sure it didn't fit even the less restrictive one
that was current at the time when this unblock request was filed.)

> Check the commits in upstream repo and see how little user-visible change is made:
> https://github.com/definite/ibus-table-chinese/commits/master

This is great news, since it will probably ease getting the needed
fixes into Wheezy.

Then, may I suggest you cherry-pick the really needed few user-visible
changes and use these to either propose a package for
testing-proposed-updates, or get them as 1.3.5-3 into sid with minimal
changes, depending on whether the 1.3.4-1 to 1.3.5-2 delta itself
meets the freeze policy?

Cheers,
--
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc


Reply to: