From owner-freebsd-questions@FreeBSD.ORG Wed Oct 18 12:19:40 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 3E9EE16A403 for ; Wed, 18 Oct 2006 12:19:40 +0000 (UTC) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7BDE43D6D for ; Wed, 18 Oct 2006 12:19:39 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from db2.internal (db2.internal [10.202.2.12]) by frontend1.messagingengine.com (Postfix) with ESMTP id 015A5DB5684 for ; Wed, 18 Oct 2006 08:19:39 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by db2.internal (MEProxy); Wed, 18 Oct 2006 08:19:41 -0400 X-Sasl-enc: W+J9trCHrWu6aVh/dq8AV4z+TOEhIqnqQC0crP5IGf2m 1161173981 Received: from gumby.localdomain (bb-87-81-140-128.ukonline.co.uk [87.81.140.128]) by mail.messagingengine.com (Postfix) with ESMTP id 3318E7637 for ; Wed, 18 Oct 2006 08:19:41 -0400 (EDT) From: RW To: freebsd-questions@freebsd.org Date: Wed, 18 Oct 2006 13:19:28 +0100 User-Agent: KMail/1.9.4 References: <20061017064757.4C88.GERARD@seibercom.net> In-Reply-To: <20061017064757.4C88.GERARD@seibercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610181319.37551.list-freebsd-2004@morbius.sent.com> Subject: Re: Problem with Portsnap Update 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: Wed, 18 Oct 2006 12:19:40 -0000 On Tuesday 17 October 2006 11:56, Gerard Seibert wrote: > I encountered this immediately after running 'portsnap' this moring: > > /usr/sbin/pkg_version -vIL= > > py25-tkinter-2.5_1 > succeeds index (index has 2.4.3_1) > python-2.5 < needs updating (index has 2.4.3,1) > python24-2.4.3_2 < needs updating (index has 2.4.3_3) > python25-2.5 > > > 'python-2.5' does not even appear to exist in the ports tree. > 'py25-tkinter-2.5_1' also seems to have a problem. Is there something > wrong with this mornings portsnap update? The lang/python port was updated to python 2.5 and then reverted to 2.4 after compatability problems were found.