I'm running amd64 and have rapidsvn installed. On Monday, Oct. 16th 2006 I have issued an emerge --update --deep world that has replaced some svn-related library (I'm sorry but I don't remember the name of it, was it "neon"?). This caused a problem in rapidsvn such that rapidsvn reported at each update or commit:
Error while performing action: PROPFIND request failed on '/svn/FS_HSMM_description'
PROPFIND of '/svn/FS_HSMM_description': SSL negotiation failed: SSL disabled due to library version mismatch (https://<SVN server URL>)
A simple rebuild of rapidsvn (with the same version number) has solved the problem, so I guess it boils down to some linking problems.
Therefore: Is it possible that portage automatically rebuilds rapidsvn to avoid the problem?
No, portage won't rebuild anything automatically. That's what revdep-rebuild is for.
but revdep-rebuild has also not rebuilt rapidsvn. To resolve the problem, I had to start emerge rapidsvn by my own.
Well, then find out what broke it and file a new. The answer to this one is no, portage won't be re-emerging anything automatically, sorry.