Is there an issue in building the binaries where a 'not automatic' flag isn't being set?
sudo pkg autoremove
shows...
Installed packages to be REMOVED:
automount: 1.7.8_2
backup-station: 0.2
binutils: 2.40_4,1
fusefs-lkl: 4.16.g20180628_4
fusefs-ntfs: 2022.10.3
gcc12: 12.2.0_6
ghostbsd-pkg-conf: 23.06.05
ghostbsd-update-scripts: 21.08.21_2
libublio: 20070103_3
libzip: 1.9.2
networkmgr: 6.2
py39-bectl: 0.2
setxkbmap: 1.3.2
software-station: 1.6
sudo: 1.9.13p3
update-station: 4.6
version: 23.06.05
xdg-user-dirs: 0.18
xmodmap: 1.0.10
xorg-macros: 1.19.3
xtrans: 1.4.0
Which is a little bizarre - there are crucial GhostBSD packages here...
I reinstalled everything [update -f] and then
sudo pkg set -A 0 'name of package'
for the essential ones to mend the problem.

autoremove option will remove dependencies that are not needed by any app.

Autoremove should only remove outdated packages. Those packages listed should be old versions

You can check by running

pkg info automount

To check which version is installed

BTW you can update GhostBSD with the update-station program

OK, but the system is up to date and these are not outdated pkgs that autoremove wished to cull....
So why would GhostBSD system pkgs [networkmgr, update-station, software-station...] and sudo, automount... be in autoremove''s sights?
Isn't this unusual?

Is it because I experimented this last week with ghost-build and it used different pkg targets?

@nevets looks like ghostbsd-utils was removed. It is a meta package for to install all GhostBSD tools.

Thanks Erik, spot on - the ghostbsd-utils pkg is missing

neville wrote: ↑Sun Jun 25, 2023 8:15 pm Autoremove should only remove outdated packages. …

No, please see pkg-autoremove(8).

Okay thanks

I will make a ticket to mark default packages as vital.

Here is the ticket https://github.com/ghostbsd/issues/issues/169.