Shouldn't it show up in GSlapt then?
It should. I'd add the /testing repo to your sources and then click on the Update button. See if it shows up. You can always disable the /testing repo the next time if it makes you uncomfortable to include it.
I kind of like "trailing edge" and stability more than "bleeding edge," and the newest available package. I guess it it comes from Debian, but when I tested that distribution I always used the stable version. I kind of avoid Ubuntu and its many derivatives specifically because it uses the "testing" branch. Probably the terminology is different in Slackware. But I'm still reluctant to add "testing" to my repository. But mostly I've just gone with the default. And, I'm used to doing regular full updates in CentOS -- but maybe that's not the best way to way to go in Slackware/VectorLinux. I obviously need to learn more.
/testing in VectorLinux is for packages, not the whole distribution. You can decide which packages from /testing you want enough to be a bit daring; you don't have to install all of them, or any of them. But particularly in the case of browsers, a new version is often issued to fix security holes. I want that kind of update as soon as I can get it. Since all packages go in /testing first, I don't want to wait for days or weeks for the package to make its way out of testing. That's why I keep /testing enabled and just make sure I know where an update is coming from. Mostly I avoid things in /testing unless I know for sure that I want them, not just because they're new.
One way you can find out what upgrades are available in /testing without keeping /testing enabled is to check *just* testing in your Sources, then do Update to get your new list of packages. Clicking on Update in Gslapt simply updates your package list; it doesn't do an update of the packages. After you've updated the package list with what's available in /testing, click on Mark All Upgrades, then on F4 to View Marked. You'll see just the packages in /testing and if you want one, make a note of it. Then enable your usual repo sources (including /testing), update again, and then click on the package or packages in /testing that you noted you want to install. You need to have /testing enabled when you do this because there may be dependencies there that have to be fetched along with your package. When you've finished selecting the updates you want, click on Execute. The dialog will show you what packages will be installed. Finally click on OK and Gslapt will get your updates. Once everything is completed, go to Preferences, Sources and exclude /testing again. You can then continue doing upgrades your preferred way.
Again, in VectorLinux /testing does not refer to the distro itself. It includes just packages that aren't considered ready for the regular repos because they haven't been tried by enough users. If you do install a package from /testing, it would really help if you would go to the "VL package news and Updates" section of the forum and leave a reply in the topic that announces that package. If you have or don't have problems, mention that.
gsb-2.22 contains gnome things that are needed by some packages. Usually they are needed as dependencies.
Thanks. Wondered what that was. So it's Gnome 2.22.
I don't know if it's gnome 2.22. I also don't know how much of Gnome is included. Can you install Gnome from the gsb-2.22 repo? I have no idea.
I know sometimes that yum (in CentOS) gets out of sync and you have to issue a "yum clean all" command to get everything synchronized again. Is there something like that in Slapt?
I don't know. Maybe there's something in the command-line slapt-get. Nothing jumped out at me when I did man slapt-get.