#FreeBSD pkg 2.6.0 is reported to be broken.

[tomaoki@mastodon.bsd.cafe]

#FreeBSD pkg 2.6.0 is reported to be broken.
https://lists.freebsd.org/archives/dev-commits-ports-main/2026-March/181408.html

`pkg lock ports-mgmt/pkg` is adviced until the issue is addressed.
I've done so as I've noticed the post at the time just pulling updates into my local ports repo.

Acccording to this another report, logic for deletion seems to become too aggressive.
https://lists.freebsd.org/archives/dev-commits-ports-main/2026-March/181412.html

At least on previous version 2.5.1, it can forcibly delete specific pkg only with "-f" option.
But the behavior mentioned in above report suggests that possibly deletions are done for anything depending on the pkg to be deleted, too.

Anyway, users of quarterly wouldn't be affected, as pkg 2.6.0 is not yet merged into 2026Q1.

[_bapt_@mastodon.social]

@TomAoki it is not broken at all, please be careful in how you announce things, it had a regression that only affects portmaster users (and people doing make deinstall in ports) aka a minor part of the users! also to be fair with pkg developers semantically the right behavior of pkg delete -f would be to be recursive! It's not due to pkg_delete legacy, in the future we should introduce a new flag like pkg delete -f --ignore-rdeps and make the ports tree use it