Re: When will a new (ungoogled-)chromium package become available ?

> pkg-status is your friend in letting you know where package builds stand.
> Unfortunately, the actual build systems are Iv6-only and my IP6 tunnel is not working > and I have not had time to figure ou what's wrong, so I can't check on whether
> ungoogled-chromium packaged successfully in the last build.

Good to know. I will keep my eyes out for it.

------- Original Message -------
On Thursday, December 8th, 2022 at 4:18 AM, Kevin Oberman <rkoberman@gmail.com> wrote:

> On Tue, Dec 6, 2022 at 3:51 PM Pete Wright <pete@nomadlogic.org> wrote:
>
>> On Tue, Dec 06, 2022 at 01:55:17AM +0000, 0x1eef wrote:
>>> Hello !
>>>
>>> When can we expect to see the two recent security patches be available through "pkg"
>>> on the Latest branch ? (FBSD13).
>>>
>>> Patch 1:
>>> https://github.com/freebsd/freebsd-ports/commit/fa51d48be7f6c709ee7be36d0764fa318a840bdb
>>>
>>> Patch 2:
>>> https://github.com/freebsd/freebsd-ports/commit/2528c6e55b7bb30d4ad48bd32f68e18bd423761b
>>>
>>> Three days old. 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. 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.
>>
>> Interestingly enough as of a few mins ago my local system picked up the latest pkg.
>>
>> -pete
>>
>> --
>> Pete Wright
>> pete@nomadlogic.org
>
> Looking at pkg-status, a build of over 33K ports started on Dec. 1 shortly after 1:00 UTC. Unfortunately, that was before the patches were committed, so it could not be packaged until the completion of the next run that started on Dec. 06 and took 50 hours, so completed at about 3:00 UTC today. Agt that point, the newly updated packages must be moved to all mirrors. Once it is confirmed that the copies were successful, the package should be available. Hopefully in just a few hours.
>
> pkg-status is your friend in letting you know where package builds stand. Unfortunately, the actual build systems are Iv6-only and my IP6 tunnel is not working and I have not had time to figure ou what's wrong, so I can't check on whether ungoogled-chromium packaged successfully in the last build.
> --
>
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkoberman@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683