Description of problem: Not clear why, but yum 3.2.14-10.fc9 on F9 will pull in some i386 java packages when building an x86_64 package that has a BR on java-devel. see the logs in #449526 for an example. failure
The patch in #449056 does _not_ resolve the problem.
Created attachment 307911 [details] root.log
can you recreate the chroot in question and run: yum -d 5 resolvedep java-devel I would like to see some more output from it
]# yum --installroot=$(pwd)/root -d 5 resolvedep java-devel Config time: 0.041 Yum Version: 3.2.14 COMMAND: yum --installroot=/var/lib/mock/fedora-development-x86_64- gridengine/root -d 5 resolvedep java-devel Installroot: /var/lib/mock/fedora-development-x86_64-gridengine/root Ext Commands: java-devel Reading Local RPMDB rpmdb time: 0.000 Setting up Package Sacks pkgsack time: 0.374 Searching pkgSack for dep: java-devel Potential match for java-devel from 1:java-1.6.0-openjdk-devel-1.6.0.0- 0.14.b09.fc10.x86_64 Matched 1:java-1.6.0-openjdk-devel-1.6.0.0-0.14.b09.fc10.x86_64 to require for java-devel Potential match for java-devel from 1:java-1.6.0-openjdk-devel-1.6.0.0- 0.14.b09.fc10.i386 Matched 1:java-1.6.0-openjdk-devel-1.6.0.0-0.14.b09.fc10.i386 to require for java-devel Potential match for java-devel from java-1.5.0-gcj-devel-1.5.0.0-21.fc9.x86_64 Matched java-1.5.0-gcj-devel-1.5.0.0-21.fc9.x86_64 to require for java-devel 0:java-1.5.0-gcj-devel-1.5.0.0-21.fc9.x86_64
Created attachment 308295 [details] yum-install-log.txt yum -d 7 install java-devel
I have tried with yum-3.2.17-2.fc9.noarch (not sure if that is relevant info): # rpm -qa | grep ^java java-1.6.0-openjdk-devel-1.6.0.0-0.16.b09.fc9.x86_64 java-1.6.0-openjdk-1.6.0.0-0.16.b09.fc9.x86_64 java-1.6.0-openjdk-plugin-1.6.0.0-0.16.b09.fc9.x86_64 java-1.5.0-gcj-1.5.0.0-21.fc9.x86_64 java_cup-0.10-0.k.6jpp.2.x86_64 # yum -d 5 resolvedep java-devel --noplugins Config time: 0.162 Yum Version: 3.2.17 COMMAND: yum -d 5 resolvedep java-devel --noplugins Installroot: / Ext Commands: java-devel Reading Local RPMDB rpmdb time: 0.000 Setting up Package Sacks pkgsack time: 0.446 Searching pkgSack for dep: java-devel Potential match for java-devel from 1:java-1.6.0-openjdk- devel-1.6.0.0-0.16.b09.fc9.i386 Matched 1:java-1.6.0-openjdk-devel-1.6.0.0-0.16.b09.fc9.i386 to require for java-devel Potential match for java-devel from 1:java-1.6.0-openjdk- devel-1.6.0.0-0.16.b09.fc9.x86_64 Matched 1:java-1.6.0-openjdk-devel-1.6.0.0-0.16.b09.fc9.x86_64 to require for java-devel Potential match for java-devel from java-1.5.0-gcj-devel-1.5.0.0-21.fc9.x86_64 Matched java-1.5.0-gcj-devel-1.5.0.0-21.fc9.x86_64 to require for java-devel Potential match for java-devel from 1:java-1.6.0-openjdk- devel-1.6.0.0-0.10.b09.fc9.x86_64 Matched 1:java-1.6.0-openjdk-devel-1.6.0.0-0.10.b09.fc9.x86_64 to require for java-devel Potential match for java-devel from 1:java-1.6.0-openjdk- devel-1.6.0.0-0.10.b09.fc9.i386 Matched 1:java-1.6.0-openjdk-devel-1.6.0.0-0.10.b09.fc9.i386 to require for java-devel 0:java-1.5.0-gcj-devel-1.5.0.0-21.fc9.x86_64
I'm not sure, this might be fixed in 3.2.17-2 ... as we fixed a similar looking ppc vs. ppc64 problem. Matt can you try it? It's in updates-testing atm. but is being pushed to stable today.
yes, appears fixed, thanks.