make Xor32Detector friends with the associated unit test
move T_ChunkDetectors test into upload namespace (friends requirement)
add unit test to check xor32 implementation
specify unsigned-ness for xor32 function
re-define chunking cut marks after portability fix
Merge pull request #304 from reneme/test_xor32

FIX: Portability of XOR32 Implementation To The ARM Platform

The xor32 implementation in the Xor32Detector was taking a char as input parameter. It turns out that the C standard does not define the 'signed-ness' of char leading to unportable code. (x86 interprets char as a signed char whereas ARM takes it as an unsigned char). This fixes this ambiguity by changing the input parameter of xor32 to unsigned char with the expense of a changed behaviour on x86.

Note: This already contains a fix to the directly affected unit tests but it breaks others as well.
update content hashes of generated chunks
FIX: misconfigured FileProcessor
Merge pull request #305 from reneme/fix_file_processing_unit_tests

FIX: FileProcessing Unit Tests

Because the ChunkGenerator implementation and behaviour changed in the previous pull request, we need to adapt the FileProcessing unit tests that build on top of it. Namely it generates different chunks now and we needed to update the expected content hashes lists.

Additionally this fixes a misconfiguration of the FileProcessor template, causing a too coarse-grained file chunking.
cleanup old external versions
Merge branch 'master' of github.com:cvmfs/cvmfs
change symlink default value syntax from := to :-
replace LockGuard and LockGuardAdapter by a more general RAII template
Merge pull request #306 from reneme/replace_lockguard

Replace LockGuard and LockGuardAdapter by a More General RAII Template

It turns out, that my LockGuardAdapter template was broken and relying on undefined behaviour. This totally gets rid of it and replaces the former LockGuard by a more general RAII wrapper class.
expose a magic file while stratum1 snapshotting is running
set locale in cvmfs_server (calls to 'date')
remove the magic file even when a SIGNAL appears
Merge pull request #307 from reneme/snapshotting_magic_file

Expose a Magic File While Stratum1 Snapshotting is Running

This exposes a magic file called .cvmfs_is_snapshotting in the repository root while the snapshot procedure is running. Monitoring tools can use that to show nice spinner-animations while replication is in progress. Initially I put this status information in the mini-REST-API but it would be nice to have this information, even if the stratum 1 administrator decides to not expose the REST-API at all.