Have checked similar threads. Running 12.2, Configured #/etc/slackpkg/slackpkg.conf; commented Main=slackware, changed ARCH to = x86_64,tried Main=slackware64, tried PKGMAIN="slackware64"; and added in 64 to /slackware/slackware-current so it looks like this slackware/slackware64-current in /etc/slackpkg/mirrors.
What happens when i issue:#slackpkg update is that .txt and .bz lists and files download but slackpkg/mirrors list doesn't change. I don't think anything has downloaded since i can't find anything in /var/cache/packages
nothing in /tmp ; then if i do slackpkg update I get "Nothing has change are you sure you want to download files? Y/n

When I issue slackpkg install-new, I get "No matching packages" try /usr/bin reinstall...
After that trying to issue slackpkg upgrade-all is futile... Noticed there was no "PKGMAIN=" in slackpkg.conf *only MAIN=slackware ...
Should the Order of Download Priority be changed or reference to slackware?
What am I doing wrong? Thanks for your help

Was running slackpkg 2.7x something, downloaded slackpkg 2.8x configured it and set mirror. It is working fine.
The downloading and upgrading is taking forever and i keep getting "Warning that this pkg and that pkg may have not installed correctly and i may have to reinstall the older pkg". I am wondering if it I am running out of space on /root, its only 15GB ?? We'll see.

I don't really think that you can upgrade from a 32-bit Slackware (12.2 is 32-bit, isn't it) to 64-bit, according to the CHANGES_AND_HINTS.TXT:

1 members found this post helpful.

Why wouldn't one be able to upgrade from 32bit 12.2 when you can build a multi lib slackware OS?
I saw that upgrade from earlier version than 13.0 is not supported technically but it is doable and am finding enough posts of people who have done it and solved issues in the forum, it is a great learning opportunity, I get to discover the what, where, when, why, and how, i love it!
I started out with a Howto from Rob Workman on some slackware blog, its bookmarked on my other computer. Come to find 1 issue has to do with partition types ie. ext 3 vs ext4 I have to take a closer look at the straight install documentation. In any case i have the directory on my PC a good start and my 12.2 install is working fine still because I did not change the kernel existing install. I will build off what i have and transfer to its' own partition for a slackware64 current mirror. When I have it working I will install onto the 64 bit PC.

In any case slackpkg 2.8x worked great and did what it was supposed to do... issue was the version I started out with it was too old but good enough to download the one I replaced it with

Those are two very different things.

What happens if you start upgrading a 32-bit Slackware to Slackware64? Bit by bit, 32-bit binaries are being replaced with 64-bit binaries, and there will come a point where slackpkg will call a binary that has been upgraded to 64-bit.
And that will be end of story... because a 32-bit kernel does not support 64-bit application binaries.

The other way round (starting 32-bit binaries on a 64-bit kernel) is supported because the Slackware64 kernels are configured that way (it's not a default configuration.

Eric

1 members found this post helpful.