Notices of using Subversion

If you want to use Subversion, for example, updating ports tree, you should pay attention to the following issues:

(1) If your server works behind a proxy, you should modify your Subversion configuration file: 

  1. # cat ~/.subversion/servers
  2. [global]
  3. http-proxy-host = web-proxy.xxxx.com
  4. http-proxy-port = 8080
  5. http-compression = no

Otherwise, you may encounter following errors: 

  1. # svn checkout https://svn.FreeBSD.org/ports/head /usr/ports
  2. Error validating server certificate for 'https://svn.freebsd.org:443':
  3.  - The certificate is not issued by a trusted authority. Use the
  4.    fingerprint to validate the certificate manually!
  5.  - The certificate hostname does not match.
  6. Certificate information:
  7.  - Hostname: FG3K6C3A15800021
  8.  - Valid: from Mar 21 09:15:26 2015 GMT until Mar 21 09:15:26 2025 GMT
  9.  - Issuer: FG3K6C3A15800021, Fortinet Ltd.
  10.  - Fingerprint: 1D:F4:21:20:2F:06:41:45:3F:7A:18:FB:79:F3:BB:30:36:32:22:A3
  11. (R)eject, accept (t)emporarily or accept (p)ermanently? p
  12. svn: E170013: Unable to connect to a repository at URL 'https://svn.freebsd.org/ports/head'
  13. svn: E000054: Error running context: Connection reset by peer

Or: 

  1. # svn checkout https://svn.FreeBSD.org/ports/head /usr/ports
  2. ......
  3. svn: E175002: REPORT request on '/ports/!svn/me' failed

(2) If you meet similar errors like as follows executing svn command: 

  1. svn: E200030: SQLite compiled for 3.11.1, but running with 3.9.2

You should update your SQLite: 

  1. # pkg upgrade sqlite3

References:
Using FreeBSD inside a controlled network – A required HTTP Proxy and No FTP;
How to configure a HTTP proxy for svn.