From owner-freebsd-x11@FreeBSD.ORG Wed Apr 1 21:22:52 2015 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 68FA1E33; Wed, 1 Apr 2015 21:22:52 +0000 (UTC) Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 219C5C7B; Wed, 1 Apr 2015 21:22:52 +0000 (UTC) Received: by qcbii10 with SMTP id ii10so30164009qcb.2; Wed, 01 Apr 2015 14:22:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=U0/fxgceCyXRLwwkMiDaFtCb3DCvycxGsU3tGGS5RpI=; b=tpfg0npD/XuhgE+hNOgWiZn2YduuwnvZjOPivsLffh30MSvVBmPEEe8+mhlqOFKNyf s/B+lBq3e1TlSFkF2Itx1vq6ClbP2dQ+zjZLVmPgwEyonLrkGtQnyVMISPlWcwUzGm7H S9N2+b6LFNGWbrMhFt2NxS/SfnorVZxDtRt5WpUNlbYrQVL9ZXws+ifavOvlEtkzywsj d0N72/5XgOXPnA9SD76BJoyS+fwviQaxW2/KvzDzXJNUsY0dygFp0Abml0//O0gx+y9P RSD4csbByNaPObqeCvsBYhXhypStREGswNBeulCkOn7MNcjukihb1THO0/uUVcP5ZVKZ OojA== MIME-Version: 1.0 X-Received: by 10.141.18.146 with SMTP id u140mr57531585qhd.48.1427923371306; Wed, 01 Apr 2015 14:22:51 -0700 (PDT) Received: by 10.229.125.195 with HTTP; Wed, 1 Apr 2015 14:22:51 -0700 (PDT) In-Reply-To: References: <551C036B.2010806@rainbow-runner.nl> Date: Wed, 1 Apr 2015 23:22:51 +0200 Message-ID: Subject: Re: libdrm 2.4.58 upgrade fails From: Torfinn Ingolfsen To: FreeBSD Ports ML Content-Type: text/plain; charset=UTF-8 Cc: x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 21:22:52 -0000 On Wed, Apr 1, 2015 at 10:52 PM, Torfinn Ingolfsen wrote: > Update, > > > Furthermore, how do I rebuiuld all these ports? They all refer to > (have as dependency) the libdrm port, and therefore fail when I try to > portupgrade them. I figured it out; I had to rebuild a few (about a handful) ports one by one (without upgrading dependencies, ie. 'portupgrade portname'), until I could successfully upgrade the libdrm port. "normal" portupgrade works now (it is still portupgrading, but it looks much better now). Thanks! -- Regards, Torfinn