From owner-freebsd-current@FreeBSD.ORG Fri Nov 21 15:42:16 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3871D16A4CE for ; Fri, 21 Nov 2003 15:42:16 -0800 (PST) Received: from marklar.blazingdot.com (marklar.blazingdot.com [207.154.84.83]) by mx1.FreeBSD.org (Postfix) with SMTP id 2FA3943FE3 for ; Fri, 21 Nov 2003 15:42:13 -0800 (PST) (envelope-from marcus@blazingdot.com) Received: (qmail 92462 invoked by uid 503); 21 Nov 2003 23:42:12 -0000 Date: Fri, 21 Nov 2003 15:42:12 -0800 From: Marcus Reid To: freebsd-current@freebsd.org Message-ID: <20031121234212.GA91890@blazingdot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Coffee-Level: nearly-fatal User-Agent: Mutt/1.5.4i Subject: Vinum breakage - please update UPDATING X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2003 23:42:16 -0000 X-List-Received-Date: Fri, 21 Nov 2003 23:42:16 -0000 Hello, I just upgraded a -CURRENT box this afternoon to discover that vinum is broken. If I hadn't done dumps of my working world beforehand I would be in pretty sad shape. Should UPDATING make note of this breakage? It would have saved me some embarassment, and I'm sure others are about to clobber their machines. Marcus