From owner-freebsd-questions@freebsd.org Mon Aug 13 13:09:58 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A604910722EF for ; Mon, 13 Aug 2018 13:09:58 +0000 (UTC) (envelope-from wes.frazier@members.fsf.org) Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.posteo.de", Issuer "StartCom Class 3 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2979C786AA for ; Mon, 13 Aug 2018 13:09:57 +0000 (UTC) (envelope-from wes.frazier@members.fsf.org) Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id A1B8820FDA for ; Mon, 13 Aug 2018 15:09:48 +0200 (CEST) Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 41px0C3QY1z6tm6 for ; Mon, 13 Aug 2018 15:09:47 +0200 (CEST) Reply-To: wes.frazier@members.fsf.org Subject: Re: Resolving package conflicts (pkg set -o?) To: freebsd-questions@freebsd.org References: <03EF2AAC-B928-4B82-BB14-3AF4C009E5E5@astro.gla.ac.uk> From: wes Frazier Openpgp: preference=signencrypt Autocrypt: addr=wes.frazier@members.fsf.org; prefer-encrypt=mutual; keydata= xsBNBFnkGS8BCADFsuOK5MoYG9ngr5avBVEZ3M2YWFYqhFnrnegeC6gFP7CEEEhFlAlGFRJa 2lomWr9vkG19OpxtbiJVnXfmgquN5niDm3rx00So2EmpspHIp8/mOFE7Gx8tupQcOU6kVt4A 7i3U4KF+E1adev2BzVTxLOJPoaKRsA+puHdPH8jZ1a3y0YEtvLF8UUKiSEsECrjk30fQVKEl pGwNZUk5T30zWQWEIJXdYSviCbJmbzbf8DUQbHAxfcADYbMPm83XIOo14YbBjym8owNP1zhF M8ZOOxI0tQSh8Y+5U9Yn7pCm4FbIflLAIfV2dpoqeLgjQjOUDna+bo0HaWDt1bQQtUczABEB AAHNKVdlcyBGcmF6aWVyIDx3ZXMuZnJhemllckBtZW1iZXJzLmZzZi5vcmc+wsB/BBMBCAAp BQJZ5BkvAhsDBQkCky4ABwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQFO57iiyrSi6Q KAf+Pv/4HBh7Pk/NpjwaxdwK4Sxd4kO54VwcEcNmeGKMLPqD3ctDslETRBPyzA5Uvyckn5cE 6B8CbNKPEzpRRgr0kDHT5lzoHFaaubnl5ncYe419HMs8Dk3PXpwkjZ8KMotzJFvNVaaZ7Q7X B+r4godvMkDIZAz9GDBbyHKeK/1yqWQgquWJ7vxf2wSWWE6NqqENgcXQNUp54Ay4H+r3qEhT E72xbKFycmZ9idB7bzIKaf801M3AnbiUlvLcMXenFORtqhWXFYJqv/N/io9DN0nQfBpr9Fyc h50MNG4yVw/5jAtlnr6pXbTHPfAzp3/mv1NsrpLR6cRhXU5PW+jqyqLM7M7ATQRZ5BkvAQgA vIxBTKdST8TjalLJ45i2VO6x6FiTuS7FNwhlWinbmLrVqBOyuMU7Foxbps0BSjSY0+6tGUfJ bUdnbZ4EzzrVT1lPpj86vv4ukj9n7XzggAZJopzTj66ghqmiUfrZu5K5ClQUtosxYiUtIO7z 1BRf1xC5UNmqFEWxafEk81AVr6Us9J7BbyW4SdMh2ReHF+zgSs1CSzjobCZ/sA4v5uYp1hiq V08ZLawLIQoKQQFDorwMDPuX0ZL2O6ux2pX9tI04pGem2JVfQwxgfoE1Tj47MIvftmlzJ5uC O1y9zpkPjw00AngJgHKaIb0Xe6z4dJKotbAygB2tD/EM+2QJfBZ7aQARAQABwsBlBBgBCAAP BQJZ5BkvAhsMBQkCky4AAAoJEBTue4osq0ou3+8IAI/lD29qvdz2qmN0O68h9sE3r7qaqTpq 9LNgNIeTEJ7H6EfO9xU7TnPrBEm49V7fBJZLhkpyhA1XDwXPFgnQU+1dln9zGmm5qRySY71y zVvttW0k9FffhqvJy8yekcBHi8LIJVGV+FhrNixICs0zzPquWKtlcTSYQt80zuLND6XQYHb+ 7nq80Ij2h9e1b3sZ34Ceo0fjvIogieVXdmrg6K/fWKZ+yKOx0LBI60wB9pzb0T7WjuO0svxt lq3NfAji6+fadgIyWCDPx0aJx0/+LXvxkK0+1c4E9KjqmEfRSR1fdwasqLN43eD7x465JIIv DaE+1+8RUdzR93Ym3iKR3/Y= Message-ID: Date: Mon, 13 Aug 2018 09:09:45 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Aug 2018 13:09:58 -0000 I am curious about this too. I am currently living with a conflict between lang/chicken and lang/mono over the 'csi' binary; and I would appreciate knowing what the proper solution is. On 08/12/18 14:12, Norman Gray wrote: > > Or (the same question more compactly expressed) is there a general > strategy for dealing with package conflicts, where two packages install > files at the same path? > > On 10 Aug 2018, at 18:10, Norman Gray wrote: > >> Greetings. >> >> When installing the 'ceph' package, I get an error: >> >> pkg: openldap-client-2.4.46 conflicts with openldap-sasl-client-2.4.46 >> (installs files into the same place).  Problematic file: >> /usr/local/bin/ldapadd >> >> I'm not sure how best to resolve this.  Can anyone offer advice? >> >> This happens because I've installed the openldap-sasl-client package >> in preference to openldap-client (or rather, the nss-pam-ldapd-sasl >> package installs the former rather than the latter).  I take it that >> the two packages would be broadly equivalent in function from the >> point of view of dependencies.  However I'm not sure what the real >> difference is between these two alternatives. >> >> One way of resolving this appears to be to use pkg set -o >> net/openldap24-client:net/openldap24-sasl-client, as mentioned in a >> UPDATING entry of 20121212 (I haven't tried this yet). >> >> However the pkg-set(8) manpage suggests this is deprecated, I can't >> find any way to reverse this if I mess up, and the discussion at >> suggests >> this is a rather desperate measure, in the sense that (I quote) >> 'there's no going back', and there seems to be no way to discover >> later what fixes have been applied.  That is, this sounds highly >> breakable, and pretty clearly not TRTTD. >> >> Section 4 of the handbook doesn't seem to cover this situation. >> >> I can't think of where else to look. >> >> I (vaguely) imagine I could get round this by installing ceph's >> dependencies via pkg by hand, and then building net/ceph using >> portmaster.  Though I see that that has an 'R-dep' on openldap-client, >> so that might just be a longer route to the same problem. >> >> I don't really want to build ceph from source.  I doubt that'd be hard >> to do, but it'd be annoying to maintain (and hence errorprone). >> >> I can't be the first to have this type of problem, so I expect I'm >> missing something pretty obvious. >> >> Best wishes, >> >> Norman >> >> >> --  >> Norman Gray  :  https://nxg.me.uk >> SUPA School of Physics and Astronomy, University of Glasgow, UK >