From nobody Fri Aug 16 14:33:29 2024 X-Original-To: freebsd-ports@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 4Wlkxs5m0mz5T23B for ; Fri, 16 Aug 2024 14:33:37 +0000 (UTC) (envelope-from portmaster@bsdforge.com) Received: from udns.ultimatedns.net (udns.ultimatedns.net [24.113.41.81]) (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 "ultimatedns.net", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wlkxs0lktz4VZL; Fri, 16 Aug 2024 14:33:37 +0000 (UTC) (envelope-from portmaster@bsdforge.com) Authentication-Results: mx1.freebsd.org; none Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 47GEXThL074970; Fri, 16 Aug 2024 07:33:35 -0700 (PDT) (envelope-from portmaster@bsdforge.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ultimatedns.net; s=mx99; t=1723818816; x=1723819416; r=y; bh=B5PmoJNKA6zNfcEpTl5dY//ZawyrXHOiJugeBDBxyG0=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=kbEH+V7hXFvAHyPhXYmVELwNU2B00DtScuOklmSwq08Z2JMvTSDTVA8OrGpUVKmQI W9a5Pi66kF63CMr1vfz1BPkVAvMpR1W+RExAP8zy135ISoMPz8ZeQPfrLBzSAdk+sO EFzap38H7Z0WfZGYvBRfnVziwCAoQjRXvVs10F1qbVMT8gSQrTSgnrniardEG4tD+9 0VJk/Ip1RSA9g/v98YMtpqgGfo6WkwlmGuKus3ssf/WOtUMzi7OR67yBHiRzkNExK0 X2O1k5bUbM4EVFCMV3FRuiq7BRJr2p3FkDoKcChjKZifXc2de8juzhMz8PcNDtQFd7 FlrLzREy+DBmg== List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.org MIME-Version: 1.0 Date: Fri, 16 Aug 2024 07:33:29 -0700 From: Chris To: Dimitry Andric Cc: Miroslav Lachman <000.fbsd@quip.cz>, henrichhartzer@tuta.io, Freebsd Ports Subject: Re: quarterly 2024Q3 amd64 / 13.3 missing all vital packages for desktop In-Reply-To: References: <608da216-2047-4fdd-b48b-88659dedb27c@quip.cz> <3c600636-34a5-4d6c-86d6-f04da1daa806@quip.cz> User-Agent: UDNSMS/17.0 Message-ID: X-Sender: portmaster@bsdforge.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US] X-Rspamd-Queue-Id: 4Wlkxs0lktz4VZL On 2024-08-16 07:09, Dimitry Andric wrote: > On 16 Aug 2024, at 15:49, Chris wrote: >> >> On 2024-08-16 00:37, Miroslav Lachman wrote: >>> On 16/08/2024 01:34, henrichhartzer@tuta.io wrote: >>>> Hi Miroslav, >>>> Please see my email titled: "Quarterly backport for multimedia/x265 >>>> patch" sent to this list a few hours before yours. Shortly after sending >>>> it, the patch was committed to 2024Q3. Builders will have to catch up, >>>> but hopefully things can be resolved. >>>> I do feel like this could have been caught and fixed faster with some >>>> better alerting. I've heard of pkg-fallout and know little of it, but >>>> maybe it should have noticed this? Or did it? I have no idea. >>>> I know it's a terrible experience when pkg is wanting to remove your >>>> desktop packages in bulk. >>> Thank you for pointing to this thread. >>> This is really bad experience with quarterly branch. I think the branch >>> should be >>> published only after the successful build of main packages. Blindly >>> created >>> quarterly branch which is not working for about 6 weeks is terrible >>> experience. >> While I completely agree. I'm wondering if this isn't more a pkg(8) >> deficit. eg; if pkg first >> determined that all/most of the packages intended to be upgraded did not >> exist, issue a warn, with the >> option to bail/quit. Leaving the system untouched. > > Last time I checked "pkg upgrade" asks "Proceed with this action? [y/N]", > and the > default is "N". So what you are suggesting, is already the case? Right you are. Sorry. Just got up, I'll refrain from responding before finishing my coffee in the future. :/ > > This is a problem with patches (or really any distfiles) that are retrieved > from > websites which are not under FreeBSD's control. If those websites decide to > change > the contents of those files, there is not much we can do about it, and ports > which > used to work then simply break. If other ports depend on those, those break > too, > there is not much you can do, except postponing upgrades. > > -Dimitry --Chris -- Be a measuring stick of quality. Not everyone is used to an environment where excellence is expected.