From nobody Sat Mar 08 16:49:41 2025 X-Original-To: desktop@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 4Z98Jk02Nhz5pRrs for ; Sat, 08 Mar 2025 16:49:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z98Jj6HfZz3pPQ for ; Sat, 08 Mar 2025 16:49:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1741452581; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tbgkUtVIK7FjVXTw6xlzlulj7jJShxW4Ol3tQKuam10=; b=pAfkkb6YWW6b0FZ+6wIvJn8uxKmBsTTFCj8TJOmvJ2PXasCQNmamez8DFvmr1514kh2F3L GexICsL7ylqLhDhrJJEFkNdghIxIsRABh65yDZI+x5MuQhdxy73sB74Z6Cw2jRMyYYobyI CDBMfhYn2HTY1pQwQAm9cglRrHOkITCR4S9lydPZIYmkxxQXm6hrgY3PCc9zxHyI/FEDYJ otMiOKWDGJZwxSOO74VaO0ZdN4pQzsCVZuN6YFsPO/vZauelaJDbmjAJgrmPYlZOLqpE+K HEFgzIBnH8viM3+tDx+VqDGiyUcQxZDUT/wuIO1hbFcywJoPnti+Vc/10nVqpQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1741452581; a=rsa-sha256; cv=none; b=aI+kltQhppP56CesCLN7xACB97Xg+fAEM28LXTWj6CS+jR/F6GXboX7bU2xIds8K9C5IgV OTtWHK627h3Ma1Uay+AyLiPfRCUaheYHYwAFSnd0cHVLhJJI3tbNlgwHJKk4XUsWH1lcp0 jos3QHySga4LShAy4FKicgqDt/xhhbUURp+MG9Mabl0Mgwvc3Icw249FYsfCwyaIS+biQA NJ0bNgvrBiMxJ7q+cJxg3ZlKz4SHrJwkaZJ4hQv/Uy3Tf6bpiMETgZ2dQcfrMlHw+weubk Kwt6BzrMZmHQlEmbL0mHI4iwG/ol9Odx1maUth+Qab+NKX3evawpr2pIUtXwbg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1741452581; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tbgkUtVIK7FjVXTw6xlzlulj7jJShxW4Ol3tQKuam10=; b=wCeIEMziT7+XJxc5iLEiTZYGt9P90QjehzBCtRvHj8sHLgCB1Pqqp+IbEX4m1xYMccUQQk G6mTQ0c6DH8g07ENG46suAYL2AV0KgOQTk2SU4IN+ahTHJ8QEoLupHTMCioPtZJs1CEP6M 9uJ/u/Vn2uOfyf7YLmpxXIaEUUvO25hjBuD9ujpcFNptJJL2WjrgZlYjXGKDVPDopTdZpJ 5kdx+qe+WwRFLmcgIFwHEBp1WsLlrBWvlalgdetXeHFrLTUb4kzN3X/auo0DnsNHj1Tl+B v7x+uyiOPpUqrNRkm1JGgu4Vt7NIVZrSTiCP7tBBydJs6jy4f0r+huZKBdAUbQ== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Z98Jj5S7yzX2F for ; Sat, 08 Mar 2025 16:49:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 528GnfXA053417 for ; Sat, 8 Mar 2025 16:49:41 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 528Gnf6h053416 for desktop@FreeBSD.org; Sat, 8 Mar 2025 16:49:41 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: desktop@FreeBSD.org Subject: [Bug 285253] devel/dbus: upgrade without bumping dependent ports breaks ... everything Date: Sat, 08 Mar 2025 16:49:41 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: milios@ccsys.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: desktop@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Using and improving FreeBSD on the desktop List-Archive: https://lists.freebsd.org/archives/freebsd-desktop List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-desktop@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285253 Chad Jacob Milios changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |milios@ccsys.com --- Comment #5 from Chad Jacob Milios --- (In reply to Gleb Popov from comment #2) has this finally become the project's official position? i admit i do not s= tay well read on the mailing lists but i do read everything put in CHANGES. i havent seen anything to that effect and it looks like the handbook section 5.2.3.1 reads the same as i remember it. actually come to think of it, i di= dnt realize it said "that includes changes that only affect a package built with non-default options." is our make and our shell no longer a "supported" ports build tool? i reali= ze for many years it hasn't been the "cool" way to do it anymore, but time and time again i've sought assurance and been assured that poudriere will not become a mandatory requirement to utilize the ports tree effectively. my site has yet another such tool, developed internally and maintained since the FreeBSD 6 pkg_install days. it has always relied on a change of PKGNAME= (of which PORTREVISION is a component) as signal it's necessary to rebuild a po= rt. save for the occasionally overlooked bump or a non-default optional depende= ncy here and there, it's always reliably kept our rollout up to date with dynam= ic links intact and it ties into our workflow in a way that is entirely out of scope for poudriere, synth or portmaster. if it "should be taught to consult pkg provides/requires" was there a notice issued that might point me in the right direction? what relationship(s) necessitate i should cascade rebuilds? (whenever LIB_, RUN_, or BUILD_DEPEN= DS changes, just to be safe?) believe me, i'm not resistant to change in this direction. i would love it = if we're ready to stop all the obligatory PORTREVISION bumping commits. i'm not opposed to enhancing our tooling here to detect staleness of same-named packages by other conditional logic. the only reason we haven't is since 5.2.3.1 still reads as it reads. i'll be glad when we usher in this better way of doing things, i just got to say i was unprepared. without commits like a347a92e i too would've had a bu= nch of broken packages and before reading your comment #2, arrowd@, i probably would have been at a loss to quickly realize why --=20 You are receiving this mail because: You are the assignee for the bug.=