[Yum-devel] [PATCH] Update from noarch pkg to arch pkg and vice versa. BZ 709225
Zdenek Pavlas
zpavlas at redhat.com
Thu Sep 22 14:00:34 UTC 2011
>> + or self.conf.obsoletes and (
>> + p.arch == 'noarch' # from noarch
>> + or available_pkg.arch == 'noarch' # to noarch
>> + )
> So if available_pkg.arch == 'noarch' we allow anything, right?
Yes, I understand that foo-1.2.noarch should update foo-1.1.arch.
Shouldn't it? Same name, same provides etc.. why not?
> Also I've no idea what the conf.obsoletes test is here for ...
Yes, it's bogus.
> I meant that traditionally to have packages "move arch" we had
> them obsolete older versions of themselves in their specfiles.
Oh, now I see. That shouldn't hurt, but is it necessary?
I feel this somewhat makes 'arch' part of the package name,
so it's no longer an update, but install + uninstall of obsoleted.
One shouldn't expect such things from 'yum update', IMO..
--
Zdenek
More information about the Yum-devel
mailing list