32-bit Warnings ...

Hi

Not sure if anyone can help with the description I'm about to give, but when I was updating KDE through Smart (from 3.5.5 to 3.5.7), it was saying something about "32-bit ..." not being compatible and a huge list was presented on the screen (well off the screen actually). Does this sound familiar? Do I have a corrupted system? I can post more details when I get home from work later if needed.



Edit: Should note that I had just installed openSUSE 10.2 and was being the system up-to-date. No other packages were installed previously.

You probably have the wrong SMART repositories set up, that is, you probably have the 32-bit ones configured, not the 64-bit ones.

You probably have the wrong SMART repositories set up, that is, you probably have the 32-bit ones configured, not the 64-bit ones.[/b]

That is what I originally thought, so I went back to GURU's homepage. Went to "All Packages" (like I did before) but the 64-bit link had been selected (i.e different colour link to the rest) so it must have been the correct package(s) that were downloaded.



Edit: When I installed openSUSE, I selected the "32-bit ..." from the list. If I left this unchecked, would this mean I could only install 64-bit packages?

Please post the output of: uname -a

Please post the output of: uname -a[/b]

At work at the moment but will do when I get back home later.

Please post the output of: uname -a[/b]

Below is the output from "uname -a":-

Linux computer 2.6.18.8-0.3-default #1 SMP Tue Apr 17 08:42:35 UTC 2007 x86_64 x86_64 x86_64 GNU/Linux

One of Smart's weaknesses is the inability to properly reconcile bi-arch packages, and I've heard of cases where it's pulled in i586 packages when unable to find x86_64. Yast/zypper is much better in this manner.

Having said that, keep in mind that the 64-bit package list also includes 32-bit compatibility packages with the indicator -32-bit as part of the package name; if they were truly 32-bit they'd be listed as i386/i586/i686.

Sometimes when the build-service is building new packages, you wind up in a bit of a limbo stage where dependent packages aren't actually available, and this can throw up errors similar to the one you're receiving, though without knowing the actual message, that's a guess. Could be that if you try again within a few hours after the mirrors have updated, it may resolve itself.

But the other thing I really didn't like about Smart was that I found it too frequently wanted to downgrade/uninstall packages when it couldn't resolve dependencies, rather than manually stepping through them via Yast. So that's just a subtle suggestion to maybe try Yast, too. It could actually help you narrow down where the problem may be.

Anyways, just my 2c...

Cheers,
KV

It's strange as I've never had problems with 64-bit version and Smart before now . Just in case it may have been user error, I re-installed openSUSE again last night and had exactly the same error (the conflict in question was pointing to kdelib32...). Anyhow, I'm re-installing the 32-bit version now and just about to update KDE (fingers crossed). Thanks guys for your help on this.

It's strange as I've never had problems with 64-bit version and Smart before now . Just in case it may have been user error, I re-installed openSUSE again last night and had exactly the same error (the conflict in question was pointing to kdelib32...). Anyhow, I'm re-installing the 32-bit version now and just about to update KDE (fingers crossed). Thanks guys for your help on this.


[/b]

The SuSE KDE developers have been working to update KDE-3.5.7 for opensuse 10.3. A week or so back, they started putting some of the updates into those for 10.2. Needless to say there were a few oversights causing a few problems. I think most of them have been fixed by now; or, I got mine fixed and quit following the issue.

http://www.suseforums.net/index.php?showto...amp;hl=io-slave may help, especially that part about:

rpm -qa 'kde*3*' --queryformat '%{name}\n' | xargs smart reinstall --yes

and
look at the names of the KDE packages having problems there & on Novell bugzilla (link on that page) for other workarounds.

I managed to install and update the 32-bit version without any problems . Now I'm tempted to re-install the 64-bit version again (hoping that the problem has been fixed). :unsure:.

Could I ask a quick question? When installing the 64-bit version of openSUSE, would you recommend adding 32-bit support or just keep it plain 64-bit?