From owner-freebsd-pkg@FreeBSD.ORG Thu Apr 3 16:35:09 2014 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0EB4DF79; Thu, 3 Apr 2014 16:35:09 +0000 (UTC) Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D1F271EA; Thu, 3 Apr 2014 16:35:08 +0000 (UTC) Received: by mail-pa0-f49.google.com with SMTP id lj1so2098843pab.22 for ; Thu, 03 Apr 2014 09:35:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=fT0HEQZEUHbDKo4GJOVk0rYwxt+Ufj0lmQNznRED3Ts=; b=aFRAo6hmX1JuespIbzhlU6m4T3EDjnQUYX2fqk11qdFzzGHxRUpDhoREytePJSgJ0Z ziUjKodQTCYp7TUTy+mBtj7qs9BwhAzEupeKujw/xxJFPPgk6On4XHGCgT+USMo7Jq0D YCUT/qBigQ6D8oIMPkN+DV0k4t7AibSFTWMBnQ4FnqSyfXEz0Xk57e3iWyda1tg/+qz2 VsPC2TbGh4YdA0gcpCANeGoQtoJLBbpW9Y2kuk8IRU3Fpk04ALuzSkI8zDyfWPSrWjuf 8bLbgPgc777dMVw9hw/XdHLrH3DUaWJRhOCpCK/QFua+dfXzvVcmrEOtdbsEeHd8Xavs ZQMA== X-Received: by 10.66.119.172 with SMTP id kv12mr8845534pab.34.1396542907942; Thu, 03 Apr 2014 09:35:07 -0700 (PDT) Received: from [10.10.21.169] (otra.opentable.com. [199.16.144.7]) by mx.google.com with ESMTPSA id bz4sm12212447pbb.12.2014.04.03.09.35.04 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 03 Apr 2014 09:35:04 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: Installing bacula-server with PostgreSQL 9.2 From: Steven Schlansker In-Reply-To: <533CF8EB.7090403@FreeBSD.org> Date: Thu, 3 Apr 2014 09:35:03 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <6534BBBF-4D98-4FCB-A9AC-4564B0373E08@gmail.com> References: <413DCEA9-DE6D-4834-B9F1-6C08C7BE5F2C@likeness.com> <533CF8EB.7090403@FreeBSD.org> To: Matthew Seaman X-Mailer: Apple Mail (2.1874) Cc: freebsd-pkg@freebsd.org X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2014 16:35:09 -0000 On Apr 2, 2014, at 11:00 PM, Matthew Seaman wrote: > On 03/04/2014 02:11, Steven Schlansker wrote: >> [steven@d0028:~]% sudo pkg install -f bacula-server >> Updating repository catalogue >> The following 2 packages will be installed: >>=20 >> Installing postgresql90-client: 9.0.17 >> Installing bacula-server: 5.2.12_3 >>=20 >> The installation will require 11 MB more space >>=20 >> Oh no! I=92m running postgresql92-client! >=20 > The dependency on postgresql90 is "baked into" the compiled package, = and > it is not possible to use that package with a different version of > postgresql. Apart from anything else, any binaries are linked against > the specific ABI versions of shlibs provided by the postgresql client > package. 'pkg set -o' is not an answer in this case, That=92s very unfortunate! I would expect a binary built against libpq = 9.0 to work fine when linked with libpq 9.3, but can=92t say that I know = exactly how good PostgreSQL is about binary compatibility. >=20 > If you want to use a different version of postgresql, then you're = going > to have to compile anything that links against the postgresql shlibs > yourself (ie. that depends on postgresql90-client). That would be okay if a little unfortunate, except the port seems broken = in 10.0-R as well :( make[3]: don't know how to make /usr/include/openssl/pq_compat.h. Stop make[3]: stopped in = /usr/ports/sysutils/bacula-server/work/bacula-5.2.12/src/cats *** Error code 1 Stop. make: stopped in /usr/ports/sysutils/bacula-server > It is possible to > run your own repo with just stuff that depends on postgresql and pull > down anything else from pkg.FreeBSD.org, but you will find your local > repo ends up containing more than locally built pkgs than is strictly > necessary -- ie. everything that those postgresql consuming pkgs = depend > upon, even if those dependencies are themselves completely independent > of postgresql.