New version was release 2014-02-17, ChangeLog: Version 0.3.2: * Fixed a LOT of errors * Removed a LOT of memory leaks * Added Yandex Rich Content API support to URL Preview * Added Yandex.Disk support instead of Yandex.Narod * Added AutoPaster plugin * Added sorting of conference participants by their role * Added ability to tune font settings for roster * Added new icons for mostly everything * Added context search in chat window * Added "Nuvo" chat style * Added "QIPish" chat style * Changed chat tabs' highlighting behaviour
For version 0.3.2 you need to update net-libs/jreen to the latest version or take it from qutim sources. Also, app-crypt/qca and app-crypt/qca-ossl packages are need to be update to latest version like qca-9999 package from rion overlay. net-libs/jreen-1.1.1 and app-crypt/qca-ossl-2.0.0_beta3-r2 aren't compatible with new version
*** Bug 512958 has been marked as a duplicate of this bug. ***
Created attachment 388498 [details, diff] migrate to telepathy-qt-0.9 API.
Created attachment 388500 [details] ebuild for net-im/qutim-0.3.2 The ebuild requires two patches: - Attachment 388386 [details, diff] from bug 506614 - Attachment 388498 [details, diff]
Created attachment 388508 [details] new metadata.xml
Created attachment 389186 [details] ebuild for net-im/qutim-0.3.2 a couple of small fixes to the ebuild
Created attachment 389188 [details] metadata.xml.patch replaced metadata.xml with a patch
(In reply to hamper.nhs from comment #1) > For version 0.3.2 you need to update net-libs/jreen to the latest version or > take it from qutim sources. Also, app-crypt/qca and app-crypt/qca-ossl > packages are need to be update to latest version like qca-9999 package from > rion overlay. > net-libs/jreen-1.1.1 and app-crypt/qca-ossl-2.0.0_beta3-r2 aren't compatible > with new version is this true? if yes, i'd suggest open one bug for each ebuild/package, and block this one (In reply to Fat-Zer from comment #3) > Created attachment 388498 [details, diff] [details, diff] > migrate to telepathy-qt-0.9 API. is this a backport patch from upstream? if no, then always great to ping upstream, get an ACK or work out a better solution few comments on ebuild: ># Copyright 1999-2014 Gentoo Foundation ># Distributed under the terms of the GNU General Public License v2 ># $Header: $ > >EAPI=4 you should check what changed in ebuild 0.3.1-r1 and merge them if possible here we always use the most recent EAPI, current it's 5 > + kde-base/oxygen-icons + is it a DEPEND (build time?) probably only RDEPEND? >PATCHES=( > "${FILESDIR}/0002-Fixed-compilation-with-the-newest-cmake.patch" > "${FILESDIR}/0003-protocol-astral-migrate-to-qt-telepaphy-API-v0.9.patch" >) we prefer to name patches as ${P}-blah-blah.patch.. > $(cmake-utils_use doc QUTIM_GENERATE_DOCS) > kde-base/oxygen-icons > kde-base/oxygen-icons ^^ up, what's this? typo? >pkg_preinst () { it seems to me we are doing this more likely in pkg_postinst()..
(In reply to Yixun Lan from comment #8) > (In reply to hamper.nhs from comment #1) > > For version 0.3.2 you need to update net-libs/jreen to the latest version or > > take it from qutim sources. Also, app-crypt/qca and app-crypt/qca-ossl > > packages are need to be update to latest version like qca-9999 package from > > rion overlay. > > net-libs/jreen-1.1.1 and app-crypt/qca-ossl-2.0.0_beta3-r2 aren't compatible > > with new version > is this true? if yes, i'd suggest open one bug for each ebuild/package, and > block this one That one is mostly outdated. The current stable version of net-libs/jreen is 1.2.0. So, we are ok with it. I'm not sure if it would work with older versions (which are out of portage now) but I'll update the version requirement to be at least 1.2.0 just for sure we are on the safe side. > (In reply to Fat-Zer from comment #3) > > Created attachment 388498 [details, diff] [details, diff] [details, diff] > > migrate to telepathy-qt-0.9 API. > is this a backport patch from upstream? if no, then always great to ping > upstream, get an ACK or work out a better solution > Nope, it's my patch. I've already noticed upstream with a pull request, but got no response yet. > few comments on ebuild: > > ># Copyright 1999-2014 Gentoo Foundation > ># Distributed under the terms of the GNU General Public License v2 > ># $Header: $ > > > >EAPI=4 > you should check what changed in ebuild 0.3.1-r1 and merge them if possible > here we always use the most recent EAPI, current it's 5 ok > > > + kde-base/oxygen-icons > + > is it a DEPEND (build time?) probably only RDEPEND? > yep, my mistake > >PATCHES=( > > "${FILESDIR}/0002-Fixed-compilation-with-the-newest-cmake.patch" > > "${FILESDIR}/0003-protocol-astral-migrate-to-qt-telepaphy-API-v0.9.patch" > >) > we prefer to name patches as ${P}-blah-blah.patch.. > ok... but the first one already pushed to the tree, so I'll keep it as-is. > > $(cmake-utils_use doc QUTIM_GENERATE_DOCS) > > kde-base/oxygen-icons > > kde-base/oxygen-icons > ^^ up, what's this? typo? > yep... thanks for heads up (or whatever people supposed to say in such situations)) > >pkg_preinst () { > it seems to me we are doing this more likely in pkg_postinst().. sure, why not...
Created attachment 389232 [details] ebuild for net-im/qutim-0.3.2
(In reply to Yixun Lan from comment #8) > (In reply to hamper.nhs from comment #1) > > For version 0.3.2 you need to update net-libs/jreen to the latest version or > > take it from qutim sources. Also, app-crypt/qca and app-crypt/qca-ossl > > packages are need to be update to latest version like qca-9999 package from > > rion overlay. > > net-libs/jreen-1.1.1 and app-crypt/qca-ossl-2.0.0_beta3-r2 aren't compatible > > with new version > is this true? if yes, i'd suggest open one bug for each ebuild/package, and > block this one That one is mostly outdated. The current stable version of net-libs/jreen is 1.2.0. So, we are ok with it. I'm not sure if it would work with older versions I've updated the DEPEND to be at least 1.2.0 just for sure we are on the safe side. > (In reply to Fat-Zer from comment #3) > > Created attachment 388498 [details, diff] [details, diff] [details, diff] > > migrate to telepathy-qt-0.9 API. > is this a backport patch from upstream? if no, then always great to ping > upstream, get an ACK or work out a better solution > Nope, it's my patch. I've already noticed upstream with a pull request, but got no response yet. > few comments on ebuild: > > ># Copyright 1999-2014 Gentoo Foundation > ># Distributed under the terms of the GNU General Public License v2 > ># $Header: $ > > > >EAPI=4 > you should check what changed in ebuild 0.3.1-r1 and merge them if possible > here we always use the most recent EAPI, current it's 5 ok > > > + kde-base/oxygen-icons > + > is it a DEPEND (build time?) probably only RDEPEND? > yep, my mistake > >PATCHES=( > > "${FILESDIR}/0002-Fixed-compilation-with-the-newest-cmake.patch" > > "${FILESDIR}/0003-protocol-astral-migrate-to-qt-telepaphy-API-v0.9.patch" > >) > we prefer to name patches as ${P}-blah-blah.patch.. > ok... but the first one (0002) already pushed to the tree, so I'll keep it as-is. > > $(cmake-utils_use doc QUTIM_GENERATE_DOCS) > > kde-base/oxygen-icons > > kde-base/oxygen-icons > ^^ up, what's this? typo? > yep...a typo,,, thanks for heads up (or whatever people supposed to say in such situations)) > >pkg_preinst () { > it seems to me we are doing this more likely in pkg_postinst().. sure, why not...
+*qutim-0.3.2 (14 Nov 2014) + + 14 Nov 2014; Yixun Lan <dlan@gentoo.org> +qutim-0.3.2.ebuild, + +files/qutim-0.3.2-astral-migrate-qt-telepaphy.patch, metadata.xml: + version bump, proxy for fatzer2, bug 501808 I've only renamed the patch to slightly make it shorter, thanks
