Created attachment 323260 [details, diff] telepathy-glib-0.19.8.ebuild.diff net-libs/telepathy-qt-0.9.3 and all of net-im/ktp-*-0.5.0 are masked because of >=net-libs/telepathy-glib-0.19.x not yet in the tree. The version bump is almost just a simple rename, only the vala dep needs a bump to 0.16 - diff attached. Builds successfully and kde-telepathy is fine with it.
Note that 0.19.x is considered a development series, according to http://lists.freedesktop.org/archives/telepathy/2012-May/006095.html as it always is with odd minor version number across the whole Telepathy and GNOME stack. Though telepathy is often rather slow in making stable releases when things already depend on it, including whole stable gnome releases.
telepathy-qt 0.9 is also considered dev release per general telepathy developments rules. This is why we generally land these releases in the gnome overlay. Is there any specific reason that makes you want to unmask these dev releases in tree ? As far as I can tell for telepathy-glib and its users, upstream generally backports a good bunch of fixes to stable branch while working with master.
(In reply to comment #2) > telepathy-qt 0.9 is also considered dev release per general telepathy > developments rules. This is why we generally land these releases in the > gnome overlay. Is there any specific reason that makes you want to unmask > these dev releases in tree ? As far as I can tell for telepathy-glib and its > users, upstream generally backports a good bunch of fixes to stable branch > while working with master. What about users that are developers and want to develop against the "unstable" api? (btw the api docs published on tp.d.o is based on the latested tarball of tp-glib)
(In reply to comment #3) > What about users that are developers and want to develop against the > "unstable" api? (btw the api docs published on tp.d.o is based on the > latested tarball of tp-glib) I imagine that such users are technically proficient and could use the ebuild from gnome overlay: http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=tree;f=net-libs/telepathy-glib
Sometimes you make exception, when its in your interest...very fair. + telepathy-glib-0.17.7 (26 Mar 2012) + + 26 Mar 2012; Nirbheek Chauhan <nirbheek@gentoo.org> + +telepathy-glib-0.17.7.ebuild: + Bump, unstable release, used by gnome-shell-3.4
Look, you don't need telepathy-glib-0.19 for telepathy-qt. The telepathy-qt developers already realized that they had made a mistake by making telepathy-glib-0.19 a requirement for 0.9.3, and last month they removed it in telepathy-qt git master: http://cgit.freedesktop.org/telepathy/telepathy-qt/commit/?id=145e58636b130502adf0bd0ad5d5551aae2e2932
(In reply to comment #6) > Look, you don't need telepathy-glib-0.19 for telepathy-qt. The telepathy-qt > developers already realized that they had made a mistake by making > telepathy-glib-0.19 a requirement for 0.9.3, and last month they removed it > in telepathy-qt git master: > > http://cgit.freedesktop.org/telepathy/telepathy-qt/commit/ > ?id=145e58636b130502adf0bd0ad5d5551aae2e2932 Thanks for spotting the patch. + 11 Sep 2012; Johannes Huber <johu@gentoo.org> + +files/telepathy-qt-0.9.3-tp-glib-0.18-tests.patch, telepathy-qt-0.9.3.ebuild: + Make tests working with tp-glib-0.18 by adding upstream patch spotted by + Alexandre Rostovtsev <tetromino@gentoo.org> and usage of virtualx.eclass. I am happy this time.
This can be closed then as nothing in the tree needs this development version, we will add 0.20.x releases in the future of course
