From owner-freebsd-x11@FreeBSD.ORG Tue Aug 9 17:12:32 2011 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA5D2106564A for ; Tue, 9 Aug 2011 17:12:32 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 788AE8FC16 for ; Tue, 9 Aug 2011 17:12:32 +0000 (UTC) Received: by vws18 with SMTP id 18so237813vws.13 for ; Tue, 09 Aug 2011 10:12:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=rENyUqWqLSlodJ6xb7bpgj1zgaKvK9nJS6YPaA5QbR0=; b=ftRDbriJ6e5Ah3PEw7/ltWMRJ+GmI+kYfq1Pb4liVYR/La035MjefG/Q9UHd7MUiow OnafEtMMRuqUWY8CPVZsUcoWzfcjnXkl6nzNUEN3o1cl6fA/FFn0W/FgkgffzBEPApSp czjGtu9mQbCxDc2mZNoLPu8IeGdyvL/CXMHDM= MIME-Version: 1.0 Received: by 10.52.23.52 with SMTP id j20mr6101358vdf.24.1312908168238; Tue, 09 Aug 2011 09:42:48 -0700 (PDT) Received: by 10.52.167.33 with HTTP; Tue, 9 Aug 2011 09:42:48 -0700 (PDT) In-Reply-To: References: Date: Tue, 9 Aug 2011 17:42:48 +0100 Message-ID: From: Tom Evans To: Ambrus Szabo , x11@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Subject: Re: xkeyboard-config-1.8_1 to xkeyboard-config-1.8_2 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2011 17:12:32 -0000 On Tue, Aug 9, 2011 at 5:23 PM, Kevin Oberman wrote: > On Tue, Aug 9, 2011 at 3:17 AM, Ambrus Szabo wrote: >> Hello, >> >> xkeyboard-config-1.8_1 to xkeyboard-config-1.8_2 >> >> Script "configure" failed unexpectedly > > I see this periodically and have never bothered to track down the source, but > re-installing p5-XML-Parse seems to fix it. > > Just a guess is that something didn't run cleanly in a Perl upgrade. Perhaps > something did not get updated. At a guess, user updated perl, and either upgraded major versions and didn't rebuild all ports that depend on perl as described in /usr/ports/UPDATING, section 20100715, or upgraded minor version and didn't run the perl-after-upgrade script. Cheers Tom