On 5/21/26 14:21, Piotr Smyrak wrote:
On Thu, 21 May 2026 18:47:22 +0200
Gareth de Vaux <[email protected]> wrote:

On Sat 2026-05-16 (10:01), Tomoaki AOKI wrote:
rm -rf /usr/ports/*/*/work && rm -rf /usr/ports/*/*/work-*

Great thanks, that worked :) I'd done 'portsclean -C' but that
evidently doesn't clean everything.

Do you habitally run `portsdb -Uu`? (If you're always running
`make index` at /usr/ports after updating ports tree, it can be
`portsdb -u`.) portsclean requires up-to-date INDEX.db to work.

FTR 'portsdb -Uu' and 'portsclean -C' just removes /usr/ports/*/*/work
and leaves these in my case:

/usr/ports/devel/glib20/work-bootstrap
/usr/ports/devel/gobject-introspection/work-bootstrap

which still need manual removal.

This is a bug in the stable version of portupgrade. It means that
portsclean is not port flavour aware, and it will fail not just on
gobject and glib20, but any other port flavour, for which the WRKDIR
would be work-${FLAVOR}.

This was fixed later for unreleased 2.4.17:
https://github.com/freebsd/portupgrade/commit/c47302011528435ba32a30bc7f43b32fef2b3836


Which would erroneously remove a valid port: /usr/ports/sysutils/work-tuimer

        Michael


Reply via email to