There is new version of uw-imap (http://www.washington.edu/imap/).
The ebuild worksforme when version-bumped to uw-imap-2006d. I tested with ssl on/off and clearpasswd on/off on amd64.
And it continues to workforme for uw-imap-2006-g
BUMP I wonder whether this will reach the tree some day... --------------------- Updated: 31 July 2007 imap-2006j is a maintenance release, consisting primarily of bugfixes to problems discovered in the release that affected a small number of users. http://www.washington.edu/imap/documentation/RELNOTES.html
uw-imap-2007 is out today...
It's necessary to add a new version to the tree. See bug 231258, new version of php require c-clients 2006, bubut uw-imap-2004g (current in tree) prevent c-client to be upgraded!
Why isn't this listed as a php bug instead of a uw-imap bug? After all, php is what changed and broke something.
Both need a fix. uw-imap provides c-client, which has also been made available standalone. PHP requires a more recent version of c-client now (uw-imap is still at 2004g in the tree), but only the standalone c-client was updated and a very specific dependency for that standalone was added to the php ebuild, which leads to an unnecessary blocker. The php ebuild needs to be changed to depend on a virtual so that either uw-imap or c-client can satisfy the dependency, but uw-imap also needs a more recent version added to the tree. If not only for compatibility with php, then also for nearly four years' worth of fixes.
Well, we cannot do much in case of php. The previous way of interaction between c-client and php apparently had a severe security problem which could only be fixed by introducing a patch which makes use of some new c-client features, and as such required the dependency bump. The only way of fixing this is really getting at least 2006g of uw-imap in the tree and change the dependency to the virtual in php again. I'll try to discuss this problem with the uw-imap package maintainors later today.
Would a work-around be possible by unmerging uw-imap, installing c-client, then installing uw-imap, but only the server part, not the client part? Is this even possible?
I don't believe this is possible, no. An install of c-client 2006k will instead block the installation of uw-imap 2004g entirely.
Created attachment 161237 [details] uw-imap ebuild updated to version 2007b
Created attachment 161239 [details] uw-mailutils ebuild updated to version 2007b
Created attachment 161240 [details, diff] patch file needed by uw-mailutils ebuild
I've attached hastily updated ebuilds for uw-imap and uw-mailutils as a test/proof of concept. Very little needed changing aside from renaming the ebuilds. Both emerge and work for me, and additionally allow php to be upgraded and work. Most notably, the uw-imap ebuild needed utf8 and utf8aux added to the c-client doins, as php will not compile with imap support without these headers. The standalone c-client-2006k ebuild installs all headers, including those. I had to add a kludgey PROVIDES entry for net-libs/c-client-2006k to the uw-imap ebuild in order to get around php's own specific dependency kludge on that package. You'll just need to either mask out c-client, or update uw-imap by itself first to avoid a blocker. Also attached the patch file for uw-mailutils-2007b. It's functionally unchanged from the 2004g version.
Thanks a lot, Target. With permission from dertobi123 I just committed uw-{imap,mailutils}-2007b to the tree, with some minor changes to the ebuilds.
