Hello Elvin
which the difference between the
see Index of /storage-ci/eos/diopside/tag/testing/el-8/x86_64
and
Index of /storage-ci/eos/diopside-depend/el-8/x86_64 (*)
and
see Index of /storage-ci/eos/diopside/tag/testing/el-8s/x86_64
and
Index of /storage-ci/eos/diopside-depend/el-8s/x86_64
looks that el8s has fewer packages (eos-protobuf is not on (*))
thank you in advance
best
e.v.
Hi Emmanouil,
The “el-8” relates to CentOS8 packages - which we no longer maintain, and “el-8s” are CentOS8 Stream which is what we suggest to install.
Cheers,
Elvin
hello Elvin
thank you
I have a small issue with those repos for centos
the eos-server-5.0.13-1.el8.x86_64 depend from eos-xrootd-5.3.4-1.el8.x86_64
but at repository → Index of /storage-ci/eos/diopside-depend/el-8s/x86_64
they is an updated version eos-xrootd-5.4.1-1.el8.x86_64
and cause some issue with yum install or update
2022/03/12-00:24:24 [WARN] synchronisation with upstream produced warnings: Error:
Problem: package eos-server-5.0.13-1.el8.x86_64 requires eos-xrootd = 5.3.4, but none of the providers can be installed
thank you in advance
e.v.
hello Again
I have issue with those rpm
eos-xrootd-5.4.1-1.el8.x86_64
eos-xrootd-0:5.3.100-1.el8.x86_64
where the dependecy of eos-server is stricty on eos-xrootd-5.3.4-1.el8.x86_64
FYI
best
e.v.
Hi Emmanouil,
We normally deal with this by version locking EOS and XRootD packages (make sure yum-plugin-versionlock package is installed):
$ cat /etc/yum/pluginconf.d/versionlock.list
0:eos-archive-5.0.5-1.el7.cern.*
0:eos-client-5.0.5-1.el7.cern.*
0:eos-debuginfo-5.0.5-1.el7.cern.*
0:eos-folly-2019.11.11.00-1.el7.cern.*
0:eos-folly-deps-2019.11.11.00-1.el7.cern.*
0:eos-fuse-5.0.5-1.el7.cern.*
0:eos-fuse-core-5.0.5-1.el7.cern.*
0:eos-ns-inspect-5.0.5-1.el7.cern.*
0:eos-quarkdb-5.0.5-1.el7.cern.*
0:eos-server-5.0.5-1.el7.cern.*
0:eos-srm-5.0.5-1.el7.cern.*
0:eos-test-5.0.5-1.el7.cern.*
0:eos-xrootd-5.3.2-1.el7.cern.*
0:eos-xrootd-debuginfo-5.3.2-1.el7.cern.*
0:quarkdb-0.4.2-1.el7.cern.*
0:quarkdb-debuginfo-0.4.2-1.el7.cern.*
1:python2-xrootd-5.3.2-1.el7.*
1:xrootd-5.3.2-1.el7.*
1:xrootd-client-5.3.2-1.el7.*
1:xrootd-client-devel-5.3.2-1.el7.*
1:xrootd-client-libs-5.3.2-1.el7.*
1:xrootd-debuginfo-5.3.2-1.el7.*
1:xrootd-devel-5.3.2-1.el7.*
1:xrootd-libs-5.3.2-1.el7.*
1:xrootd-private-devel-5.3.2-1.el7.*
1:xrootd-selinux-5.3.2-1.el7.*
1:xrootd-server-5.3.2-1.el7.*
1:xrootd-server-devel-5.3.2-1.el7.*
1:xrootd-server-libs-5.3.2-1.el7.*
1:xrootd-voms-5.3.2-1.el7.*
HTH, cheers,
Cristi
hello Elvin and Cristi
thank you for your reply we are using el-8s without a problem at Ijclab
some of our admins ( on another grif subsite) would like to use rocky-8
but the repo el-8 ( and mostly the depend) appaers broken
you will plan to continue to support the el8 repository for eos ?
thank you in advance
best
e.v.
Hi Emmanouil,
Unfortunately, we don’t plan to support CentOS8 (el8) for the future, and we actually stopped some time ago releasing on that platform - EOL was at end of 2021.
We do provide source rpms for both el-7 and el-8s so if you really want to support Rocky-8 you could think of doing a rebuild from the srpms for that particular OS. Our plans focus on CentOS8 Stream and we’ll soon have a CentOS9 Stream releases.
Cheers,
Elvin
Hi Elvin,
I think there was some confusion is the question asked by Emmanouil (I just sent you an email about it). CentOS 8 is clearly EOL but RHEL8 is not. Some of us had like to deploy EOS on RHEL derivatives (Rocky or Alma) rather than CentOS Stream but it seems the el8s repo cannot be deployed on 8.5. Any good reason for that (it seems a couple of dependencies don’t have the minimum version required)? Is it something that will be fixed?
Cheers,
Michel
Hi Michel,
We plan to add support for RHEL8, so the next releases for EOS 5 will also publish the packages in the el-8 repo. Is actually RHEL8 good enough for you or do you need specific Rocky or Alama builds? I don’t know if they are compatible as we don’t plan to run with el-8, we’ll only use el-8s in production at CERN.
Just fyi we plan to build the packages based on the official RHEL8 container image:
https://hub.docker.com/r/redhat/ubi8
Cheers,
Elvin
Rocky and Alma are built from RHEL8 sources and are just clones, totally identical. So no need for a specific repository. When do you think RHEL8 support will be restored? As we are currently configuring our production EOS instance and one of the GRIF subsite would like to use RHEL8 it has a significant impact on us right now if we want to start with the last version of the RPMs (to avoid a future upgrade during the data migration process).
Cheers,
Michel
Hi Michel,
We are now in the process of rebuilding our dependencies (which are quite a few) for el-8 and bringing the repository up to date. I would expect we should have everything in place in a week or so.
Cheers,
Elvin
Great!
Michel
hello Elvin
I would like to have if we have any news and update about the el-8 new repository for RHEL8?
thank you in advance
best
e.v.
Hi Emmanouil,
We will have a couple of new releases for both branches before the end of the week, that will also contain packages for el-8. Please send me privately an email address where you would like to receive announcements about new releases and I can add it to our distribution list.
Cheers,
Elvin