For future reference


#1

How do we make sure that our systems is in sync with the repositories?

Iv’e tried the following;

pc-updatemanager syncconf
pc-updatemanager confcheck
pc-updatemanager pkcheck

@beanpole135 had mentioned another way as well. No, I did not write it down, which is why I’m asking, so that we all benefit down the road.


#2

Does your question mean this display


of the update manager can’t be trusted?


#3

In connection with this:

% pc-updatemanager --help
pc-updatemanager: Usage
----
  branches              - List available system branches

# Let’s do it:
% sudo pc-updatemanager branches
Boot-strapping updater…OK
No updates available for 12.0-CURRENT!

This is no “listing of branches”… == ???

Edit:
And: Why are there exactly 2 tags (no more, no less)?
“install <tag>,<tag2> - Install system updates” ???

The man-page tells us:
install update1, update2, …
Install specified update(s).

What does that mean? “At least 2, or - optionally - infinitely many more than 2”?

I think, the “–help” output and the man-page could
be enhanced by an “examples”-section.


#4

The “branches” option in pc-updatemanager is a relic of the PC-BSD days where you could have different OS-versions of update paths (9.x and 10.x when that option was active). Since TrueOS was spun up and started using base packages that entire “branches” mentality became obsolete (since the OS packages are also available via a pkg repository). We left it in there just in case we ever needed it again in the future, but as time goes on I think it is about time to go ahead and clean that up and remove it since the base package system “just works” so much better than the branch system of old.

@RodMyers :
I think the command you were looking for was: pkg update -f
That will forcibly re-download and re-sync the package database with the upstream repositories.


#5

That is it. I still don’t show any updates available, which is why I ask