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

Woah!  Got carried away with const.  This commit Removes the const
qualifier from the ArchiveFileItor::next() method because next()
modifies the iterator.

To loop through an ArchiveFileItor:

  auto itor = catalogue.getArchiveFilesForRepackItor(vid, startFSeq);
  while(itor.hasMore()) {
    const auto archiveFile = itor.next();
    // Do something with archiveFile
  }

Conflicts:
	objectstore/Agent.cpp
	objectstore/RetrieveQueueFailedAlgorithms.cpp
	objectstore/RetrieveQueueToReportAlgorithms.cpp
	objectstore/RetrieveRequest.cpp
	scheduler/OStoreDB/OStoreDB.cpp
	scheduler/OStoreDB/OStoreDB.hpp
	scheduler/OStoreDB/OStoreDBFactory.hpp
	scheduler/OStoreDB/QueueItor.cpp
	scheduler/RetrieveMount.cpp
	scheduler/Scheduler.cpp
	scheduler/SchedulerDatabase.hpp
	xroot_plugins/XrdCtaArchiveFileLs.hpp
	xroot_plugins/XrdCtaListPendingQueue.hpp
	xroot_plugins/XrdCtaTapePoolLs.hpp

It was using vid as container identifier where it should have used
tapepool.

Changed 'catch (cta::exception::Exception ex)' to 'catch (cta::exception::Exception &ex)' in order to avoid error: catching polymorphic type ‘class cta::exception::Exception’

Changed 'catch (cta::exception::Exception ex)' to 'catch (cta::exception::Exception &ex)' in order to avoid error: catching polymorphic type ‘class cta::exception::Exception’ by value

Changed 'catch (exception::Exception ex)' to 'catch (exception::Exception &ex)' in order to avoid error: catching polymorphic type ‘class cta::exception::Exception’ by value