-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue October 3 2006 12:10, jalal wrote:
On 03/10/06, Lennart Börjeson <Lennart.Borjeson@cinnober.com> wrote:
I have really no idea (havn't had any problems with smart myself), but perhaps the suggestions in this thread work for you, too?
http://www.linuxquestions.org/questions/showthread.php?t=485558
No, not really. The problem is simply that the packagers are not putting the correct paths in the smart metadata. Packages are being made for 10.1 and the meta files are being copied over as-is for the 10.0 branch. Which doesn't work... :(
Smart itself works fine.
This would explain why my rpm sys is broken and why I get the following when trying to use the rpm sys: ....L... /usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre/lib/rt.jar error: rpmdbNextIterator: skipping h# 2116 Header V3 DSA signature: BAD, key ID ddaf6454 error: rpmdbNextIterator: skipping h# 2118 Header V3 DSA signature: BAD, key ID ddaf6454 Unsatisfied dependencies for kdebluetooth-0.0.svn20060413-24.1: libopenobex.so.1 S.5....T c /etc/services ....L... /usr/X11R6/bin/X error: rpmdbNextIterator: skipping h# 2132 Header V3 DSA signature: BAD, key ID ddaf6454 error: rpmdbNextIterator: skipping h# 2140 Header V3 DSA signature: BAD, key ID ddaf6454 error: rpmdbNextIterator: skipping h# 2148 Header V3 DSA signature: BAD, key ID ddaf6454 error: rpmdbNextIterator: skipping h# 2156 Header V3 DSA signature: BAD, key ID ddaf6454 (I think the offending package was the openobex [v 1.02.x I believe] and it has been removed - let's see if it helps) And... "error: rpmdbNextIterator: skipping h# 2116 Header V3 DSA signature: BAD, key ID ddaf6454" is what I get anytime I try to install or remove a package - the above messages were produced by the -Va flag for rpm (-V = verify, a = all). I have to remove the offending package (which takes a bit of research to figure out which one it is), then I have to run the "-Va" flag in rpm and then the "--rebuilddb" and hope it gets fixed. This is why I am getting to the point of wondering if continuing to use SuSE is worth the effort. I am taking a programming class and haven't got time to babysit my sys. This was fine when I was on the beta team (way back when) but I need a production machine more than a test platform. I realize that OpenSuSE releases are similar to fedora in concept (aka bleeding edge). But after using SuSE for sometime (since 7.x) I am at a point where it may be the reality that the SuSE I used to use is no longer the SuSE of today - what can I say but "Thanx Novell"? So, the new packaging distribution schema that Novell has mandated bites bigtime and I either wait to see if Novell can let the devs to fix this mess or if the suits write check with their mouths that the dev can't promise to keep! (as is often the case) I know that the suits at Novell don't read much from this list, but the devs do and perhaps they might forward this and similar messages to the appropriate exec (provided he/she understand as much about computing as he/she does about market share and revenue streams). I'm trying to give Novell the benefit of the doubt (mainly because I trust and know the devs), but it's getting to the point where I'm about ready to burn that ISO of CentOS or Kubuntu and push Novell/SuSE to the curb. Just My $0.02. Curtis. - -- Spammers Beware: Trespassers will be shot, survivors will be shot again! Like the song say: "Everything's 'Zen'... I don't think so"! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFFIr9D7CQBg4DqqCwRAon9AKDFcdWnOl1ZYkIhtNe5AucJpzJxDACg29ts AoYh4ysouihylKgTtVO13Mw= =egvJ -----END PGP SIGNATURE-----