From owner-freebsd-questions@freebsd.org Thu Oct 1 22:36:41 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C9E08435E53 for ; Thu, 1 Oct 2020 22:36:41 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (mail.geeks.org [IPv6:2001:4980:3333:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4C2SfJ6WXtz3Xyg for ; Thu, 1 Oct 2020 22:36:40 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (localhost [127.0.0.1]) by after-clamsmtpd.geeks.org (Postfix) with ESMTP id B0CD13584A for ; Thu, 1 Oct 2020 17:36:33 -0500 (CDT) Received: by mail.geeks.org (Postfix, from userid 1003) id 896A035849; Thu, 1 Oct 2020 17:36:33 -0500 (CDT) Date: Thu, 1 Oct 2020 17:36:33 -0500 From: Doug McIntyre To: FreeBSD Subject: Re: freebsd-update strange message Message-ID: <20201001223633.GA18036@geeks.org> References: <7a0caa40-1021-5c03-cea0-2f9ba8fd9dd6@rail.eu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7a0caa40-1021-5c03-cea0-2f9ba8fd9dd6@rail.eu.org> X-Virus-Scanned: ClamAV using ClamSMTP X-Rspamd-Queue-Id: 4C2SfJ6WXtz3Xyg X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of merlyn@geeks.org designates 2001:4980:3333:1::1 as permitted sender) smtp.mailfrom=merlyn@geeks.org X-Spamd-Result: default: False [-2.66 / 15.00]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.93)[-0.927]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; DMARC_NA(0.00)[geeks.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.93)[-0.934]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.50)[-0.503]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7753, ipnet:2001:4980::/32, country:US]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Oct 2020 22:36:41 -0000 On Thu, Oct 01, 2020 at 08:20:03AM +0200, Erwan David wrote: > My freebsd-update cron gives me the following-message : > > Looking up update.FreeBSD.org mirrors... 3 mirrors found. > Fetching metadata signature for 11.3-RELEASE from update4.freebsd.org... > done. > Fetching metadata index... done. > Inspecting system... done. > Preparing to download files... done. > The following files are affected by updates. No changes have > been downloaded, however, because the files have been modified > locally: > /var/db/mergemaster.mtree > > No updates needed to update system to 11.3-RELEASE-p14. > > WARNING: FreeBSD 11.3-RELEASE-p13 HAS PASSED ITS END-OF-LIFE DATE. > Any security issues discovered after Wed Sep 30 02:00:00 CEST 2020 > will not have been corrected. > > I am running 11.3-RELEASE-p14, but it still has 11.3-RELEASE-p13 kernel > > What should I do ? (I did not touch to /var/db/mergemaster.mtree other > concern) Upgrade to FreeBSD 11.4-RELEASE now that 11.3-RELEASE has gone end-of-life. (3 months after the release of 11.4).