Since October my FreeBSD 8.4 systems (and 9.1) tell me that there are updates available when I run `freebsd-update fetch`. The updates all reside in /usr/share/zoneinfo. When I install them and run freebsd-update fetch, the same updates are fetched: # freebsd-update fetch Looking up update.freebsd.org mirrors... 5 mirrors found. Fetching metadata signature for 8.4-RELEASE from update2.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. The following files will be updated as part of updating to 8.4-RELEASE-p20: /usr/share/zoneinfo/Africa/Bamako /usr/share/zoneinfo/Africa/Banjul /usr/share/zoneinfo/Africa/Conakry /usr/share/zoneinfo/Africa/Dakar /usr/share/zoneinfo/Africa/Freetown /usr/share/zoneinfo/Africa/Lome /usr/share/zoneinfo/Africa/Nouakchott /usr/share/zoneinfo/Africa/Ouagadougou /usr/share/zoneinfo/Africa/Sao_Tome /usr/share/zoneinfo/Atlantic/St_Helena /usr/share/zoneinfo/Pacific/Johnston # # # freebsd-update install Installing updates... done. # # # freebsd-update fetch Looking up update.freebsd.org mirrors... 5 mirrors found. Fetching metadata signature for 8.4-RELEASE from update2.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. The following files will be updated as part of updating to 8.4-RELEASE-p20: /usr/share/zoneinfo/Africa/Bamako /usr/share/zoneinfo/Africa/Banjul /usr/share/zoneinfo/Africa/Conakry /usr/share/zoneinfo/Africa/Dakar /usr/share/zoneinfo/Africa/Freetown /usr/share/zoneinfo/Africa/Lome /usr/share/zoneinfo/Africa/Nouakchott /usr/share/zoneinfo/Africa/Ouagadougou /usr/share/zoneinfo/Africa/Sao_Tome /usr/share/zoneinfo/Atlantic/St_Helena /usr/share/zoneinfo/Pacific/Johnston # I have Nagios set up to monitor for new updates on FreeBSD and all my 8.4 and 9.1 systems are affected. 9.3 and 10.1 are not affected. The difference between these systems is that on 8.4 and 9.1 these files are hardlinks to one timezone file (not part of the perpetual update). On 9.3 and 10.1 these files are regular files (different inodes). Could someone have a look at this and please tell me how to resolve this issue. Thanks in advance.
Created attachment 154685 [details] A workaround script for use on FreeBSD 8.4
I workaround this problem with the attached script. That is, I move aside the files in question (as well as /boot/kernel/linker.hints per bug #186273), run freebsd-update, then move them back again. HTH, Greg.
I believe this is the same underlying issue as #189249. Sadly it was never fixed for 8.4, but as 8.4 is now EOL and this bug is fixed in all supported releases (9.3, 10.1, 10.2) there's no more need to keep this one open.
(In reply to Andrew Daugherity from comment #3) Agreed based on later comments. I'll mark this bug as a dupe of bug 189249. *** This bug has been marked as a duplicate of bug 189249 ***