From owner-freebsd-questions@FreeBSD.ORG Tue Sep 16 17:35:40 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B10A4C0C for ; Tue, 16 Sep 2014 17:35:40 +0000 (UTC) Received: from mout.gmx.com (mout.gmx.com [74.208.4.200]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 633B1E0 for ; Tue, 16 Sep 2014 17:35:40 +0000 (UTC) Received: from [192.168.1.65] ([172.15.184.248]) by mail.gmx.com (mrgmxus001) with ESMTPSA (Nemesis) id 0Lp49C-1XzxwX1fCG-00ew0s for ; Tue, 16 Sep 2014 19:30:29 +0200 Message-ID: <54187425.5000003@gmx.us> Date: Tue, 16 Sep 2014 13:32:21 -0400 From: Dutch Ingraham User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.8.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Issue with Ports v. Packages Versioning Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:bww7OrvGA75pIOgrpMbPSKGSiUAC9dhXYeknbBAwJaFRnPhSxLd 7zqhUb3U2fLYDhDvgltzdIphNXZzj8hdaoPyp5Jt6lWWNZQhOMJp/FfUdsH2nT9JkpUJgK+ 3RGuLkzBTxRegdJANDV8vPbl/o/95GcHIygcYCnNUoDkMSD0BuvSCeSoBo6J813sDDLvLpK 2UnA5q49oyciYY94K7EyA== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 17:35:40 -0000 (Sorry if this is a re-post - I got a bounce.) Greetings: I have two desktop units both running FreeBSD 10.0-RELEASE from the same ISO. On one, ports are updated with svn (I'll refer to it as the SVN unit) and the other uses portsnap (the PORTSNAP unit). I update both daily. On Sept. 12, the update to the SVN unit borked xorg so that if I open any x-application in my window manager (dwm), except xterm, the server crashes with a segfault. While trying to diagnose this issue, I switched daily use to the PORTSNAP unit. After a few days of fetching/updating and portmaster telling me there were no updates, I started looking at ports versus package versions. Also thrown into the mix was an update to the base system, to p9. On the PORTSNAP unit: root@stoa:~ # pkg version -l "<" dri-7.6.1_5,2 < libGL-7.6.1_5 < libdrm-2.4.17_2,1 < xf86-video-ati-6.14.6_4 < xf86-video-intel-2.7.1_9 < xorg-server-1.7.7_14,1 < but: root@stoa:~ # portmaster -ad ===>>> Gathering distinfo list for installed ports ===>>> Starting check of installed ports for available updates ===>>> All ports are up to date root@stoa:~ # root@stoa:~ # freebsd-version -ku 10.0-RELEASE-p7 10.0-RELEASE-p8 root@stoa:~ # I have the same versions and portmaster result on the SVN unit. Googling around brought me to this[1] exchange, which reflects my understanding that WITH_NEW_XORG was only necessary on pre-10.0 versions. (The Makefiles for the above ports, and the UPDATING file from April 2014 seems to indicate this is the problem.) If WITH_NEW_XORG is not the issue, could someone describe what may be the problem? If it is the issue, is the solution as easy as adding that to make.conf and updating? I don't know if this is what borked the SVN unit, but I would like to work out this issue first, then go from there. (I've already rebuilt all xf86- drivers and, when that failed to correct the issue, rebuilt all 570 ports, which also failed to solve the problem, so I'm pretty much out of ideas anyway.) In addition, are differing patch verrsions in base correct? Any/all help is appreciated. [1]http://freebsd.1045724.n5.nabble.com/HEADS-UP-WITH-NEW-XORG-is-now-\ the-default-on-FreeBSD-10-and-9-stable-td5904196.html#a5904376