Brenden Walker <BKWalker <at> drbsystems.com> writes:
> Just thought I'd chime in here as I'm on Gentoo and working fine.
> Just did an emerge --sync and double checked my update status.
> Those are the latest stable packages on x86 and amd64.
> I'm compiled with the following use flags enabled:
> apache2 berkdb dso extras gnome-keyring sasl webdav-neon
Thanks everyone for the help.
Like Branden, I have four other Gentoo ~amd64 boxes with subversion use flag
sasl, and they work fine. This laptop has always worked fine too, until about
Gentoo currently removes .la files, IIUC, after the source compilation stage. I
ran the deprecated tool to find and remove them, just in case. No .la files were
found from any package.
$ sudo lafilefixer --justfixit
/usr/lib64/libsasl2.la already clean, skipping update.
The subversion and cyrus-sasl packages are built with the following use flags.
(-sasl configured just now)
dev-libs/cyrus-sasl-2.1.25 USE="gdbm mysql pam postgres
sqlite ssl -authdaemond -berkdb -java -kerberos -ldapdb
-openldap -sample -srp -static-libs -urandom"
dev-vcs/subversion-1.7.1 USE="apache2 bash-completion nls
perl python webdav-neon
-berkdb -ctypes-python -debug -doc -dso -extras -gnome-keyring
-java -kde -ruby -sasl -vim-syntax -webdav-serf"
I am now able to access svn:// urls, so the local problem is masked, although
not fully understood. I'd like to follow it to the cause so I can file a Gentoo
bug if needed.
Are there any files under etc/ or ~/.subversion that might influence
subversion's protocol to access to svn:// urls? I had previously cleared out
~/.subversion/auth FWIW. I'm grasping for something that might be different on
this machine than the others.
Received on 2011-12-12 21:59:50 CET