From owner-freebsd-questions@FreeBSD.ORG Fri Dec 24 01:12:13 2004 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 19B2416A4CE for ; Fri, 24 Dec 2004 01:12:13 +0000 (GMT) Received: from out003.verizon.net (out003pub.verizon.net [206.46.170.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80F1843D5C for ; Fri, 24 Dec 2004 01:12:12 +0000 (GMT) (envelope-from reso3w83@verizon.net) Received: from ringworm.mechee.com ([4.26.84.7]) by out003.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041224011211.ZHQP1106.out003.verizon.net@ringworm.mechee.com>; Thu, 23 Dec 2004 19:12:11 -0600 Received: by ringworm.mechee.com (Postfix, from userid 1001) id 88ABA2CE740; Thu, 23 Dec 2004 17:09:25 -0800 (PST) From: "Michael C. Shultz" To: "Noah" Date: Thu, 23 Dec 2004 17:09:22 -0800 User-Agent: KMail/1.7.2 References: <20041222203704.M67964@enabled.com> <200412221447.00614.reso3w83@verizon.net> <20041224003452.M17161@enabled.com> In-Reply-To: <20041224003452.M17161@enabled.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412231709.24148.reso3w83@verizon.net> X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from [4.26.84.7] at Thu, 23 Dec 2004 19:12:11 -0600 cc: questions@freebsd.org Subject: Re: portmanager fails installing apache X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2004 01:12:13 -0000 On Thursday 23 December 2004 04:43 pm, you wrote: > > Try: > > > > ls /var/db/pkg > > > > and see if you have a > > > > /var/db/pkg/apache+mod_ssl-1.3.33+2.8.22 > > > > directory, if you do then you probably ran > > > > pkg_delete apache+mod_ssl-1.3.33+2.8.22 > > > > instead of > > > > pkg_delete -f apache+mod_ssl-1.3.33+2.8.22 > > > > If you don't have that directory, then let me know, > > it will cause me to install the apache ports on my system > > in an attempt to duplicate your problem. > > > > -Mike > > thanks Mike - your recommendation fixed it - but now there is > something similar with lynx and lynx-ssl. Any clues how to get out > of this loop? > > > ---- snip ---- > > pkg_create: can't find package 'lynx-2.8.5' installed! > ------------------------------------------------ > cd /usr/ports/www/lynx; make deinstall > ===> Deinstalling for www/lynx > ===> lynx not installed, skipping > ------------------------------------------------ > cd /usr/ports/www/lynx; make reinstall > ===> Installing for lynx-2.8.5 > > ===> lynx-2.8.5 conflicts with installed package(s): > lynx-ssl-2.8.5 > > They install files into the same place. > Please remove them first with pkg_delete(1). > *** Error code 1 > > Stop in /usr/ports/www/lynx. > *** Error code 1 > > Stop in /usr/ports/www/lynx. > pmupgrade 0.2.0_3 error: make reinstall returned an error, cannot > continue typhoon# > typhoon# ls -ld /var/db/pkg/lynx* > drwxr-xr-x 2 root wheel 512 Dec 22 12:50 > /var/db/pkg/lynx-ssl-2.8.5 typhoon# pkg_delete lynx-ssl-2.8.5 > pkg_delete: package 'lynx-ssl-2.8.5' is required by these other > packages and may not be deinstalled: > imp-3.2.6 > kronolith-1.1.2 > wv-1.0.0_2 > typhoon# > typhoon# portmanager -u pkg_delete -f lynx-ssl-2.8.5 and rerun portmanager, don't forget the "-f". Basically portmanager needs the lynx-ssl-2.8.5 package out of the way so it can get lynx-2.8.5 installed, but when you just run pkg_delete lynx-ssl-2.8.5 with no "-f" it does not get removed because imp-3.2.6, kronolith-1.1.2, and wv-1.0.0_2 were built with lynx-ssl-2.8.5 originally and still need it installed. After you "force" the removal of lynx-ssl-2.8.5 with the "-f" switch portmanager should end up rebuilding imp-3.2.6, kronolith-1.1.2, and wv-1.0.0_2 with lynx-2.8.5 instead of lynx-ssl-2.8.5 and all of that mess of ports should be happy once again because in the end they will all have a matching dependency of lynx-2.8.5 instead of lynx-ssl-2.8.5. I upgraded portmanager recently so the output during portmanager -u is a little easier to follow, whenever the FreeBSD folks get around to commiting the new version I am hoping it will be easier for you to follow what is going on. -Mike