Bug 131359 - freebsd-update(8): freebsd-update tag file not updated after freebsd-update rollback
Summary: freebsd-update(8): freebsd-update tag file not updated after freebsd-update r...
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 7.1-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-04 11:30 UTC by freebsd
Modified: 2019-01-17 21:40 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description freebsd 2009-02-04 11:30:01 UTC
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.

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).
Comment 1 Remko Lodder freebsd_committer freebsd_triage 2009-02-04 20:49:13 UTC
Responsible Changed
From-To: freebsd-bugs->cperciva

Reassign to Colin who authored FreeBSD-update
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:18 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped
Comment 3 Gerald Aryeetey 2019-01-17 19:50:06 UTC
This is by design. freebsd-update fetch should be used to update the tag file and determine what is the release that should be updated to.

`freebsd-version` was added (after this bug was submitted) to allow checking for the correct patch/release number.