The Samba-Bugzilla – Bug 11239
sernet-samba-ctdb fails to install because requires awk package to be installed
Last modified: 2015-05-05 10:04:21 UTC
When attempting to install the sernet-samba-ctdb-4.2.1-16.el6.x86_64.rpm via Yum, it fails to install as it is listing awk as a requirement.
# yum install sernet-samba-ctdb
Loaded plugins: downloadonly, product-id, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Setting up Install Process
--> Running transaction check
---> Package ctdb.x86_64 0:2.5.3-1 will be obsoleted
---> Package sernet-samba-ctdb.x86_64 99:4.2.1-16.el6 will be obsoleting
--> Processing Dependency: awk for package: 99:sernet-samba-ctdb-4.2.1-16.el6.x86_64
--> Finished Dependency Resolution
Error: Package: 99:sernet-samba-ctdb-4.2.1-16.el6.x86_64 (samba4)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
RHEL does not have a an actual package called awk. The awk command is provided by the gawk package on RHEL. Looking at the RPM and the list of dependencies, it does require awk.
# rpm -qpR sernet-samba-ctdb-4.2.1-16.el6.x86_64.rpm
warning: sernet-samba-ctdb-4.2.1-16.el6.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID f4428b1a: NOKEY
The package needs to be updated to have a dependency on the gawk package or /bin/awk.
Who does the sernet samba packaging? Can you assign this defect to the correct person?
Looks like sernet-samba-ctdb package adds dependency of awk instead of gawk.
CTDB standalone packaging correctly defines dependency on gawk (Check ctdb/packaging/RPM/ctdb.spec.in).
(In reply to Amitay Isaacs from comment #1)
I pointed them to this bug report.
Thanks for the heads-up! :-)
(In reply to Karolin Seeger from comment #2)
Just saw that they already addressed this, I think.
Hi, thank you for reporting!
I've fixed that yesterday.
Please use sernet-samba-ctdb-4.2.1-17.
In future you can report bugs in the sernet-samba packages to firstname.lastname@example.org