Just a very happy news!

At last I successfully upgraded from 10 to 10.1 using slapt-get --dist-upgrade without a problem (even using linuxpackages.net in my repositories).

I just needed to make one change in /etc/X11/xorg.conf (regarding keyboard) but since I was aware of the problem before I could do it easily.

Everything works fine now. But the mozilla problem continues. No longer does mozilla launch at all but just gives this error:
Another question is this: I replaced all the old config files which had a replacement with the extension .new. Is this all right, because all those configs with the .new extension I had not changed before.

Again firestarter (which I installed with slapt-get gives this error and quits):
If anybody knows how I can fix these minor problems, I would be very grateful.

P.S. KDE 3.4 looks neat. This is my first look at KDE 3.4.

well...on Mozilla : why do you use the script to start it ?
maybe try to run " /usr/bin/mozilla " ( that's what i use...)

btw.: a quote from that script:
----------
## This script is a hack. It's brute force. It's horrible.
## It doesn't use Artificial Intelligence. It doesn't use Virtual Reality.
## It's not perl. It's not python. It probably won't work unchanged on
## the "other" thousands of unices.
-----------

... and i don't know firestarter...

egag

I didn't use the script to start it. I used the menu item from KDE.

Also trying /usr/bin/mozilla didn't work. I'll try to post the exact error message later.

Mozilla stopped working when I did a slapt-get mozilla to update it before I did the dist-upgrade. Not a major problem for me because I use firefox anyway, but still it sticks out like a sore thumb and I like things to be tip-top perfect

Probably I should recompile it from sources?

Regards.

How about uninstalling mozilla and then doing a manual clean install of the version from 10.1 updates or current.

Yes. I'll try that and report my progress. Thanks.

I was very happy when I posted this thread because I had read some not-so-complimentary views about slapt-get and swaret on this forum so I thought: Ok, I might have to reinstall Slackware. But it booted and after changing keyboard to kbd in xorg.conf I was able to load KDE 3.4 so it seems that most things have worked with the update. Very happy now to have Slackware 10.1 on my system. There are some minor problems like I mentioned above, but nothing serious. I never expected it all to work anyway. I like to experiment with Slackware because my main OS is Debian where I have my important work and I can do all the breaking I want with Slackware.

I think I might have to install the gtk 2.0 libraries to get firestarter, but it appears to already exist on my system, so I have no idea what the problem with firestarter might be (from the error message you can see in my first post).

Yeah you always get those who criticise swaret and slapt-get because they prefer to do things without automated tools. Personally I have never had any major issues with swaret so I never take heed of the negative comments.

I found out why firestarter did not work.

The package name which was downloaded was:
Obviously this is a AMD 64 package. How did this happen? How can I always make sure that only x86 32-bit packages are downloaded by slapt-get rather than 64-bit?

Regards.

From /usr/doc/slapt-get-0.9.9l/example.slapt-getrc

# To exclude architectures such as i686, use the following:
# [\_\-]+i686

So, it would be like [\_\-]+x86_64 in the EXCLUDE list.

Thanks gbonvehi. I'll try doing that.

I tried excluding the x86_64 using the EXCLUDE statement. But it doesn't work.

The 486 package is also available in the mirror, but doesn't show up in slapt-get --search. Can anybody post a working slapt-getrc file here which excludes the x86_64 packages?

I am not really sure of which regular expression to use.

How can I fix it so that I download only the 486 packages and not the x86_64 packages?