From owner-freebsd-questions@FreeBSD.ORG Sun Mar 12 13:51:35 2006 Return-Path: X-Original-To: freebsd-questions@FreeBSD.org 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 3477516A400; Sun, 12 Mar 2006 13:51:35 +0000 (GMT) (envelope-from nork@FreeBSD.org) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 863C443D45; Sun, 12 Mar 2006 13:51:34 +0000 (GMT) (envelope-from nork@FreeBSD.org) Received: from nadesico.ninth-nine.com (nadesico.ninth-nine.com [219.127.74.122]) by sakura.ninth-nine.com (8.13.4/8.13.4/NinthNine) with ESMTP id k2CDpWxA057472; Sun, 12 Mar 2006 22:51:33 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Sun, 12 Mar 2006 22:51:32 +0900 From: Norikatsu Shigemura To: gerard@seibercom.net Message-Id: <20060312225132.a66b9005.nork@FreeBSD.org> In-Reply-To: <200603120830.56438.gerard@seibercom.net> References: <20060310173657.Q40614@seibercom.net> <20060311153759.41c98e18.nork@FreeBSD.org> <20060311234731.GA91232@over-yonder.net> <200603120830.56438.gerard@seibercom.net> X-Mailer: Sylpheed version 2.2.0 (GTK+ 2.8.12; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (sakura.ninth-nine.com [219.127.74.121]); Sun, 12 Mar 2006 22:51:33 +0900 (JST) Cc: ports@FreeBSD.org, freebsd-questions@FreeBSD.org, fullermd@over-yonder.net, nork@FreeBSD.org Subject: Re: Unable to build or update vcdimager X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Mar 2006 13:51:35 -0000 On Sun, 12 Mar 2006 08:30:55 -0500 Gerard Seibert wrote: > > > SEE ALSO: http://www.freebsd.org/cgi/query-pr.cgi?pr=93916 > > I got a similar error from dirmngr. It seems like the program > > installs its own INFO files, then the port tries to install INFO > > again (note the --quiet; that only appears in the bsd.port.mk > > version, not in the port's makefiles). I hacked around it by just > > using "make -k install" to make it ignore the error. > Would it be possible or feasible to remove these 'INFO' files manually > prior to building and installing or updating this port? I have never > undertaken a procedure like this before so I am unsure of its > requirements or success rate. Yes, I'm waiting for portmgr's approval. I'll commit with following message. Index: UPDATING =================================================================== RCS file: /home/ncvs/ports/UPDATING,v retrieving revision 1.294 diff -u -r1.294 UPDATING --- UPDATING 7 Mar 2006 18:50:37 -0000 1.294 +++ UPDATING 12 Mar 2006 06:00:31 -0000 @@ -6,6 +6,29 @@ time you update your ports collection, before attempting any port upgrades. +20060312: + AFFECTS: users of multimedia/vcdimager and security/dirmngr + AUTHOR: nork@FreeBSD.org + + These versions of the ports which have been installed in + your system accidentally installed some malformed entries + to $PREFIX/info/dir, which prevent them from being upgraded + to the latest versions. Please remove the following entries + manually from $PREFIX/info/dir before upgrading them to + vcdimager-0.7.23_2 (and later) and dirmngr-0.9.3_2 (and later) + respectively. + + multimedia/vcdimager + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + * vcd-info: (vcdimager)vcd-info. Video CD diagnostic tool + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + security/dirmngr + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + * dirmngr: (gnupg). X.509 CRL and OCSP server. + * dirmngr-client: (gnupg). X.509 CRL and OCSP client. + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + 20060307: AFFECTS: users of print/acroread7 and the localized versions AUTHOR: hrs@FreeBSD.org