Conductor RPM - possible conflict with OS packages...

[patrickatomic]

When installing conductor RPM, some directory are set to be "own" by the conductor RPM where in fact those dirs are already own by some OS packages, such as the filesystem one for instance...

For instance, if you poke the RPM about its content and what its content looks like:

rpm -qlp conductor-v2.4.7-0.el7.x86_64.rpm  |grep -Ex '/opt|/etc' |while read line; do echo "$line is owned by :" $(rpm -qf $line); done
/etc is owned by : filesystem-3.2-21.el7.x86_64 conductor-2.4.17-0.el7.x86_64
/opt is owned by : filesystem-3.2-21.el7.x86_64 conductor-2.4.17-0.el7.x86_64

Basically the content of /etc/ and /opt is marked to by own by 2 packages. where there should only be one owner, not 2. This can lead to some conflicts starting from CentOS 6.8, since the RPM DB has been smarter since Centos6.8. CentOS7 will behave the same. I've seen many cases where yum would just not install it, and the only way of getting rid of that would be to do an "rpm -ivh --force.." which is really not a good practice thing (the --force flag).

I suspect that the SPEC file for those RPMs has been using a wildcards in the %files section like this:

%files
%defattr(-,root,root,-)
/*

Instead of having all the files marked to be owned by the RPM, it would be best to have the content of the subdirs for stuff not already installed by some other packages. So the %files section should look like like:

/opt/conductor/
/opt/conductor/*
/etc/profile.d/conductor.sh
.......

That being said, yum isn't complaining about any conflict on c7 nor c6 for installing conductor, but I just thought I would flag this in case it becomes an issue for someone else eventually.