Summary: | net-im/psi-0.15 fails with sys-devel/qconf-2.0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kilian <roehner> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | njsg, rion4ik, skrattaren |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
net-im/psi-0.15 build log
qcm-upd.patch |
see also bug 585416 Yes. new qconf is not compatible with old configurations. I think it's better to remove Psi from Gentoo portage together with qconf. Nobody much cares to keep in good condition anyway. I have it in my overlay and keep my ebuilds updated. There is a chance a new Psi version will be based on cmake. Why not just mask =qconf-2.0, or use an unstable keyword for it? Or perhaps just remove =qconf-2.0? That way the older version of qconf and the newest version of psi can be kept as they are. Created attachment 464108 [details, diff]
qcm-upd.patch
There is a patch here which makes newer qconf working with Psi-0.15.
btw If anybody cares... I'm an owner of Psi and Psi+ projects. also qconf, iris and some others. And I'm ready to proxy-maintain them in portage. The most comfortable for me would be if someone periodically merged changes from my overlay. While I don't have 0.15 there, I can add it. my overlay: layman -a rion Thanks a lot, fixed in git commit c61e8ac69f13196253142b90d46346c28c57c67f *** Bug 585416 has been marked as a duplicate of this bug. *** |
Created attachment 461850 [details] net-im/psi-0.15 build log Downgrading to sys-devel/qconf-1.5_pre717-r1 resolves the following issue when installing net-im/psi-0.15: ./configure --prefix=/usr --qtdir=/usr --disable-growl --disable-xss Configuring Psi ... Verifying Qt 4 build environment ... fail Reason: There was an error compiling 'conf'. See conf.log for details. full build log attached.