Custom Query (894 matches)

The pkglist.xsd file in 0.9.4pre1 doesn't contain information relevant to the RPMng driver ("Instance", etc.) so repo validations are failing with:

/opt/bcfg2/Pkgmgr/rhas4.4_base.xml:4632: element Instance: Schemas validity error : Element 'Instance': This element is not expected. Expected is ( Ignore ). /opt/bcfg2/Pkgmgr/rhas4.4_base.xml:4636: element Instance: Schemas validity error : Element 'Instance': This element is not expected. Expected is ( Ignore ). /opt/bcfg2/Pkgmgr/rhas4.4_base.xml:4640: element Instance: Schemas validity error : Element 'Instance': This element is not expected. Expected is ( Ignore ). /opt/bcfg2/Pkgmgr/rhas4.4_base.xml:4643: element Instance: Schemas validity error : Element 'Instance': This element is not expected. Expected is ( Ignore ). /opt/bcfg2/Pkgmgr/rhas4.4_base.xml fails to validate

The EVR display during bcfg2's operation has an asterisk ('*') when there is no epoch present. The typical convention is to not display the epoch if it is None, sometimes even if it is 0.

Furthermore rpm does set noepoch=zeroepoch since several years now. The old noepoch < zeroepoch bug is from the promoteepoch ages that did quite a lot of adventurous loops when comparing (absent epoch of an installed file is set the same as one to be installed). It is safe and also required to assume that no epoch is the same as zero epoch.

nstall: cannot create regular file `/var/tmp/bcfg2-0.8.2-1-buildroot/etc/default/bcfg2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.50416 (%install)

I hate to be a promoter of RPM based distros, but I am forced to use them. I would also recommend that on these style of systems that we use /etc/sysconfig/bcfg2 instead of /etc/default/bcfg2 to match the rest of the crap they do wrong :)