--=-RWpMAEnoW1CMxd5tbjw9
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Tue, 2003-02-25 at 09:38, Tom Diehl wrote:
> On 25 Feb 2003, seth vidal wrote:
>=20
> > I think I just realized what's going on, maybe
> >=20
> > the custom-tag kernel is i686, isn't it?
> >=20
> > so yum is doing the following:
> >=20
> > it's seeing the i686 kernel and the other athlon kernels, it's saying,
> > what's the best you got, name+arch.
> >=20
> > then it's comparing the available pkg of 2.4.18-24.7.x to the -17.7x
> > athlon kernel and saying - look at that the new kernel is newer,
> > ignoring the i686 custom tag.
>=20
> Looks like you might be right. I did not realize that installing a
> different arch would mess with yum. Sorry.
it shouldn't. It's a bug. I've got a test fix.
>=20
> [root@octopus root]# rpm -q --qf "%{name} %{version} %{release} %{arch}\n=
" kernel
> kernel 2.4.18 24.7.x.1.nano.tjc i386
> kernel 2.4.7 10 athlon
> kernel 2.4.18 17.7.x athlon
> kernel 2.4.9 21 athlon
> So does this mean that the answer here is to handle the kernel upgrades
> by hand or do you still consider this a bug?
I've figured out how to fix it - I'll have a tarball shortly.
Thanks for finding this case, it would have bit others eventually.
-sv
--=-RWpMAEnoW1CMxd5tbjw9
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQA+W4DS1Aj3x2mIbMcRAoJYAJ9OOg7woX0rpkQ5mlCx2Is1/VwEFACgmPVq
j1gtOSAHrSs5Jp31hOnwJUY=
=ancK
-----END PGP SIGNATURE-----
--=-RWpMAEnoW1CMxd5tbjw9--
