I've never used gslapt or slapt-get.
I used gftp to get GSB 2.28 and installed it with:
upgradepkg --install-new *?/*.t?z

and then blacklisted:
alsa-lib
glib2
gtk+2
gstreamer
libwnck
libxklavier
pango
pygobject

and then let slackpkg sort everything out.

If I follow, you are creating a local GSB mirror similar to getting Eric's KDE packages and then Is doing a recursive upgradepkg through the various directories?

Yep.
I screw stuff up so much I like having my own local mirrors of everything so I don't have to re-download everything every time I bork something.. :-)


EDIT:

This is a full blacklist for GSB:
I only use "REQUIRED"

##GNOME GSB 228
# ------ REQUIRED
alsa-lib
glib2
gtk+2
gstreamer
libwnck
libxklavier
pango
pygobject
# ------ Recommended Replacements
gst-plugins-base
gmime
gnome-icon-theme
libgsf
poppler
vte
# ------ Optional Replacements
compiz
pidgin
MPlayer

I forgot to mention:
I don't download or use the "ooo" directory.
It has open office in all the different languages in it.

Either way:

Great to hear the ongoing development reached a (small) milestone. Speculations on when 13.1 will go stable will grow stronger, getting us all 'warm and comfy'.

i think the md5sum errors are because of the latest slackpkg update: when you use it to "slackpg upgrade-all" and slackpkg itself has to be upgraded too, when it gets to be upgraded it deletes the repository lists that you fetched with "slackpkg update" and so the error
but just reupdate and relaunch "slackpg upgrade-all" and it should continue from where it stopped.

if you upgrade it before the others packages and refetch the lists with "slackpkg update" before "slackpg upgrade-all" all should be fine.

I notice the slackpkg errors when I tested in the office. So when I got home, instead immediately updating everything, I first upgraded slackpkg using upgradepkg tool. Restore my blacklist and mirror, then run slackpkg.

Hey, people.

I was wondering... in order to make kde 4.4.3 boot directly into init 4, I noticed an error (actually, a warning, because it didn't do nothing) about ConsoleKit nonexistent. So i tweaked my rc.local scripts in order to start the ConsoleKit-Daemon. So, I just wanna know from you who synced with slack64-current: did everything went ok?

Thanks.

yes, maybe you have to do also a "slackpkg install-new" to fetch the added packages.

http://distrowatch.com/?newsid=06055

Am I mistake, or is the un-official ISO that's available at slackware.no (build every tuesday) not missing out this very last update? ( see changelog date of 03 may 2010, iso's made 04-may-2010 )
I'm without rsync since my deskbox borked yesterday, and my laptop fails diskspace.. So I kinda wanted to DL the latest -current ISO with my wife's Vista laptop... burn it and go.

you can try this

http://ponce.cc/slackware/slackware6...unofficial.iso

Hi,

For the new user to get '-current' or this 'Slackware 13.1 BETA1' I suggest that you use Alien_Bob's-script-mirror-slackware-current.sh. To download -current, create cdrom/dvd Or Alien_Bob's-script -mirror-slackware-current.sh : UK backup of script script to download the '-current' of choice ( 'x86' meaning 32bit or 'x86_64' meaning 64bit). You can either pass parameters or edit the script to create the 'ISO' medium of choice. Plus be sure to select a mirror of choice to use. The script is well documented to allow you choices. Alien_Bob is a Slackware® contributor and has graciously provided the scripts/tools.

Personally I would rather create my own ISO rather than utilize something created by someone else. No offense intended 'ponce'.

no prob at all: I agree with you and would have given a similar answer, but he said he ain't got no space for an rsync

<grin> No?

I'd just boot systemrescuecd one of his downed *nix boxes.

OR, boot the Slack install DVD or CD disk # 1 (do the "In a pinch" thing according to Mr. Volderki) IOW boot the kernel from the CD whilst also having use of normal stuff on the hard drive. Works great for me in the 3 bto 4 btimes I seriously borked something in the last 9 or 10 years.

The only time a *nix box is ever down for me is upon a serious hardware failure.

Silly Windows. <grin>

--
Alan.

Thanx for the info, both!
I would rsync and build my own ISO if I had enough available space avail.. but I lack 'ext4' space and 'swim' in NTFS room ( as long as my wife doesn't notice )
DL'ing from ponce right now ( I love RDP ) Will update on 13.1b later today/weekend!