Bug 120552 - freebsd-update(8): freebsd-update - -r should check existence of directories
Summary: freebsd-update(8): freebsd-update - -r should check existence of directories
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 6.3-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-12 11:40 UTC by edwin
Modified: 2022-12-14 16:16 UTC (History)
2 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 edwin 2008-02-12 11:40:00 UTC 
While running the FreeBSD update tool to upgrade to 6.3, I got this
warning:

    Fetching metadata signature for 6.3 from update1.FreeBSD.org... failed.
    No mirrors remaining, giving up.

That was my fault, I had specified "6.3" instead of "6.3-RELEASE".
But still, the tool could me in a more friendly way that the directory
6.3 didn't exist and that I should look with a webbrowser at
http://update1.freebsd.org/ to see which upgrade releases are
available.
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2008-02-12 11:44:49 UTC 
Responsible Changed
From-To: freebsd-bugs->cperciva

Over to maintainer
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:44:43 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 3 Gerald Aryeetey 2019-01-14 16:31:05 UTC 
This shouldn't be a problem anymore since if the release is specified as "6.3" it will automatically expand it to "6.3-RELEASE".
Comment 4 Colin Percival freebsd_committer freebsd_triage 2019-03-12 23:00:08 UTC 
Drop freebsd-update PRs which were assigned to me.  I'm not working on this code any more.
Comment 5 Ed Maste freebsd_committer freebsd_triage 2022-12-14 16:16:09 UTC 
Believed fixed per comment #3, please submit a new PR if any issues remain.