From nobody Thu May 14 13:04:05 2026 X-Original-To: freebsd-pkg@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 4gGVs51btKz6d6Ng for ; Thu, 14 May 2026 13:04:09 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fout-a7-smtp.messagingengine.com (fout-a7-smtp.messagingengine.com [103.168.172.150]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4gGVs41Yd3z3N81 for ; Thu, 14 May 2026 13:04:08 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b="nviGPw/z"; dkim=pass header.d=messagingengine.com header.s=fm3 header.b="o WzQD9P"; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 103.168.172.150 as permitted sender) smtp.mailfrom=void@f-m.fm Received: from phl-compute-10.internal (phl-compute-10.internal [10.202.2.50]) by mailfout.phl.internal (Postfix) with ESMTP id 71A1DEC0253 for ; Thu, 14 May 2026 09:04:07 -0400 (EDT) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-10.internal (MEProxy); Thu, 14 May 2026 09:04:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:subject:subject:to:to; s=fm3; t=1778763847; x=1778850247; bh=6KRfT1SK6jLeRNXEo58bsO6DLG44ZBbW aPn0Gal4PyQ=; b=nviGPw/zIrOH6FDMWpUVhCf8uhfxk58tW63gJsaSnMIE/zCC BPz3ITFgvECWwyY5qK9a0l1u+Fxdew9MgtQMAlm/csr9Wkv/Y3RsiNwE9N457/Ih YAlkXXkrXoviGp+Vp6XjWLXbzaSw2xudKKan8GVgUEbRDFDX+fnZqGzd70gtkXpD uqKxzQjMMYFiGHL5+A6o/L/WO8eJFr8iap0YWfSqnPnUAt6SBYwG4T6g7Tx+08B2 ePwEXIrtdIIA/dSunlcAwPAD0t0mSCjTGSaOmRL4M+tWRTvKMk2zp9tMyksKIYly +Pe8/U6mfIX6aCYEU5AE4yg9XSwLL4KO5cokGQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1778763847; x= 1778850247; bh=6KRfT1SK6jLeRNXEo58bsO6DLG44ZBbWaPn0Gal4PyQ=; b=o WzQD9PVxApjuL7rdvr47OpYagwWvu/IptnVezzmDv9M0OZmplG5Kyzse3y6M2Z6U ieteamd9/UELjCPAJiStO4p8D4KioT24w0tmVUvcbC5bvjZNS6GNwzCEarJgUy8l fxrCtwzyC0t9zDYZ4YjrQsihLkd+6l4TZk4GPfZIt7d+DtBL4GKbkxxwLjbn3dqs 7NVPm8vJt1kP7M84XpjuzuAYlcDRTf79iOWDvwtP9JtQvZ8Lc60y3YVKkM2oJCrl IRQhoXSpImNLF8EdQOS+vTBfgPBxY61y3uHeOT/xxTr43NX/IbVnyFVWzXmfB2xi IlhII38mQmoDCw+OhJi9A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefhedrtddtgdduvdejheelucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugesthdtredttddtvd enucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgrthhtvghr nhepveduffeivdfffffghfegfeejfefftdeiteehteekfefhvdefgfettdeuheegffeune cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepvhhoihgu sehfqdhmrdhfmhdpnhgspghrtghpthhtohepuddpmhhouggvpehsmhhtphhouhhtpdhrtg hpthhtohepfhhrvggvsghsugdqphhkghesfhhrvggvsghsugdrohhrgh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Thu, 14 May 2026 09:04:06 -0400 (EDT) Date: Thu, 14 May 2026 14:04:05 +0100 From: void To: freebsd-pkg@freebsd.org Subject: circular dependencies in ports tree - how to fix? Message-ID: Mail-Followup-To: freebsd-pkg@freebsd.org List-Id: Binary package management and package tools discussion List-Archive: https://lists.freebsd.org/archives/freebsd-pkg List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkg@FreeBSD.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Spamd-Result: default: False [-2.59 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.991]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.150:from]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_FROM(0.00)[f-m.fm]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-pkg@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MLMMJ_DEST(0.00)[freebsd-pkg@freebsd.org]; ASN(0.00)[asn:151847, ipnet:103.168.172.0/24, country:AU]; RCVD_VIA_SMTP_AUTH(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] X-Spamd-Bar: -- X-Rspamd-Queue-Id: 4gGVs41Yd3z3N81 Hi, On a 15.1 poudriere jail with latest ports tree, the following happens: [00:05:30] Sanity checking build queue [00:05:30] Error: /usr/local/share/poudriere/bulk.sh:pkgqueue_sanity_check:27:Dependency loop detected: These packages depend on each other: run:libheif-1.21.2_3 run:ffmpeg-8.1.1,1 run:libcaca-0.99.b20_1 build:libcaca-0.99.b20_1 run:imlib2-1.12.6,2 build:imlib2-1.12.6,2 These packages depend on each other: run:ffmpeg-8.1.1,1 run:libcaca-0.99.b20_1 build:libcaca-0.99.b20_1 run:imlib2-1.12.6,2 run:libheif-1.21.2_3 build:libheif-1.21.2_3 These packages depend on each other: run:libcaca-0.99.b20_1 build:libcaca-0.99.b20_1 run:imlib2-1.12.6,2 run:libheif-1.21.2_3 run:ffmpeg-8.1.1,1 These packages depend on each other: run:libcaca-0.99.b20_1 build:libcaca-0.99.b20_1 run:imlib2-1.12.6,2 run:libheif-1.21.2_3 run:ffmpeg-8.1.1,1 build:ffmpeg-8.1.1,1 [151amd64-default] [2026-05-12_19h03m56s] [crashed] Time: 00:05:19 How to fix, please? If not fixable in the short term, would this best be raised as a PR in ports infrastructure, or against each port? For the time being, I'm going to try commenting out each affected port in the build list. --