From nobody Fri Jul 10 16:36:00 2026 X-Original-To: freebsd-pkgbase@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4gxcsR15B4z6lNX1 for ; Fri, 10 Jul 2026 16:36:11 +0000 (UTC) (envelope-from the.lists@mgm51.com) Received: from oneyou.mgm51.net (oneyou.mgm51.net [IPv6:2607:f2f8:af30::100]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (secp384r1) client-digest SHA384) (Client CN "oneyou.mgm51.net", Issuer "Mike's Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4gxcsQ2yHPz3Nx0 for ; Fri, 10 Jul 2026 16:36:10 +0000 (UTC) (envelope-from the.lists@mgm51.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=mgm51.com header.s=mgm51.com-10 header.b=QjAAD8uL; spf=pass (mx1.freebsd.org: domain of the.lists@mgm51.com designates 2607:f2f8:af30::100 as permitted sender) smtp.mailfrom=the.lists@mgm51.com; dmarc=pass (policy=reject) header.from=mgm51.com Received: from sentry.mgm51.net (sentry.mgm51.net [IPv6:2001:558:6017:e3:1130:5cc5:3dee:2458]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "sentry.mgm51.net", Issuer "Mike's Certificate Authority" (verified OK)) by oneyou.mgm51.net (Postfix) with ESMTPS id 4gxcsF5twpzHh0t for ; Fri, 10 Jul 2026 12:36:01 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mgm51.com; s=mgm51.com-10; t=1783701361; bh=lpJKeUR6uv0IFWOX4g31oiTtbdgU1DpaEKVM6z4EEig=; h=Date:Subject:From; b=QjAAD8uLwvhaAph5iNLNCyxNrEIHdvWKIICOmjKDImociifjzLnsnSINNhDUqy3CW blRCvxajmnxg4UZGwCERT4oWEHDk/FpEVRsXBvj9Xy69NaZ8TmrBgh6k3+AlTvdUCh O3xOGIwdrCnIg9XwX3fIFQDU3+fBUWLbv2hl62Y5wJV9dTxVsHmKvo8qKRyoFdClYJ h9RLLxZG8TrtrFDr7YDnSksvSWabTmbreRKYeFy+tz4HyJIiIt9mDHQwXCvf9NQ1lg cGe2VJ7r63niMtauUCREi5lZiEOTkXLWEiZiTAQXh/9IqGs/brKN1MrjS0o6zMIaV2 n4G9VdioSO9hg== Received: from [10.11.2.100] (bigbloat.24cl.home [10.11.2.100]) by sentry.mgm51.net (Postfix) with ESMTP id 4gxcsD51WyzRcpy for ; Fri, 10 Jul 2026 12:36:00 -0400 (EDT) Message-ID: <2ef5ceae-791f-486a-bc5a-504dc4a97f61@mgm51.com> Date: Fri, 10 Jul 2026 12:36:00 -0400 List-Id: Packaging the FreeBSD base system List-Archive: https://lists.freebsd.org/archives/freebsd-pkgbase List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkgbase@FreeBSD.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: pkg upgrade yields conflicts in message To: freebsd-pkgbase@FreeBSD.org References: <62849618-c9b7-4310-8555-cf7a91e4af9d@mgm51.com> <4e9a04c9-512c-44c0-8e0c-3da2704da608@yahoo.com> Content-Language: en-US From: Mike In-Reply-To: <4e9a04c9-512c-44c0-8e0c-3da2704da608@yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-6.00 / 15.00]; DWL_DNSWL_MED(-2.00)[mgm51.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; DMARC_POLICY_ALLOW(-0.50)[mgm51.com,reject]; R_SPF_ALLOW(-0.20)[+ip6:2607:f2f8:af30::100]; R_DKIM_ALLOW(-0.20)[mgm51.com:s=mgm51.com-10]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:25795, ipnet:2607:f2f8::/32, country:US]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-pkgbase@freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-pkgbase@FreeBSD.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[mgm51.com:+] X-Rspamd-Queue-Id: 4gxcsQ2yHPz3Nx0 X-Spamd-Bar: ----- On 6/27/2026 12:37 AM, Mark Millard wrote: > On 6/26/26 15:54, Mike wrote: >> OK, I have a 15.1 test system, loaded with FreeBSD 15.1 AMD from a mem img. >> >> >> I went through the install, which went well. >> >> Then I loaded the ports pkgs I usually use, which also went well. >> >> >> Now, when I run >>     pkg upgrade >> as I had usually done to see if there were any updates to the ports pkgs >> I had installed, I see the following ... >> >> ==================== >> >> Updating FreeBSD-ports repository catalogue... >> FreeBSD-ports repository is up to date. >> Updating FreeBSD-ports-kmods repository catalogue... >> FreeBSD-ports-kmods repository is up to date. >> Updating FreeBSD repository catalogue... >> FreeBSD repository is up to date. >> All repositories are up to date. >> Checking for upgrades (15 candidates): .......... done >> Processing candidates (15 candidates): .... done >> Checking integrity... done (9 conflicting) >>   - libcdb-g2020082801 [FreeBSD-ports] conflicts with tinycdb-0.81 >> [installed] on /usr/local/lib/libcdb.a > > One of the Makefiles is explicit about it: > > # grep -r CONFLICT /usr/ports/*/*cdb/Makefile > /usr/ports/databases/tinycdb/Makefile:CONFLICTS_INSTALL= libcdb # > lib/libcdb.a > >>   - gcc14-14.2.0_4 [FreeBSD-ports] conflicts with gcc14- >> devel-14.3.1.s20260327,1 [installed] on /usr/local/bin/c++14 >>   - gcc14-14.2.0_4 [FreeBSD-ports] conflicts with gcc14- >> devel-14.3.1.s20260327,1 [FreeBSD-ports] on /usr/local/bin/c++14 >>   - gcc13-13.3.0_3 [FreeBSD-ports] conflicts with gcc13- >> devel-13.4.1.s20260326 [installed] on /usr/local/bin/c++13 >>   - gcc13-13.3.0_3 [FreeBSD-ports] conflicts with gcc13- >> devel-13.4.1.s20260326 [FreeBSD-ports] on /usr/local/bin/c++13 >>   - gcc12-devel-12.4.1.s20250702 [FreeBSD-ports] conflicts with >> gcc12-12.4.0_3 [installed] on /usr/local/bin/c++12 >>   - gcc12-devel-12.4.1.s20250702 [FreeBSD-ports] conflicts with >> gcc13-13.3.0_3 [FreeBSD-ports] on /usr/local/include/libgccjit++.h >>   - gcc12-devel-12.4.1.s20250702 [FreeBSD-ports] conflicts with gcc13- >> devel-13.4.1.s20260326 [installed] on /usr/local/include/libgccjit++.h >>   - gcc12-devel-12.4.1.s20250702 [FreeBSD-ports] conflicts with gcc13- >> devel-13.4.1.s20260326 [FreeBSD-ports] on /usr/local/include/libgccjit++.h > > Some lang/gcc* vs. lang/gcc*-devel conflicts are not new and are > documented in the Makefiles: > > # grep -r CONFLICT /usr/ports/lang/gcc*/Makefile > /usr/ports/lang/gcc12-devel/Makefile:CONFLICTS= gcc12 > /usr/ports/lang/gcc12/Makefile:CONFLICTS= gcc12-devel > /usr/ports/lang/gcc13-devel/Makefile:CONFLICTS= gcc13 > /usr/ports/lang/gcc13/Makefile:CONFLICTS= gcc13-devel > /usr/ports/lang/gcc14/Makefile:CONFLICTS= gcc14-devel > /usr/ports/lang/gcc15/Makefile:CONFLICTS= gcc15-devel > /usr/ports/lang/gcc16/Makefile:CONFLICTS= gcc16-devel > > (Looks like lang/gcc[456]-devel do not document that other direction for > the conflicts. and 12-devel and 13 did document their conflict status.) > > However, if I understand right, modern pkg has gotten better at > detecting and reporting conflicts, with an example file as well more of > the time, even when the Makefiles are not explicit. > >> Checking integrity... done (0 conflicting) >> Your packages are up to date. >> >> ========================================== >> >> >> A comment ... >> >> I dislike seeing the word "conflicting" in the routine commands I run. >> >> What did I do incorrectly? > > Looks like no 2 installs conflict with each other. I'm not sure that you > did anything incorrectly.Mostly you have -devel installs for gcc* but > one of them is not: gcc12-12.4.0_3 [installed] . Is that as you intended? > > Is that as you intended? I didn't change any of the options to use -devel installs. I suspect it was done by one of the pkgs I installed. That's why I asked. So far, everything on the test server has been running as expected, in spite of those conflicts. But it is a minimal-usage server. So I'll just go along with them for now. However, I may have a higher level of concern when it comes to moving my two production servers over to the pkg install system when (if) such conflicts continue to occur with generic pkg installs. Thanks for your explanation. And I apologize for taking so long to get back to you. Life happened. :)