Just installed VL64-STD-7.2 B1 from a USB stick (used instructions found on an Arch Wiki). Used the Automatic option.
After installing, I got an error message that the Xscreensaver was very old. Did a system upgrade (probably shouldn't have) and istalled JRE runtime environment and Google Chrome.
Under most circumstances, doing upgrade is "the thing to do" as test releases progress. The problem here was a needed change to Network Manager that breaks existing installs due to path and other changes.
If you decide to reinstall, you may want to try the unreleased B2.
B2 already includes the changes introduced by the new build of NM, so that will go smoother. John, your current installation is still salvageable if you wish. One tip: the location of NM's pid file has changed. Also, make your /etc/NetworkManager.conf look as much like /etc/NetworkManager.conf.new as is practical on your system. Especially, the dnsmasq line should be commented out unless you're specifically using that. Internal mutations of hostname are also involved, which may be the reason for your connection problems.
I wanted to install some extra applications, but couldn't find them in GSlapt. Tried to add the "extra" repo but got a message after trying to add the repo and reloading:
"This package source failed or is not available."
Had the same problem when I tried to enable the patches repo. I checked the forums as well as this page
but can't seem to find a solution.
It's normal now to use only the untested repo until just before release. Part of the release process is populating the stable repos such as packages, extra, and patches. More packages need to be built for 7.2. We already have the scripts for almost all of what's needed, but just haven't updated the versions and triggered the builds. Too many out-of-date packages no longer maintained upstream were built for 7.1.
Please continute to test B2 and mention which packages you miss, so they can be updated. Half (or more) of the staff is taking a fairly long breather at this point before pushing on to release, so responses will be slow for now; but your input won't be wasted.