Hi!
> What does "make check" do after you apply this?
+ exit 0
> Also I'm pretty sure the problem in the BZ doesn't want to trigger on
> exactarch,
I see.. It's probably very different thing. 'exactarch=0' only treats
'compatible' arches (almost) equal, while this BZ is about 'noarch' packages.
This is probably better:
# check to see if the pkg we want to install is not _quite_ the
newest
# one but still technically an update over what is installed.
- pot_updated = self.rpmdb.searchNevra(name=available_pkg.name,
arch=available_pkg.arch)
+ pot_updated = [
+ p for p in self.rpmdb.searchNevra(name=available_pkg.name)
+ if p.arch == available_pkg.arch # exact match
+ or 'noarch' in (p.arch, available_pkg.arch) # arch <=> noarch
+ ]
if pot_updated and self.allowedMultipleInstalls(available_pkg):
# only compare against the newest of what's installed for
kernel
pot_updated = sorted(pot_updated)[-1:]
> and I'm pretty sure there was a reason we didn't just do this before.
> Then again, I'm also pretty sure that what is the "expected" behaviour
> here has changed at least once.
Mmmm.
--
Zdenek
_______________________________________________
Yum-devel mailing list
Yum-devel@lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel
