That is odd. Perhaps you uncommented a -current mirror that has issues? Just grasping at straws as that should work.

Or. When you uncomment a mirror, you have to remove the # and a space. If you leave the space, it might **** things up. Only a guess.

Yes. You must remove the # in front of a mirror, save then exit, for slackpkg to work. You do not need to remove the space anymore. The space glitch did mess up past versions of Slackware.

Ah, thanks, hitest. Didn't know the space removal wasn't necessary now.

You're welcome, brianL. :)

The mirror that I uncommented is in the -current section, and I did save it. It's the Oregon State university ftp site.
I guess I could try a different mirror....

Nothing wrong with that mirror, that's the one I use. Odd indeed.

I can confirm this behavior. I have made some tests in Virtualbox, using my own mirror (which is not mirrored from Oregon State University):
a) Upgrade from fresh install:

1. Install Slackware64 13.37 in Virtualbox
2. Add my mirror in /ect/slackpkg/mirrors
3. slackpkg update, OK
4. slackpkg install-new, cancelled the test here because of gpg errors

b) Upgrade from an up-to-date OS

1. Install Slackware64 13.37 in Virtualbox
2. Add my 13.37 mirror in /ect/slackpkg/mirrors and upgraded the system the usual way (update, install-new, upgrade-all, clean-system), OK
3. Change the mirror to Slackware64 -current and repeat the process, cancelled after install-new because of gpg errors.

c) Upgrade with updating gpg first:

1. Install Slackware64 13.37 in Virtualbox
2. Add my 13.37 mirror in /ect/slackpkg/mirrors and upgraded the system the usual way (update, install-new, upgrade-all, clean-system), OK
3. Change the mirror to Slackware64 -current
4. updated the package database and gpg (slackpkg update followed by slackpkg update gpg)
5. Used the usual routine to upgrade the system (as above), cancelled at install-new because of gpg errors

Seems to me that upgrading from 13.37 to current is broken at this time.

Strange, I did on Wednesday, and it's worked for me.

As i can see you have the 32 bit version installed. May it be possible that this is a 64 bit only issue?

@ceh383: Which version have you used?

Mmm, could be.

At least I now know it's not just me...
I'm running 64bit here..

This is almost exactly what I did, the only differences are..
1) A)Upgrade from an up-to-date OS with added software (bumblebee, cairo dock, etc) B)Upgrade from fresh install completely updated C)Upgrade from fresh install D)Upgrade with updating gpg first
2) I was installing to a machine, not a virtual machine.
3) I used the Oregon State University mirror.

Thanks for taking the time to verify this issue....

Now that there has been a "Friday the 13th massive upgrade", can one assume this issue has been resolved?

I just tried it in the VM and the problem still exists.

Thanks for the info TobiSGD,

I guess I'll have to keep on waiting....LOL