From owner-freebsd-stable@FreeBSD.ORG Thu Dec 20 23:55:57 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7B1F1B75; Thu, 20 Dec 2012 23:55:57 +0000 (UTC) (envelope-from b.smeelen@ose.nl) Received: from mail.ose.nl (mail.ose.nl [212.178.134.164]) by mx1.freebsd.org (Postfix) with ESMTP id CA0488FC0A; Thu, 20 Dec 2012 23:55:56 +0000 (UTC) X-Footer: b3NlLm5s Received: from localhost ([127.0.0.1]) by mail.ose.nl (using TLSv1/SSLv3 with cipher AES256-SHA (256 bits)); Fri, 21 Dec 2012 00:55:54 +0100 Message-ID: <50D3A58A.3020002@ose.nl> Date: Fri, 21 Dec 2012 00:55:54 +0100 From: Bas Smeelen User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Matthew Seaman Subject: Re: Will we get a RELEASE-9.1 for Christmas? References: <201212090318.UAA11257@lariat.net> <50C412F6.7040300@sdf.org> <201212090526.26535.lumiwa@gmail.com> <50C8CF77.2040102@FreeBSD.org> <50C975B3.7070701@FreeBSD.org> <50C991F3.3040307@freebsd.org> <50D3A1E3.6090408@FreeBSD.org> In-Reply-To: <50D3A1E3.6090408@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2012 23:55:57 -0000 On 12/21/12 00:40, Matthew Seaman wrote: > On 13/12/2012 08:29, Matthew Seaman wrote: > > (On 'pkg check -Ba' producing 'shared library not found' errors for some > packages) > >> Unfortunately it seems to be a fairly common effect in some large >> projects. Other packages showing the same symptoms: >> >> thunderbird (yeah -- that one was predictable...) >> openjdk6 >> virtualbox-ose >> >> ... and that's just out of what's installed on my desktop: by no means >> comprehensive. As far as I can tell from a quick check, openjdk6 >> doesn't rely on setting LD_LIBRARY_PATH in the environment. >> >> I've raised issue #403 in pkgng Github. > I've just finished committing fixes for this problem to the master and > release-1.0 branches in Github. If anyone is feeling enthusiastic and > would like to try pulling those sources and confirming that their > favourite packages no longer generate scads of nasty errors when > re-analysing shlib dependencies, I'd be grateful. > > Cheers, > > Matthew > > PS. If you're running pkg-1.0.3, I recommend you pull down the > release-1.0 branch for these tests. While you could upgrade to 1.1.a1 > from master, that involves various local.sqlite DB schema changes which > will be tedious to unwind should you want to revert to the released > version. > I would like to. But just getting used to svn and other new things since simple csup and friends. How do I pull it? I have pkg-1.0.3_1 on a machine building packages for my laptop right now.