Date: Fri, 26 Jun 2026 21:37:39 -0700 From: Mark Millard <marklmi@yahoo.com> To: Mike <the.lists@mgm51.com>, freebsd-pkgbase@FreeBSD.org Subject: Re: pkg upgrade yields conflicts in message Message-ID: <4e9a04c9-512c-44c0-8e0c-3da2704da608@yahoo.com> In-Reply-To: <62849618-c9b7-4310-8555-cf7a91e4af9d@mgm51.com>
index | next in thread | previous in thread | raw e-mail
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? > > thx. > > > > -- === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e9a04c9-512c-44c0-8e0c-3da2704da608>