From nobody Thu Dec 08 19:19:21 2022 X-Original-To: freebsd-questions@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 4NSkVY6GKTz4kDGk for ; Thu, 8 Dec 2022 19:19:33 +0000 (UTC) (envelope-from 0x1eef@protonmail.com) Received: from mail-40134.protonmail.ch (mail-40134.protonmail.ch [185.70.40.134]) (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 "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NSkVY3vJ4z4NL9 for ; Thu, 8 Dec 2022 19:19:33 +0000 (UTC) (envelope-from 0x1eef@protonmail.com) Authentication-Results: mx1.freebsd.org; none Date: Thu, 08 Dec 2022 19:19:21 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1670527171; x=1670786371; bh=Zh266ss0HrtqEg9e0m6SbzFdsx3g3zSHPq+NVJOAlgA=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=IaDYC6Yczhpoxdg7zyltLgiq2oRpK5UYiBesYBW/KRD2S3QJjDKWKu9qRELNAYzLk Z7y5ObAN69HIVC7C/TtljjhvZe4pq0WJWFus0DuGtNLgedIXqdX4CWE8U3sMohu1SK zv8JDCqJCCXBhtOfdFGInAFg2X+3mfUnDb5JqJL5HednoJ8X8Y25GWdOcYiGfFw6tH m4z+Qwmt6eQY1RNqNkI2HY/XLJzNKmPvEdciaw1axXwpA/7zCmGUqI8OFFaGKsYDCC qUEMnA6wrsqtOoLRwDH8+EmO6W93O9sz8BCYiZM+3jQBYHWnVHsmpdJ1ivZOEzRum9 jNUJyVunbXh1Q== To: Ian Smith From: 0x1eef <0x1eef@protonmail.com> Cc: Pete Wright , freebsd-questions@freebsd.org Subject: Re: When will a new (ungoogled-)chromium package become available ? Message-ID: In-Reply-To: References: <20221206015513.wslttnr5ccltepdu@reflect.0x1eef.test> <20221206235141.vn3kn5ox7a43emm5@topanga> Feedback-ID: 39071764:user:proton List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4NSkVY3vJ4z4NL9 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > I'll cop to the low form of sarcasm if you'll consider owning unwarranted= impatience. Fair enough. I'm not sure how (relatively) normal such a situation is, though. My other computer that runs OpenBSD picked up the fix no later than 3 days after release, and it could have been available sooner than that. "Void Linux" was more or less the same. It looks like the processes FreeBSD follows can lead up to a delay anywhere between 1, and 7 days. > This is a patch to ported software that - like many others - will always need ongoing updates. There are a number of other browsers you could use meanwhile, should particular bugs expose you to=20 unacceptable immediate risk. I think what I have learnt from this thread, and other places I=20 discussed the same issue is that I should run chromium in a jail,=20 and/or setup my own package server on a VPS that can build things=20 like Chromium as soon as a fix becomes available. Thanks, 0x1eef