Confirming that the proposed package for Trusty fixes the issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452326
Title:
[SRU] Wrong input results
To manage notifications about this bug go
Sorry, my above comment was for Utopic, I'm still testing Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452326
Title:
[SRU] Wrong input results
To manage notifications about this bug go
Confirming that the proposed package for Trusty also fixes the issues.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452326
Confirming the proposed package in Trusty fixes the issues as well.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452376
Title:
Confirming the proposed package in Utopic fixes the issues as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452376
Title:
[SRU] Many UX issues fixed upstream
To manage notifications about
The proposed package for Vivid fixes the issues I reported in the
original comment. Thanks Brian!
Could you also push the packages for Trusty and Utopic? :)
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of
Public bug reported:
[Impact]
Ubuntu Trusty, Utopic and Vivid are currently shipping some older
versions of ibus-cangjie, which have some known issues.
Those are fixed in ibus-cangjie 2.4, which is on its way to Wily.
Trusty currently ships ibus-cangjie 2.1, and both Utopic and Vivid have
2.2.
** Description changed:
+ [Impact]
+
Ubuntu Trusty and Utopic are currently shipping some older versions of
libcangjie, which have some known issues.
Those are fixed in libcangjie 1.3, which is already in Vivid.
Trusty currently ships libcangjie 1.0, and Utopic has 1.1.
Moving
Public bug reported:
Ubuntu Trusty and Utopic are currently shipping some older versions of
libcangjie, which have some known issues.
Those are fixed in libcangjie 1.3, which is already in Vivid.
Trusty currently ships libcangjie 1.0, and Utopic has 1.1.
Moving from 1.0 to 1.3 implies no
This bug has been fixed upstream, and the fix is included in our latest
ibus-cangjie release, fresh from this morning. :)
http://blog.fedora-fr.org/bochecha/post/2014/04/New-releases-from-the-
Cangjians
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi, IBus Cangjie upstream here. :-)
For the record, this bug is tracked upstream at:
https://github.com/Cangjians/ibus-cangjie/issues/49
I think we've identified the problem, so we'll issue a fix quickly.
In addition, we were thinking about making a new minor release soon, so
we'll make sure it
Hey Iain,
I'm upstream for these 3 packages, so let me try to help here. :-)
I'm also a Fedora packager, so I do understand your concern about not
pushing something just because it's the latest, but only if it's better
for the users.
In the present case, those x.1 releases are really what
I'm not sure whether I'm looking at this correctly (upstream developer
of ibus-cangjie here, and Fedora packager), but it seems to me that
Anthony correctly added the build requirement on python3-pycangjie:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/ibus-
Note: I'm the upstream developer of IBus Cangjie.
There's not much I can do about the packaging bug (I'm confident Anthony will
fix it as soon as he finds the time :-) ), but for now I added instructions to
work around the problem on the upstream website:
Good catch on the licensing Sebastien.
I'm not a licensing expert either, but it does appear like I had at
least made something of a mess by bundling that file, if not made
something completely illegal.
To avoid any potential issue, I took the easy way out and dropped the bundle
copy of
The above issues have been fixed and Zhengpeng helped to sponsor the
upload.
Anthony, how did you solve the licensing issue with quick-classic.txt?
Can we have your fix sent upstream?
It would have been really better to send your fix upstream first,
instead of just fixing things only for
16 matches
Mail list logo
