Botched upgrade from 7/8 snap to 7/14 snap
-
Any idea what caused this? Was it the IPv6 code or something else?
-
As I said: Nothing was botched. You are seeing exactly what you are supposed to be seeing when you are using the IPv6 code now.
-
That's true for the 2.1 statement in the console but are you saying the IPv6 code should be causing those errors to show up in the console and in place of the WebGUI too?
-
If you aren't actually on the current code, yes. See the post I linked earlier, you need to fix your gitsync url.
-
Doh, I just saw that in the IPv6 forum too. Thanks :)
-
I resynced the old ipv6 tree just now so it would pick up the same set of bug fixes the main branch received for that, but that won't be happening quite so often now that it's in mainline. Fixing the gitsync URL is best.
-
Since I can't get into the webGUI I re-ran the gitsync from the console developer shell like you would for the initial gitsync to IPv6 (but used the new URL), doesn't seem to have fixed it. Still get the errors on startup and still can't get into the webGUI. I'll probably reinstall it tonight unless you see something I did wrong?
-
A gitsync (to either URL) should have fixed that particular error.
-
That was my thought as well. So since 2.0 has been branched into a mainline now, does that mean release is within grasp?
-
Actually try one more sync. I thought you hit one that had already been fixed, but it was a different one.
-
Sweet that fixed it. The console ran through a LOT more text this reboot, most of it about reinstalling packages (VMTools is all I have installed). Everything looks good now, thanks for the help.
