De : Johan Engelen <jbc.engelen@...2592...>
We are currently on rev35 with gtk+ 2.24.10 according to your last commit message.
Exact.
The devlibs r35 readme.txt says gtkmm 2.24.2. Check the revision history *online*
http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs/trunk/view/head:/... says gtkmm 2.22.0
(note that bazaar is... well......). There is no un-commit there. If un-committing does not show up in the history online, we should never do such a bzr (bizarre) action.
Well, yes, maybe I should have reverted the changes by committing a rev. 37. Uncommitting seems to remove all traces of the last commit. I guess we would prefer to have it logged somewhere. And it seems to leave the local checkouts and branches in an unstable status. Could you try "bzr revert"? I'm not sure "bzr update" works as expected after an uncommit.
-- Nicolas