misc/135444: freebsd-update failing should be more verbose

Dan Naumov dan.naumov at gmail.com
Wed Jun 10 13:30:04 UTC 2009


>Number:         135444
>Category:       misc
>Synopsis:       freebsd-update failing should be more verbose
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jun 10 13:30:03 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Dan Naumov
>Release:        7,2-STABLE
>Organization:
>Environment:
agathon# uname -a
FreeBSD agathon.localdomain 7.2-STABLE FreeBSD 7.2-STABLE #0: Sat May 30 09:28:34 EEST 2009     root at agathon.localdomain:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
Now, I *know* you are only supposed to use freebsd-update to update installations done from official binaries and that it's not supposed to work on updating the -STABLE or -CURRENT branches. However, I believe that freebsd-update should be more verbose when failing to update such a system, explaining the reasons why. Right now, running freebsd-update fetch on a -STABLE system results in the following:

agathon# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 2 mirrors found.
Fetching metadata signature for 7.2-STABLE from update4.FreeBSD.org... failed.
Fetching metadata signature for 7.2-STABLE from update5.FreeBSD.org... failed.
No mirrors remaining, giving up.

There is absolutely no indication for the reasons of the failure.
>How-To-Repeat:
Install any version of FreeBSD that includes freebsd-update, do a source upgrade to -STABLE, install, reboot and run freebsd-update.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list