Bug 116298

Summary: RPM dependency problem between cms & content types
Product: [Retired] Red Hat Web Application Framework Reporter: Jon Orris <jorris>
Component: installationAssignee: Dennis Gregorovic <dgregor>
Status: CLOSED RAWHIDE QA Contact: Jon Orris <jorris>
Severity: medium Docs Contact:
Priority: medium    
Version: nightlyCC: ccm-bugs-list
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-03-17 16:56:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jon Orris 2004-02-19 21:01:14 UTC 
Description of problem:
RPM dependencies aren't correct between cms and the content types.


[root@goodeats autobuild]# yum -y install ccm-core ccm-cms
ccm-cms-types-article
Gathering header information file(s) from server(s)
Server: Autobuild
Finding updated packages
Downloading needed headers
Resolving dependencies
....Unable to satisfy dependencies
Package ccm-cms-types-article needs ccm-cms = 6.1.0, this is not
available.

cms will install by itself fine.
[root@goodeats autobuild]# yum -y install ccm-core ccm-cms
Gathering header information file(s) from server(s)
Server: Autobuild
Finding updated packages
Downloading needed headers
Resolving dependencies
Dependencies resolved
I will do the following:
[install: ccm-core 6.1.0.AUTO.40589-4.noarch]
[install: ccm-cms 6.1.0.AUTO.40589-4.noarch]
Getting ccm-core-6.1.0.AUTO.40589-4.noarch.rpm
ccm-core-6.1.0.AUTO.40589 100% |=========================| 8.7 MB    00:01
Getting ccm-cms-6.1.0.AUTO.40589-4.noarch.rpm
ccm-cms-6.1.0.AUTO.40589- 100% |=========================| 1.8 MB    00:00
Running test transaction:
Test transaction complete, Success!
ccm-core 100 % done 1/2
ccm-cms 100 % done 2/2
Installed:  ccm-core 6.1.0.AUTO.40589-4.noarch ccm-cms
6.1.0.AUTO.40589-4.noarch
Transaction(s) Complete
Comment 1 Daniel Berrangé 2004-02-20 10:27:13 UTC 
I believe this is expected & desired behaviour from auto-build RPMs.
Since these are not formal builds, we munge the version number so that
the dependancies will only work with packages from the same run of the
auto-build. So, it looks like you have a previous install of
'ccm-cms-types-article' from an old auto-build run, which can't be
upgraded to work with ccm-cms from the new auto-build run.
Comment 2 Dennis Gregorovic 2004-03-15 08:19:06 UTC 
@41308
Comment 3 Dennis Gregorovic 2005-03-17 16:56:22 UTC 
closing old tickets