Date: Wed, 4 Feb 2009 11:23:39 GMT From: "Ben C. O. Grimm" <freebsd@bengrimm.net> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/131359: freebsd-update tag file not updated after freebsd-update rollback Message-ID: <200902041123.n14BNdx3038890@www.freebsd.org> Resent-Message-ID: <200902041130.n14BU1Rt090195@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 131359 >Category: misc >Synopsis: freebsd-update tag file not updated after freebsd-update rollback >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Feb 04 11:30:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Ben C. O. Grimm >Release: 7.1-RELEASE-p2 >Organization: None >Environment: FreeBSD 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: After performing a rollback from (e.g.) 7.1-RELEASE-p2 to 7.1-RELEASE-p1 the tag file (/var/db/freebsd-update/tag) does not reflect the changed patch level. It remains on "|2|". After a rollback, there is no way to find out which patch level you are actually running. Only the admin's memory is available for that, and he may encounter a train. The tag is only updated by the 'freebsd-update fetch' command. >How-To-Repeat: >Fix: Either have freebsd-update alter the tag file, or export the patch level to e.g. /etc/motd or uname -a (which also does not reflect the current patch level of the OS - just the kernel's). >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200902041123.n14BNdx3038890>