From owner-freebsd-questions@FreeBSD.ORG Thu Mar 18 02:02:19 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4039F106564A for ; Thu, 18 Mar 2010 02:02:19 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id C0D028FC12 for ; Thu, 18 Mar 2010 02:02:18 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Ns53x-0002AQ-Lm for freebsd-questions@freebsd.org; Thu, 18 Mar 2010 03:02:17 +0100 Received: from pool-68-239-68-178.res.east.verizon.net ([68.239.68.178]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 18 Mar 2010 03:02:17 +0100 Received: from nightrecon by pool-68-239-68-178.res.east.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 18 Mar 2010 03:02:17 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Followup-To: gmane.os.freebsd.questions Date: Wed, 17 Mar 2010 22:01:50 -0400 Lines: 76 Message-ID: References: <510299.56442.qm@web111601.mail.gq1.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: pool-68-239-68-178.res.east.verizon.net Subject: Re: How do I fix the broken python26 port in 7.2-RELEASE ? 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: Thu, 18 Mar 2010 02:02:19 -0000 George Sanders wrote: > Virgin 7.2-RELEASE install. > > I run: > > csup -h cvsup4.freebsd.org -i ports/lang/python26 -g -L 2 > /usr/share/examples/cvsup/ports-supfile ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > and now I have a /usr/ports/lang/python26/distinfo that looks like: > > MD5 (python/Python-2.6.4.tgz) = 17dcac33e4f3adb69a57c2607b6de246 > SHA256 (python/Python-2.6.4.tgz) = > 1a25a47506e4165704cfe2b07c0a064b0b5762a2d18b8fbdad5af688aeacd252 SIZE > (python/Python-2.6.4.tgz) = 13322131 This looks like mine. > Perfect. I'll just do a 'make install' and ... > > # make install > ===> Vulnerability check disabled, database not found > ===> Found saved configuration for python26-2.6.4 > => Python-2.6.1.tgz is not in /usr/ports/lang/python26/distinfo. This is the wrong distfile. > => Either /usr/ports/lang/python26/distinfo is out of date, or > => Python-2.6.1.tgz is spelled incorrectly. > *** Error code 1 > > Stop in /usr/ports/lang/python26. > *** Error code 1 > > Stop in /usr/ports/lang/python26. > > > I have no idea how to make this work. I grepped everywhere for both > "Python-2.6.1.tgz" and "python26-2.6.4" in an attempt to change them by > hand, but I cannot find a single file in my filesystem that contains those > strings, so I have no idea where the ports tree is getting this > information. > > This was not an odd or non-standard operation - what am I doing wrong ? > I believe something in your juxtaposition of commands in your command line above [near beginning of post] has produced an out of order and munged path. I haven't built the python26 port anytime recently, but have several django related things running fine under it. What I do is csup the ports tree by itself (not trying to do it at the same time on the same command line as the build). I keep my csup housekeeping and supfiles in /usr/sup so I just cd /usr/sup and csup -L 2 ports where my 'ports' file simply contains: *default host=cvsup.nl.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix compress ports-all After the ports tree refresh is finished then I install software by changing to the appropriate port directory and do the usual make && make install && make clean dance. I also use portupgrade so there are additional embellishments for use in an update/upgrade scenario. Try separating the steps, ala do the ports tree refresh to completion first, then attempt to install the port. -Mike