Date: Wed, 10 Jun 2009 13:26:51 GMT From: Dan Naumov <dan.naumov@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/135444: freebsd-update failing should be more verbose Message-ID: <200906101326.n5ADQpXH003280@www.freebsd.org> Resent-Message-ID: <200906101330.n5ADU4Mn057023@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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@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:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200906101326.n5ADQpXH003280>