when i emerge subversion with ssl support, i ve no ssl support in svn --version also, check out a https doesent work... i ve corrected the problem in reemerging neon (wich was already installed) Reproducible: Always Steps to Reproduce: 1. 2. 3.
birdy root # genlop -i neon * net-misc/neon Total builds: 2 Info about currently installed ebuild: * net-misc/neon-0.24.7 Install date: Thu Mar 24 23:56:07 2005 USE="ssl zlib expat" CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer" birdy root # birdy root # genlop -i subversion * dev-util/subversion Info about currently installed ebuild: * dev-util/subversion-1.1.3 Install date: Fri Mar 25 00:00:48 2005 USE="ssl apache2 berkdb python perl java nls -emacs" CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer" birdy root # the first time i installed neon as a dependency, dont know how it was installed ...
Indeed for ssl support subversion needs a neon library version with ssl support. Unfortunately we don't have useflag dependencies yet, so I cannot state it in the dependency.
I don't know if it is a related problem but: In ~amd64 In every --deep --newuse --update world . emerge asks for neon 0.25.3 update. But the current subversion wants 0.24.7. So the update finishes and subversion doesn't work anymore. If I do again a --deep --newuse --update world emerge wants again to downgrade to 0.24.7.. After the emerge subversion works again... But in the next --update--deep --newuse again the 0.25.3 is being asked.... and so on... and so on... to infinitity ...
No, that's unrelated, but probably caused by neon being in your world file. Let it be short, current subversion does not work with the newer neon library as it breaks compatibility. I can't fix the useflag problem either
