Fixed.

Moreover, the PL/SQL code for the CTA catalogue is temporarily
moved out of the catalogue folder as it requires some schema
changes that are still work in progress in a dev branch. Until
then, all migration code is evolved in the migration/ folder.

References:
https://gitlab.cern.ch/cta/CTA/issues/479 (on the CTA side)
Jira: CASTOR-5526: support the migration to CTA (on the CASTOR side)

The latter won't be updated further, all required code will
be committed here and gitlab tickets will be updated accordingly.

Fixes race condition: for text stream responses, guarantees that
header is printed before the stream data.

Upgrading to eos 4.4.32 that brings some [SSD scrubbing fixes](https://its.cern.ch/jira/browse/EOS-3349) for the new pps and xrdfs query backup bit on eos.

Someone added xrootd in eos-citrine-depend repo which had a priority of 2. Lowering this one as people are messing with it.

repositories.

basically requiring xrootd-4.8-3 and not our 4.9.0 this is an externally
triggered problem. To fix this we can either disable protectbase yum
plugin for all our yum commands, remove the plugin, sed -i
's/protect=1/protect=0/' /etc/yum.repos.d/* in all our containers OR
enable baseprotect on our repos...
I enabled baseprotect on all our repos.

Upgraded to EOS 4.4.25-20190301013418git43576ce in order to get Elvin's new FST communication configuration where we can set the number of connections used by the FST to send commit messages to the MGM

This commit works towards issue cta/CTA#436.

This commit works towards issue cta/CTA#436.

Adding logrotate as eos tends to generate plenty of logs and eos-server does not depend on logrotate. This helps a lot for long stress tests.

Upgraded to EOS 4.4.25-20190220154847git43a58c0 in order to get the new logs of the WFE::Job::SendProtoWFRequest() method

Upgraded to eos version4.4.25-20190208164812gite195333 in order to test simplifications of eos::mgm::TapeAwareGc

We are supposed to stick in the loop for 30 seconds until nothing more comes out, but
this only worked for retrieves (archive reports failed to loop).

the kubernetes CI namespace and externally.
More in README_postgres.md

CatalogueTest now asserts new archive file identifiers are unique as opposed to strictly incrementing sequentially by 1