Date
1 - 5 of 5
RPM issues on CentOS 7.8
|
Steffen Christgau
Hi everyone,
first, I really appreciate the availability of the RPMs for installing DAOS. This really simplifies setting up a working system. I've tried them and, in principle, succeeded to install DAOS. Nevertheless, I haven't configured the system and thus haven't started it yet since there are two minor issues I encountered and which I want to clearify before continuing. I'm using CentOS 7.8.2003, epel-release is already installed and up to date. If I follow the admin guide and then do yum install * after unpacking the rpms I end up with the following conflicts: Transaction check error: file /usr/lib64/libabt.so.0.0.0 conflicts between attempted installs of libabt0-1.0rc1-2.el7.x86_64 and argobots-1.0rc1-5.el7.x86_64 file /usr/include/abt.h conflicts between attempted installs of argobots-devel-1.0rc1-5.el7.x86_64 and libabt-devel-1.0rc1-2.el7.x86_64 file /usr/lib64/libabt.a conflicts between attempted installs of argobots-devel-1.0rc1-5.el7.x86_64 and libabt-devel-1.0rc1-2.el7.x86_64 libabt and argobots provide the same content but different versions with argobots appearing to be more recent than libabt. Thus, I deleted the package for the latter and also libabt-devel since it requires the libabt package. After that I could install the other rpms. Just to be sure: Can the libabt package really be dropped or will it be missed by some component? In addition: Are the developer packages really required to setup a working system? I removed all '*devel*' rpms and did 'install *' which succeeded as well. Looking forward for your responses. Regards, Steffen
|
|
|
|
Kirvan, Scott <scott.kirvan@...>
Steffen,
I'll forward your questions to our packaging expert and have someone get back to you shortly. One thing I noticed is that you are using 7.8 and for the DAOS 1.0 branch we did all of our testing on 7.7. We moved to 7.8 with the 1.1/master branch that is under
development.
Regards, Scott
From: daos@daos.groups.io <daos@daos.groups.io> on behalf of Steffen Christgau <christgau@...>
Sent: Thursday, July 30, 2020 9:10 AM To: daos@daos.groups.io <daos@daos.groups.io> Subject: [daos] RPM issues on CentOS 7.8 Hi everyone,
first, I really appreciate the availability of the RPMs for installing DAOS. This really simplifies setting up a working system. I've tried them and, in principle, succeeded to install DAOS. Nevertheless, I haven't configured the system and thus haven't started it yet since there are two minor issues I encountered and which I want to clearify before continuing. I'm using CentOS 7.8.2003, epel-release is already installed and up to date. If I follow the admin guide and then do yum install * after unpacking the rpms I end up with the following conflicts: Transaction check error: file /usr/lib64/libabt.so.0.0.0 conflicts between attempted installs of libabt0-1.0rc1-2.el7.x86_64 and argobots-1.0rc1-5.el7.x86_64 file /usr/include/abt.h conflicts between attempted installs of argobots-devel-1.0rc1-5.el7.x86_64 and libabt-devel-1.0rc1-2.el7.x86_64 file /usr/lib64/libabt.a conflicts between attempted installs of argobots-devel-1.0rc1-5.el7.x86_64 and libabt-devel-1.0rc1-2.el7.x86_64 libabt and argobots provide the same content but different versions with argobots appearing to be more recent than libabt. Thus, I deleted the package for the latter and also libabt-devel since it requires the libabt package. After that I could install the other rpms. Just to be sure: Can the libabt package really be dropped or will it be missed by some component? In addition: Are the developer packages really required to setup a working system? I removed all '*devel*' rpms and did 'install *' which succeeded as well. Looking forward for your responses. Regards, Steffen
|
|
|
|
Murrell, Brian
On Thu, 2020-07-30 at 17:10 +0200, Steffen Christgau wrote:
Thus, I deleted theYes that is the correct thing to do. The libabt* packages should not be part of the tarball. We have an internal ticket to have this rectified. Just to be sure: Can the libabt package really be dropped or will itIt can be dropped. In addition: Are the developer packages really required to setup aNo. They are only needed if you want to build software with the DAOS library. I removed all '*devel*' rpms and did 'install *' whichThat is fine. FWIW, the tarball actually unpacks a fully functioning "repo-md" repository that can be used with yum/dnf. You simply need to create .repo files per the example in the README and then you can use commands like "yum install daos-client" rather than just installing everything. Looking forward for your responses.Apologies for it being so late. I did actually respond to this last week but I cannot find it. I must have wrote the message and forgot to hit send, or got distracted or some such. Ahh. Just checked and it's stuck in my Outbox. Must have been some kind of error trying to send it. Cheers, b.
|
|
|
|
Steffen Christgau
On 04/08/2020 17.23, Murrell, Brian wrote:
On Thu, 2020-07-30 at 17:10 +0200, Steffen Christgau wrote:Thanks for confirming those points.Thus, I deleted theYes that is the correct thing to do. [...] FWIW, the tarball actually unpacks a fully functioning "repo-md"Yeah, I noticed that. However, the documentation suggested the above steps (https://daos-stack.github.io/admin/installation/#installing-daos-from-rpms). Using the a local repo appears to be more elegant. Maybe the documentation can be updated with regards to that. Regards, Steffen
|
|
|
|
Murrell, Brian
On Fri, 2020-08-07 at 09:52 +0200, Steffen Christgau wrote:
I've opened a ticket to resolve this discrepancy. Thanks for letting us know. Cheers, b.
|
|
|