problem fetching ports tree

[USerID]

10 years have passed... and the problem is as good as new. What patch should I make in 2024?

root@none:~ # portsnap fetch update
portsnap: Directory does not exist or is not writable: /var/db/portsnap

root@none:~ # freebsd-update fetch
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 14.1-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 14.1-RELEASE-p3.

 

[SirDice]

I would suggest stop using portsnap(8), it's going to be decommissioned. Use devel/git (preferred), net/gitup (easy to use) or devel/got.

 

[USerID]

Solution to the problem in 2024:
root@none:~ # mkdir /var/db/portsnap
root@none:~ # chmod +rw /var/db/portsnap
root@none:~ # portsnap extract

root@none:~ # portsnap update
Ports tree is already up to date.


 

[Argentum]

Solution to the problem in 2024:
root@none:~ # mkdir /var/db/portsnap
root@none:~ # chmod +rw /var/db/portsnap
root@none:~ # portsnap extract

root@none:~ # portsnap update
Ports tree is already up to date.


Yes. And one can still build the ports-mgmt/portsnap from ports. It is not included in the base any more. This is philosophical question, is it good or bad. Personally I tried the gitup way and disappointed. portsnap seems to be much faster.