Red Hat Bugzilla – Bug 479640
Do not conflict with specspo if there is not any reason
Last modified: 2009-12-07 07:02:40 EST
Description of problem:
We have two spacewalk-backend-* packages that conflict with specpo. There seems to have been some problem with specspo in the past but the details are fuzzy.
We should not conflict with specspo, and if having specspo causes us problems, we should get specspo fixed, or run our code with LANG=C, or something to that effect.
Version-Release number of selected component (if applicable):
# rpm -q spacewalk-backend-app spacewalk-backend-xp
Steps to Reproduce:
1. # rpm -q --conflicts spacewalk-backend-app spacewalk-backend-xp
and Spacewalk works.
No conflicts (no conflicts with specspo), specspo installed, and Spacewalk works.
The discussion took place on mailing list: https://www.redhat.com/archives/spacewalk-devel/2009-January/msg00040.html
The Conflict was removed from .spec, in commit d0846e3510b8ca26a15cf499a5921c2326807253.
FAILQA till the issue in BZ 480127 is resolved.
temporary workaround: rpm -e specspo
We seem to have the conflict removed both from Spacewalk and Satellite packages:
[root@xen90 ~]# rpm -q spacewalk-backend-app spacewalk-backend-xp
[root@xen90 ~]# rpm -q --conflicts spacewalk-backend-app spacewalk-backend-xp
[root@sputnik-prod ~]# rpm -q spacewalk-backend-app spacewalk-backend-xp
[root@sputnik-prod ~]# rpm -q --conflicts spacewalk-backend-app spacewalk-backend-xp
As such, moving to VERIFIED.
Spacewalk 0.7 released.