Quote from: franco on Today at 10:11:40 AM3. We forcefully disable FreeBSD repo since a few years on firmware configure. We can't avoid user console fiddling with that neither, but at least preserve the integrity the system still has after the fact.I guess what I am trying to do is have a failsafe where the script aborts in between /usr/local/etc/pkg/repos/FreeBSD.conf being removed during the script's process (so the disable override is gone), and refresh.sh re-copying back the sample confs. Without that failsafe, the disable override isn't there when opnsense-revert or an update is run again, and so the system falls back to using /etc/pkg/FreeBSD.conf. This is what happened in my case. When I re-ran opnsense-revert after the first abort, I received an error about package conflicts (can't recall the exact message), and was prompted to reinstall/upgrade pkg. Not realising that this was because the FreeBSD repo was being used, I did that, and this led to my troubles.
Quote from: Patrick M. Hausen on April 01, 2026, 03:19:40 PMSee you in Brussels, possibly?
Quote from: Monviech (Cedrik) on April 01, 2026, 11:37:59 AMI guess most of these issues are self inflicted due to the medium of internet.
Quote from: trasz@ on March 27, 2026, 10:42:47 AMThe way commit bits work is that an existing committer (anyone with FreeBSD.org email) sends core@ an email proposing someone, and then core votes on that.
Quote from: franco on Today at 10:03:51 AMAll the people wanting the ultimate Linux based firewall but nobody really doing it