Date: Wed, 09 Jan 2019 02:26:52 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 234771] freebsd-update(8) fails on 11.1-STABLE: fetching public key fails Message-ID: <bug-234771-227-JzVW753M2R@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234771-227@https.bugs.freebsd.org/bugzilla/> References: <bug-234771-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234771 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |cperciva@FreeBSD.org Status|New |Open Keywords| |needs-patch Summary|freebsd-update(8) fails on |freebsd-update(8) fails on |11.1: fetching public key |11.1-STABLE: fetching |fails |public key fails Severity|Affects Only Me |Affects Some People --- Comment #4 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to Yuri Victorovich from comment #3) One can also use --currently-running <release>, which is a new command line frontend for the previously environment-based variable (UNAME_r) override u= sed to 'fake' the current versions. From man freebsd-update: --currently-running release Do not detect the currently-running release; instead, assume that the system is running the specified release. This is most likely to be useful when upgrading jails. This issue ("fetching key ... failed") is a frequently asked question/repor= ted issue. It would be great to improve the error/messaging and user experience= for these cases. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234771-227-JzVW753M2R>