This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages.
--=_critter.penguinmonster.com-4226-1048515883-0001-2 Content-Type: multipart/alternative; boundary="=-dMRwyWnEu4BIEZPuUSJN" --=-dMRwyWnEu4BIEZPuUSJN Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2003-03-24 at 03:08, -ray wrote: > The rpms are probably broken. I've spent hours and hours trying to > resolve kde.org rpm dependencies in the past, to no avail. They are > circular, cross-linked, and stupid. I've always used this procedure, and > it works ok: uninstall all kde, arts, and qt rpms. Then install qt, > arts, and all kde rpms with --nodeps (and sometimes --replacefiles). If > that doesn't work, then plan B is uninstall everything, then install qt, > arts, and kde rpms from the distribution cd (and updates). Since kde > config is stored in ~/.kde, you shouldn't lose any setup info. That > should at least get you running again. I don't think I understand what you mean by "circular" dependencies. If two rpms depend on each other, install both at once.=20 >=20 > --nodeps isn't always a bad idea, if you know what you're doing. For > instance, the whole XFree86 suite isn't needed if you'll just be tunnelin= g > the display to another X server. Or if i'll only be playing ogg with > xmms, then there's no need for the xmms-mpg123 rpm dependency. Be > forewarned that things might not work perfectly when using --nodeps, but > it probably won't work perfectly anyway (haha), and --nodeps has come in > handy for me more times than not. >=20 > -ray >=20 xmms does not depend on xmms-mpg123. In fact, I'm not even familiar with an xmms-mpg123 rpm, though I've used xmms-mp3 from freshrpms.net. Later versions of Red Hat Linux do not even come with mp3 support, so I'm not sure where that assumption comes from. In my experience, XFree86 can also be installed with just enough rpms to support display exportation without installing the whole thing. If that isn't the case, then there is a bug in the rpms, and you should file a bug report at https://bugzilla.redhat.com/bugzilla (if it's a Red Hat Linux system). I, for one, can say that I do know what I'm doing, and I _never_ break dependencies on a production machine. I just don't see the point of not solving them. --=-dMRwyWnEu4BIEZPuUSJN Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8"> <META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/1.1.8"> </HEAD> <BODY> On Mon, 2003-03-24 at 03:08, -ray wrote: <BLOCKQUOTE TYPE=3DCITE> <PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>The rpms are probably broken. I= 've spent hours and hours trying to resolve kde.org rpm dependencies in the past, to no avail. They are circular, cross-linked, and stupid. I've always used this procedure, and it works ok: uninstall all kde, arts, and qt rpms. Then install qt, arts, and all kde rpms with --nodeps (and sometimes --replacefiles). If that doesn't work, then plan B is uninstall everything, then install qt, arts, and kde rpms from the distribution cd (and updates). Since kde config is stored in ~/.kde, you shouldn't lose any setup info. That should at least get you running again.</I></FONT></PRE> </BLOCKQUOTE> <FONT SIZE=3D"3">I don't think I understand what you mean by "circular= " dependencies. If two rpms depend on each other, install both at once= . <BR> <BR> </FONT><BR> <BLOCKQUOTE TYPE=3DCITE> <PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I> --nodeps isn't always a bad idea, if you know what you're doing. For instance, the whole XFree86 suite isn't needed if you'll just be tunneling the display to another X server. Or if i'll only be playing ogg with xmms, then there's no need for the xmms-mpg123 rpm dependency. Be forewarned that things might not work perfectly when using --nodeps, but it probably won't work perfectly anyway (haha), and --nodeps has come in handy for me more times than not. -ray </I></FONT></PRE> </BLOCKQUOTE> xmms does not depend on xmms-mpg123. In fact, I'm not even familiar with an= xmms-mpg123 rpm, though I've used xmms-mp3 from freshrpms.net. Later versi= ons of Red Hat Linux do not even come with mp3 support, so I'm not sure whe= re that assumption comes from. In my experience, XFree86 can also be = installed with just enough rpms to support display exportation without inst= alling the whole thing. If that isn't the case, then there is a bug in the = rpms, and you should file a bug report at <A HREF=3D"https://bugzilla.redha= t.com/bugzilla">https://bugzilla.redhat.com/bugzilla</A> (if it's a Red Hat= Linux system).<BR> <BR> <BR> I, for one, can say that I do know what I'm doing, and I _never_ break depe= ndencies on a production machine. I just don't see the point of not solving= them. </BODY> </HTML> --=-dMRwyWnEu4BIEZPuUSJN-- --=_critter.penguinmonster.com-4226-1048515883-0001-2 Content-Type: application/pgp-signature; name="signature.asc" Content-Transfer-Encoding: 7bit Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+fxNPtfFnsyEoWxsRAm5uAKCBmJOd/MtZlzulxTbT3+QsFUmWlwCfdYaF CE1WYs+67EHoXH9a2Bp/k70= =mL83 -----END PGP SIGNATURE----- --=_critter.penguinmonster.com-4226-1048515883-0001-2--
