In order to improve logging for tape-operations and to facilitate the current
testing surrounding this bug, the serrno code of ENOMEM has been replaced by
the more specific error ETNOLBLINFOMEM meaning "No memory available for label
information" within the setlabelinfo function.

Fix which requires testing.

  - svcClass was dropped from the MigrationRouting table as unused. Tools have been amended accordingly.
  - MigrationJob has now an originalCopyNb and originalVID in case of repack migrations that allow to identify repacks properly
  - a table MigratedSegment has been added holding information on other existing tape segments for the migrating files. This allows to avoid putting 2 copies on a file on the same tape
  - in general, migrations that can be triggered at recall time (extra copy and repacks) are populated in MigrationJob table from the beginning, in status MIGRATIONJOB_WAITONRECALL. This allows easy triggering of the migrations after the recall and to identify any problematic migration routing before we even recall.

The main gains are :
  - simpler DB schema : StreamToTapeCopy and SvcClass2TapePool have disappeared. TapeCopy is split in to the dedicated RecallJob and MigrationJob. Stream is replaced by MigrationMount that includes all data needed from the Tape table (so the Tape table only used by recall now).
  - simpler concepts : MigrationMounts match with mounts and do not survive them (as Stream did), MigrationRouting table explicitely gives the migration routing. NbDrives has moved to the TapePool
  - less components : migHunter is gone, replaced by the MigrationRouting table and by a DB job that starts the needed mounts
  - better error reporting : migration failures due to bad configuration are reported sunchronously to the user, on file close or even on file opening when possible. e.g. if the combination of svcClass and fileClass given by the the user is not present in the MigrationRouting table, the file opening will fail with message "File recreation canceled since the file cannot be routed to tape". This case used to loop forever in the migration part.

Conflicts:

	castor/db/oracleCommon.sql
	castor/db/oracleSchema.sql
	castor/db/oracleTapeGateway.sql
	castor/tape/tapegateway/daemon/TapeStreamLinkerThread.cpp
	castor/tape/tapegateway/daemon/VmgrTapeGatewayHelper.cpp
	castor/tape/tapegateway/daemon/VmgrTapeGatewayHelper.hpp
	castor/tape/tapegateway/daemon/ora/OraTapeGatewaySvc.cpp
	castor/tape/tapegateway/daemon/ora/OraTapeGatewaySvc.hpp
	codeGeneration/RH.xmi

Conflicts:

	castor/db/oracleCommon.sql

The version is MUCH lighter than the previous one and consists only in a small python script talking to the stager DB.
In particular the repack DB and repack daemon are gone.
The handling of repack at the stager level has also be greatly improved, using bulk APIs and a direct access to the nameserver DB via DB link. The will make the repacking of tapes with > 1M files possible.

Merged v2_1_11Version-TapeBulkProtocols branch into trunk.

Removed probagation of serrno as this appears to be againt CASTOR coding conventions (stop the sarcasm).

Fixed bug in s_recv function where it was not probagating the value of errno to serrno.

Merged branches/bridge_bug_80217 into the trunk.

I have replaced C++ comments in C code with C code comments.

I have moved/changed variable declarations to not bream the ISO C90 rule
against mixed declarations and code.

Fixed compilation of client RPMs and created shortcuts targets in the Makefiles for all executables and libraries.
It involved fixing the installation of client man pages and cleaning the client packages of tape code.
In particular package castor-tape-client has been obsoleted and replace by castor-tape-tools that is not a client package.
Similarly the libcastortape, libcastorrtcopy and libcastorexpert are now part of the castor-lib-tape package rather than the client side castor-lib.

Another iteration of replacement of Kernighan and Ritchie declarations by ansi ones after it was found that the regexp for finding such declarations was not perfect (See bug #69659)

Fixed commit 20383. Some arguments that were removed from the _Cregexp_c function were still given, leading to a core dump

Conflicts:

	ns/Cns_oracle_ifce.pc

Note that this is a noop as the code after precompilation did not change. This has been double checked.

Note that this is a noop as the code after precompilation did not change. This has been double checked.

Replaced all Kernighan and Ritchie function declarations by standard ones. Note that his breaks the rfio code

Note that this change is a noop, as the code after compiler preprocessing does not change. This was actually double checked manually.

Note that this change is a noop, as the code after compiler preprocessing does not change. This was actually double checked manually.

Note that this change is a noop, as the code after compiler preprocessing does not change. This was actually double checked manually.

In particular, dropped all code related to unsupported platforms.
Note that it has been verified that this commit is a noop for the compiled code as the preprocessed code is unchanged (modulo some line numbers).

The recursive behavior is gone and we now use proper Makefile inclusions.
This brings full (and fast) dependency checking across the whole code base.
The output was also improved so that make -s gives something sensible.
At the same time, all constants declared in any Makefile have been grouped back to site.def and many simplifications have been done in the Imakefiles themselves.

bug #68020: RFE: The mighunter should gracefully stop when it encounters an invalid migration-policy or stream-policy function-name

Improved the rather misleading error-message that is logged by the mighunter
when the migrator-policy Python-function does not attach a tape-copy to any
tape-pool.

the InvalidConfiguration exception.

This commit works towards implementing the following RFE:

bug #68020: RFE: The mighunter should gracefully stop when it encounters an invalid migration-policy or stream-policy function-name

addressing the following RFE:

bug #67945: RFE: The mighunter should not start if the migration and stream policy modules are not configured properly

Note that this particular commit updated the manual page for serrno.h to includethe new  constant SEINVALIDCONFIG.

addressing the following RFE:

bug #67945: RFE: The mighunter should not start if the migration and stream policy modules are not configured properly

  - Dependencies are easier to express
  - DEPLIB and LIBS variables are gone
  - flags have been cleanup up to the very minimum
  - -Wextra is enforced (and last remaining warnings fixed)
  - Osuf macro is gone

Another major cleanup of the castor code targetting to drop all warnings due to the -Wextra flag. On the way, many little bugs were fixed (possible core dumps in command lines, wrong or missing checks, ...), code was dropped since unused, files were converted from dos to unix end of line convention, etc, etc ...