From owner-freebsd-questions@FreeBSD.ORG Thu Jun 19 19:23:17 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FC1C37B401 for ; Thu, 19 Jun 2003 19:23:17 -0700 (PDT) Received: from ratchet.nebcorp.com (ratchet.nebcorp.com [205.217.153.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2F6243F75 for ; Thu, 19 Jun 2003 19:23:16 -0700 (PDT) (envelope-from ardent@nebcorp.com) Received: by ratchet.nebcorp.com (Postfix, from userid 1001) id AEA993A274; Thu, 19 Jun 2003 19:23:16 -0700 (PDT) Date: Thu, 19 Jun 2003 19:23:16 -0700 From: "Rev. Joe Doyle Ardent" To: freebsd-questions@freebsd.org Message-ID: <20030620022316.GA52638@nebcorp.com> Mail-Followup-To: "Rev. Joe Doyle Ardent" , freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: Strange formatting error with pkg_info after using portupgrade X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Rev. Joe Doyle Ardent" List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jun 2003 02:23:17 -0000 Hello, everyone, I have a fairly strange error, that has popped up on both machines where I have used portupgrade (both 4.8-RELEASE boxes). Here is an example output: please:~> pkg_info |head BitTorrent-3.2.1b "Peer to Peer file sharing/mirroring."Mesa-3.4.2_2 A graphics library similar to SGI's OpenGL ORBit-0.5.17 High-performance CORBA ORB with support for the C language XFree86-4.3.0,1 X11/XFree86 core distribution (complete, using mini/meta-po Note how Mesa's entry begins immediately after the last character of BitTorrent's. The behavior seems to be that if a package has been installed/upgraded with portupgrade, it eliminates the terminal newline from the pkg_info listing. Running pkg_info with a particular package as an argument works fine. pkgdb reports that the database is uncorrupted and up-to-date. The only effect seems to be this fairly annoying display bug, but nothing that is impairing the functionality of the system in a serious way. Thank you in advance for any help/insights/hints. Have a good day. -Joe