Bug 147430 - freebsd-update(8) not updating /usr/src/UPDATING
Summary: freebsd-update(8) not updating /usr/src/UPDATING
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 8.0-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-03 13:30 UTC by Oleg
Modified: 2023-08-16 06:09 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oleg 2010-06-03 13:30:02 UTC 
freebsd-update not updating /usr/src/UPDATING

It seems not correct, because sources become new, but there is no information about changes in UPDATING file. Hard to maintain and make some confusion.

Also I noticed that updating by csup and by freebsd-update bring me different version of files. I means not major differences, but different in versions numbers. But this last may be ok.

How-To-Repeat: Just try to update by freebsd-update and check /usr/src/UPDATING
Comment 1 Alexander Best freebsd_committer freebsd_triage 2010-11-24 00:46:51 UTC 
State Changed
From-To: open->feedback

Is /usr/src/UPDATING still not being updated?
Comment 2 Alexander Best freebsd_committer freebsd_triage 2010-11-24 19:28:14 UTC 
State Changed
From-To: feedback->open

Feedback received. This is still an issue.
Comment 3 Alexander Best freebsd_committer freebsd_triage 2010-11-24 19:28:14 UTC 
Responsible Changed
From-To: freebsd-bugs->cperciva

Colin, could you take a look at this PR please?
Comment 4 Phil Pennock 2014-06-24 22:05:46 UTC 
This is still happening with FreeBSD 10.0; `src` is in `Components`, `IgnorePaths` is empty, other files in `/usr/src` get updated, only `/usr/src/UPDATING` is being skipped.

With 10.0 up to -p6, and <http://svnweb.freebsd.org/base?view=revision&revision=267829> showing that `releng/10.0/UPDATING` is being modified upstream, the last entry in `/usr/src/UPDATING` on this box is from "20131223".
Comment 5 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:41:37 UTC 
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Comment 6 Colin Percival freebsd_committer freebsd_triage 2019-03-12 23:00:14 UTC 
Drop freebsd-update PRs which were assigned to me.  I'm not working on this code any more.
Comment 7 Ed Maste freebsd_committer freebsd_triage 2022-12-14 16:40:03 UTC 
This is a consequence of the way FreeBSD-update binary patches are built. The patches from ENs/SAs are applied to the tree and new objects are built, and UPDATING itself does not appear in any of those patch files - it is modified only as the patches are committed to the tree.

We should indeed address this, perhaps as part of moving the FreeBSD-update build infrastructure to use git (assuming this doesn't become OBE via pkgbase). I have no expected timeline for this, though,