Bug 241831

Summary: freebsd-update from 11.3 to 12.1 causes error messages "Directory not empty"
Product: Base System Reporter: Victor Sudakov <vas>
Component: binAssignee: freebsd-bugs (Nobody) <bugs>
Status: New ---    
Severity: Affects Some People CC: doug, emaste, pvoigt, spam+bugs.freebsd.org, vas
Priority: ---    
Version: 12.1-RELEASE   
Hardware: Any   
OS: Any   

Description Victor Sudakov 2019-11-09 14:48:28 UTC
During the final stage of upgrading 11.3 to 12.1 with freebsd-update, cryptic messages can be seen: 

# freebsd-update install
src component not installed, skipped
Installing updates...rmdir: ///var/db/etcupdate/current/usr/share/openssl/man/en.ISO8859-1: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/openssl/man: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/openssl: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/man/en.UTF-8: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/man/en.ISO8859-1: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/man: Directory not empty
 done.
#

They seem harmless but give the unsettling impression that something is not right.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229502 may be related.
Comment 1 Victor Sudakov 2019-11-09 14:49:32 UTC
And no, I don't know how to reliably reproduce them.
Comment 2 Ed Maste freebsd_committer 2019-11-19 21:14:24 UTC
Confirmed with 11.2->12.1 update,

root@twelve:~ # freebsd-update install
src component not installed, skipped
Installing updates...rmdir: ///var/db/etcupdate/current/usr/share/openssl/man/en.ISO8859-1: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/openssl/man: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/openssl: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/man/en.UTF-8: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/man/en.ISO8859-1: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/man: Directory not empty
 done.
Comment 3 pvoigt 2019-11-20 14:53:03 UTC
Well, can confirm exactly the same error/warning on two different machines during 11.3 -> 12.1 upgrade.
Comment 4 Doug Poland 2020-11-18 15:13:54 UTC
Same on 11.4 to 12.2 amd64