On Wed, Feb 13, 2013 at 3:26 PM, Norbert Preining <prein...@logic.at> wrote: > Hi, > > On Mi, 13 Feb 2013, Aron Xu wrote: >> Here is a relevant commit, though I'm not sure this is the whole story: >> https://github.com/ibus/ibus/commit/53d33ec4e6ad41a116f25cfa7ce12e04f6f93752 > > Seen that, it is huge, not sure reverting it would help. > There are too many code changes there. I have the feeling this > is a catch all commit and not really one commit for one thing. > THat makes revering much harder. > > On Mi, 13 Feb 2013, Ma Xiaojun wrote: >> I believe that it is removed since changing dconf key has no effect either. > > Argh, that is a good point, if chanigng dconf key does not work, > all hope is lost. > > I would propose to re-upload 1.4 with a new epoch to unstable, to > unbreak current sitatuon. > > Or do you see any chance that ibus upstream fixes this? >
Do you think uploading as something like 1.5.1a.is.1.4.2 will work? It's complicated but avoids epoch... We can wait until ibus upstream provides a reasonable release and then continue the versioning. -- Regards, Aron Xu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
