#328: depcheck: should not test packages from both x86_64 and iX86 unless needed --------------------+------------------------------------------------------- Reporter: tflink | Owner: Type: defect | Status: new Priority: major | Milestone: Hot issues Component: tests | Resolution: Keywords: | --------------------+------------------------------------------------------- Comment (by tflink):
I was digging into this and from what I can tell, yum relies on rpm to tell it what packages have conflicts. With this in mind, I wondered what rpm said about wine-wow.
If I download pacakges for: * [http://kojipkgs.fedoraproject.org/packages/zabbix/1.8.5/1.fc14/x86_64 /zabbix-server-mysql-1.8.5-1.fc14.x86_64.rpm zabbix-server- mysql-1.8.5-1.fc14] * This is a reference since I know yum finds the conflict between this and zabbix-server-sqlite3 * [http://kojipkgs.fedoraproject.org/packages/wine/1.3.19/1.fc14/x86_64 /wine-wow-1.3.19-1.fc14.x86_64.rpm wine-wow-1.3.19-1.fc14]
And run 'rpm --conflicts -qp <rpm file>' (I'm using F14 x86_64) on the packages, I get the following for zabbix-server-mysql: {{{ $ rpm --conflicts -qp zabbix-server-mysql-1.8.5-1.fc14.x86_64.rpm zabbix-server-pgsql zabbix-server-sqlite3 }}}
But when I do the same to wine-wow: {{{ $ rpm --conflicts -qp wine-wow-1.3.19-1.fc14.x86_64.rpm }}}
I get nothing. I would have expected a conflicts on wine-wow
It turns out that the Conflicts is within wine, not wine-wow. So wine.x86_64 conflicts with wine-wow.i686 but there are no issues between the different arches of wine-wow. Running 'yum install wine wine.i686' confirms this.
The only way I can think of for us to work around this is to check for conflicts on all packages and their parents in order to keep from installing conflicting packages. I wonder what would happen if the installation of wine-wow.x86_64 and wine-wow.i386 was allowed to continue since that's pulling in both arches of wine-core.