Date: Mon, 2 Mar 2026 13:01:12 -0800 From: Mark Millard <marklmi@yahoo.com> To: Vladimir Druzenko <vvd@freebsd.org>, Baptiste Daroussin <bapt@FreeBSD.org> Cc: dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org Subject: Re: git: 513318c5d748 - main - ports-mgmt/pkg: update to 2.6.0 Message-ID: <ba59c759-c57a-49d0-b1a9-1fffd95cc8e1@yahoo.com> In-Reply-To: <9c9fa1eb-29fa-4d5d-a385-f7c134ff82ea__14776.0348556162$1772479823$gmane$org@freebsd.org> References: <69a5c6d9.3c55e.b9459b1@gitrepo.freebsd.org> <9c9fa1eb-29fa-4d5d-a385-f7c134ff82ea__14776.0348556162$1772479823$gmane$org@freebsd.org>
index | next in thread | previous in thread | raw e-mail
On 3/2/26 11:30, Vladimir Druzenko wrote: > Hello! > > 02.03.2026 20:20, Baptiste Daroussin пишет: >> The branch main has been updated by bapt: >> >> URL: https://cgit.FreeBSD.org/ports/commit/? >> id=513318c5d7487c5d47a91651bfbe8e08edc3ff42 >> >> commit 513318c5d7487c5d47a91651bfbe8e08edc3ff42 >> Author: Baptiste Daroussin <bapt@FreeBSD.org> >> AuthorDate: 2026-03-02 17:18:16 +0000 >> Commit: Baptiste Daroussin <bapt@FreeBSD.org> >> CommitDate: 2026-03-02 17:20:16 +0000 >> >> ports-mgmt/pkg: update to 2.6.0 >>. . . > > After this update portmaster is totally broken. I'm having trouble following the logic here for how portmaster behavior is a pkg bug. portmaster does not even list the pkg port as something it depends on. See: <https://cgit.freebsd.org/ports/tree/ports-mgmt/portmaster/Makefile>; May be it is implicit via some ports infrastructure that is used that in turn uses pkg? Later below I report on why the deletions look correct to me, though I'm unsure if all the backup packages were generated that should have been. > It removes a lot of ports instead of updated only one. "it" being portmaster, not pkg as far as I can tell. > I tested with previous pkg 2.5.1 and just updated portmaster 3.33 - work > as expected. > But pkg 2.6.0 breaks the system - look at example: (You do not show the command that produced the output that you show or the contrast with the command and output for the above 2.5.1 context. SO I work with what is here.) > >> ===>>> Creating a backup package for old version bash- >> completion-2.17.0_1,2 >> Creating package for bash-completion-2.17.0_1,2 >> Checking integrity... done (0 conflicting) >> Deinstallation has been requested for the following 3 packages (of 0 >> packages in the universe): >> >> Installed packages to be REMOVED: >> bash-completion: 2.17.0_1,2 > These lines shouldn't be here: { >> lives: 3.2.0_26 >> x264: 0.164.3095_3 <https://cgit.freebsd.org/ports/tree/multimedia/x264/Makefile>; has: BASH_BUILD_DEPENDS= bash-completion>0:shells/bash-completion BASH_RUN_DEPENDS= bash-completion>0:shells/bash-completion BASH_CONFIGURE_ENABLE= bashcompletion BASH_PLIST_FILES= share/bash-completion/completions/x264 So deleting bash-completion can delete a x264 that was built to depend on bash-completion. It seems that the BASH option was enabled, which, in turn caused a bash-completion dependency. <https://cgit.freebsd.org/ports/tree/multimedia/lives/Makefile>; has: X264_RUN_DEPENDS= x264:multimedia/x264 So deleting x264 can delete lives that was built to depend on X264. It seems that the X264 option was enabled. As stands, it looks to me like portmaster's deletions are correct based on dependencies also being deleted. But I do not know if backup packages should have been generated first for those that were not. > } >> >> Number of packages to be removed: 3 >> >> The operation will free 10 MiB. >> [1/3] Deinstalling lives-3.2.0_26... >> [1/3] Deleting files for lives-3.2.0_26: 100% >> [2/3] Deinstalling x264-0.164.3095_3... >> [2/3] Deleting files for x264-0.164.3095_3: 100% >> [3/3] Deinstalling bash-completion-2.17.0_1,2... >> [3/3] Deleting files for bash-completion-2.17.0_1,2: 100% >> ==> Running trigger: desktop-file-utils.ucl >> Building cache database of MIME types >> ==> Running trigger: gtk-update-icon-cache.ucl >> Generating GTK icon cache for /usr/local/share/icons/hicolor >> >> ===> Installing for bash-completion-2.17.0_1,2 >> ===> Checking if bash-completion is already installed >> ===> Registering installation for bash-completion-2.17.0_1,2 >> Installing bash-completion-2.17.0_1,2... >> To enable the bash completion library, add the following to >> your .bashrc file: >> >> [[ $PS1 && -f /usr/local/share/bash-completion/bash_completion.sh ]] && \ >> source /usr/local/share/bash-completion/bash_completion.sh >> >> See /usr/local/share/doc/bash-completion/README.md for more information. >> >> >> ===>>> Waiting for background 'make clean' processes to finish >> >> ===>>> pkg-message for bash-completion-2.17.0_1,2 >> On install: >> To enable the bash completion library, add the following to >> your .bashrc file: >> >> [[ $PS1 && -f /usr/local/share/bash-completion/bash_completion.sh ]] && \ >> source /usr/local/share/bash-completion/bash_completion.sh >> >> See /usr/local/share/doc/bash-completion/README.md for more information. >> >> ===>>> Done displaying pkg-message files >> >> ===>>> Re-installation of bash-completion-2.17.0_1,2 complete > -- === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ba59c759-c57a-49d0-b1a9-1fffd95cc8e1>