Hopefully the title is correct. I think that's what it's called under BSD.

Anyways I did a fresh install of GhostBSD under VMWare with the goal of getting some software ported to FreeBSD. I did a fresh install of GhostBSD 4.0 32-bit and then run the following commands to get everything in order to install software. This has normally worked for me with all the flavors of GhostBSD 4.0 and RCs.

But today I do this and unless the Ports Repository is boogered up (which has happened a couple of months ago) I get all kinds of errors attempting to install software that I have always installed fine under all my GhostBSD 4.0 installations. So I figured I'd start from scratch and do a # sudo make install uninstallbut that fails too.

fmh@ghostbsd /u/p/p/pkg> sudo make install uninstallPassword:/!\ WARNING /!\WITH_NEW_XORG and WITHOUT_NEW_XORG knobs were removed and have no effectWITH_KMS was removed and has no effect

===> License BSD2CLAUSE accepted by the user=> pkg-1.4.2.tar.xz doesn't seem to exist in /usr/ports/distfiles/.=> Attempting to fetch http://files.etoilebsd.net/pkg/pkg-1.4.2.tar.xzpkg-1.4.2.tar.xz 100% of 1757 kB 130 kBps 00m14s===> Fetching all distfiles required by pkg-1.4.2 for building===> Extracting for pkg-1.4.2/!\ WARNING /!\WITH_NEW_XORG and WITHOUT_NEW_XORG knobs were removed and have no effectWITH_KMS was removed and has no effect

===> License BSD2CLAUSE accepted by the user===> Fetching all distfiles required by pkg-1.4.2 for building=> SHA256 Checksum OK for pkg-1.4.2.tar.xz.===> Patching for pkg-1.4.2===> Configuring for pkg-1.4.2configure: loading site script /usr/ports/Templates/config.sitechecking for a BSD-compatible install... /usr/bin/install -c -o root -g wheelchecking whether build environment is sane... configure: error: newly created file is older than distributed files!Check your system clock===> Script "configure" failed unexpectedly.Please report the problem to portmgr@FreeBSD.org [maintainer] and attach the"/usr/ports/ports-mgmt/pkg/work/pkg-1.4.2/config.log" including the outputof the failure of your make command. Also, it might be a good idea to providean overview of all packages installed on your system (e.g. a/usr/ports/ports-mgmt/pkg/work/pkg-1.4.2/src/pkg-static info -g -Ea).*** Error code 1

Something is very wrong in the current Ports. Since nothing changed in the ISO I am using when GhostBSD 4.0 was released I know it's not GhostBSD. I did another fresh install in VMWare just to make sure and after doing all the normal stuff I was informed to do a sudo make deinstallsudo make reinstall

so I did.

fmh@horvatbsd /u/p/p/pkg> sudo make reinstall===> Installing for pkg-1.4.2===> Registering installation for pkg-1.4.2Installing pkg-1.4.2...If you are upgrading from the old package format, first run: # pkg2ng

So I did asudo pkg2ngit runs for a long time and generates a lot of errors.

Something changed in Ports because everything worked about a month ago. Funny thing is Chromium one day is in Ports and the next it is not. So it is changing constantly and not always for the best in this case with the issue I am having. I have another VM installed a month ago and software will install just fine there. I have a document I created and store online so every time I create a new VM or setup GhostBSD on real hardware I do the exact same steps every time to get the machine setup. I Copy and Paste line for line from the document into the terminal. This is the first time it hasn't worked. That's why this morning I setup a fresh VM with GhostSBD just to make sure I didn't do anything wrong the other day. I still get the same errors so it wasn't me this time.

But you might have problem with the new GDM upgrade, the GDM past from GDM2 to GDM3 and GDM 3 need 3D acceleration. Not that ports and packages on GhostBSD are always updating to the latest available if you want to install some software you will need to update constantly your software.

and got this screen when I went to shutdown. Now the system will not boot. I did this on the second VMWare fresh install of GhostBSD 4.0 and got the exact same thing and it will not boot either. So something is definitely not right.