https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277964
Bug ID: 277964
Summary: Obsolete Files Not Removed upon 13.3 P0 to 14.0 P5
Update
Product: Base System
Version: 14.0-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: misc
Assignee: b...@freebsd.org
Reporter: m...@scarahoof.com
Updating from FreeBSD RELEASE 13.3 P0 to 14.0 P5 by following the instructions
at <https://www.freebsd.org/releases/14.0R/installation/#upgrade> failed to
remove obsolete files. This failure occurs after updating installed packages
and the final run of “freebsd-update install” as the root user, which returns
the folowing:
# freebsd-update install
src component not installed, skipped
Installing updates...rmdir: ///usr/tests/usr.bin/uuencode: Directory not empty
rmdir: ///usr/tests/usr.bin/uudecode: Directory not empty
done.
The source freebsd-src-main/ObsoleteFiles.inc file contains as a comment “#
20220418: uudecode merged into uuencode and renamed to bintrans” confirming
that the /usr/tests/usr.bin/uuencode directory should have been removed.
Checking the /usr/tests/usr.bin directory confirmed that the uuencode directory
was not empty and was not renamed, and that the the uudecode directory had not
been merged. Other files and directories listed in ObsoleteFiles.inc to be
removed were not, indicating the failure to remove or rename the uuencode
directory prevented processing of the ObsoleteFiles.inc file by freebsd-update.
Since the rmdir directory command was chosen to be run, it might be that the
contents of the uuencode and uudecode directories were intended to be moved to
a new bintrans directory leaving uuencode and uudecode empty and then possible
to remove by running rmdir.
--
You are receiving this mail because:
You are the assignee for the bug.
