Hide Forgot
Description of problem: The Solaris up2date code uses Provides: for Upgrades: to find packages that should be upgraded. This Provides value should be the "full" version of the package, including the release (revision + PSTAMP, in case of Solaris packages) part. Otherwise the up2date has problem figuring out what exact version the package ... well ... provides. Version-Release number of selected component (if applicable): solaris2mpm 5. How reproducible: Spend a couple of days digging around up2date code and Solaris and Satellite and rhnPackageCapability and solaris2mpm and grepping the whole client SVN directory ... Steps to Reproduce: 1. Have a look at the code. 2. Have a look into rhnPackageCapability after the package was uploaded. Actual results: tools/rhnpush/solaris2mpm.py: def provide_self(header): """Figure out the info needed to put a package into its provides list""" dct = { 'name' : None, 'version' : None, 'flags' : 8, } dct['name'] = header['name'] dct['version'] = header['version'] if not header.has_key('provides'): header['provides'] = [] header['provides'].insert(0, dct) Observe that the 'release' is not used at all. In the database, you will find '1.0'. Expected results: The version should be version concatenated with the release. In the database, we should find things like 1.0-123_PSTAMP_2020.04.12.09.17. Additional info:
Fix committed to Spacewalk master, commit fc99e702084ed4305fba981bf3f2bb9bcf02083d.
Tagged as rhnpush-5.3.0-1. The change is also in rhnpush-0.4.7-1 but we'd really want the > 5.2.0 version here.
Packages rhn-solaris-bootstrap-5.3.0-7.el5sat.noarch.rpm / rhn_solaris_bootstrap_5_3_0_7-1-0.el5sat.noarch.rpm were built, containing RHATrpush-5.3.1-3.pkg.
But the rhnpush package does not contain the fix, in spite of the name.
The rhnpush 5.3.1-5 has the fix (and so has RHATrpush 5.3.1-5). Package rhn_solaris_bootstrap_5_3_0_8-1-0 has that RHATrpush, so moving this bugzilla ON_QA, with composes Satellite-5.3.0-RHEL?-re20090424.1 available.
5.3.0 stage verification: I'm confirming the results from the comment above. RELEASE_PENDING
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1434.html