Date: Thu, 08 Dec 2022 21:37:00 +1100 From: Ian Smith <smithi@nimnet.asn.au> To: Pete Wright <pete@nomadlogic.org>,0x1eef <0x1eef@protonmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: When will a new (ungoogled-)chromium package become available ? Message-ID: <957AA1F3-534D-4373-A701-2FEFE4198009@nimnet.asn.au> In-Reply-To: <20221206235141.vn3kn5ox7a43emm5@topanga> References: <20221206015513.wslttnr5ccltepdu@reflect.0x1eef.test> <20221206235141.vn3kn5ox7a43emm5@topanga>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7 December 2022 10:51:41 am AEDT, Pete Wright <pete@nomadlogic=2Eorg> wr= ote: > On Tue, Dec 06, 2022 at 01:55:17AM +0000, 0x1eef wrote: > > Hello ! > >=20 > > When can we expect to see the two recent security patches be > available through "pkg"=20 > > on the Latest branch ? (FBSD13)=2E > >=20 > > Patch 1: > > > https://github=2Ecom/freebsd/freebsd-ports/commit/fa51d48be7f6c709ee7be= 36d0764fa318a840bdb > >=20 > > Patch 2: > > > https://github=2Ecom/freebsd/freebsd-ports/commit/2528c6e55b7bb30d4ad48= bd32f68e18bd423761b > >=20 > > Three days old=2E Is it normal to wait this long for a security patch > to reach "Latest" ? > Am I missing something, it looks like the patches were comitted to > the ports source tree 4 and 3 days ago=2E I think it takes time for > official packages to be built, but when I've had to address serious > security issues with a port/pkg I've built it locally until the build > cluster catches up=2E >=20 > Interestingly enough as of a few mins ago my local system picked up > the latest pkg=2E >=20 > -pete Considering the first commit was as of now 5 days ago, consisting of 318 c= hanged files with 1,658 additions and 1,731 deletions, with Pete's message = a day old, I'd have thought it was pretty darn snappy service for a hardly = essential port, especially considering the discount price =2E=2E=2E cheers <&^}=3D
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?957AA1F3-534D-4373-A701-2FEFE4198009>