Date: Sun, 23 Nov 2014 11:55:23 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 195302] New: Missing lib32 on freebsd-update to 10.1-RELEASE Message-ID: <bug-195302-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195302 Bug ID: 195302 Summary: Missing lib32 on freebsd-update to 10.1-RELEASE Product: Base System Version: 10.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: dal36@gmx.co.uk I've updated one of my machines from 10.0-RELEASE-p12 (amd64) to 10.1-RELEASE using freebsd-update and found that the usual contents of /usr/lib32 were missing afterwards. I've reproduced this twice now, using the following process on a fresh install of FreeBSD 10.0-RELEASE (amd64), after having selected all optional items (including lib32) in the installer: # freebsd-update fetch install # reboot # freebsd-update -r 10.1-RELEASE upgrade # freebsd-update install # reboot # freebsd-update install # reboot # freebsd-update install # reboot After the first invocation of freebsd-update install, /usr/lib32 contains a large number of library files (i.e. as I would expect), but after the second invocation, it only contains the following three folders (all empty): dtrace i18n private Note that freebsd-update -r 10.1-RELEASE listed world/lib32 amongst the installed components when following this process; the 'not installed' part of the listed components was empty. Note also that the second run of this process was done ~24 hours after this message regarding issues with freebsd-update: http://lists.freebsd.org/pipermail/freebsd-stable/2014-November/080996.html This has been discussed in the FreeBSD forums, at the following threads: https://forums.freebsd.org/threads/10-0-10-1-upgrade-emptied-lib32.49103/ https://forums.freebsd.org/threads/missing-lib32-on-freebsd-update-to-10-1-release.49031/ Please let me know if there's any further info that will help with investigating this. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-195302-8>