Date: Wed, 7 Dec 2022 23:18:15 -0800 From: Kevin Oberman <rkoberman@gmail.com> To: Pete Wright <pete@nomadlogic.org> Cc: 0x1eef <0x1eef@protonmail.com>, freebsd-questions@freebsd.org Subject: Re: When will a new (ungoogled-)chromium package become available ? Message-ID: <CAN6yY1vFOAUU0tLWa4GWRMCzbzaT8iNQDgeLnwWoKZ_r7xcn6Q@mail.gmail.com> 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
--0000000000001d221a05ef4bd81d Content-Type: text/plain; charset="UTF-8" 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 --0000000000001d221a05ef4bd81d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon= t-family:tahoma,sans-serif;font-size:small">On Tue, Dec 6, 2022 at 3:51 PM = Pete Wright <<a href=3D"mailto:pete@nomadlogic.org">pete@nomadlogic.org<= /a>> wrote:</div></div><div class=3D"gmail_quote"><blockquote class=3D"g= mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204= ,204,204);padding-left:1ex">On Tue, Dec 06, 2022 at 01:55:17AM +0000, 0x1ee= f wrote:<br> > Hello !<br> > <br> > When can we expect to see the two recent security patches be available= through "pkg" <br> > on the Latest branch ? (FBSD13).<br> > <br> > Patch 1:<br> > <a href=3D"https://github.com/freebsd/freebsd-ports/commit/fa51d48be7f= 6c709ee7be36d0764fa318a840bdb" rel=3D"noreferrer" target=3D"_blank">https:/= /github.com/freebsd/freebsd-ports/commit/fa51d48be7f6c709ee7be36d0764fa318a= 840bdb</a><br> > <br> > Patch 2:<br> > <a href=3D"https://github.com/freebsd/freebsd-ports/commit/2528c6e55b7= bb30d4ad48bd32f68e18bd423761b" rel=3D"noreferrer" target=3D"_blank">https:/= /github.com/freebsd/freebsd-ports/commit/2528c6e55b7bb30d4ad48bd32f68e18bd4= 23761b</a><br> > <br> > Three days old. Is it normal to wait this long for a security patch to= reach "Latest" ?<br> Am I missing something, it looks like the patches were comitted to the port= s source tree 4 and 3 days ago.=C2=A0 I think it takes time for official pa= ckages to be built, but when I've had to address serious security issue= s with a port/pkg I've built it locally until the build cluster catches= up.<br> <br> Interestingly enough as of a few mins ago my local system picked up the lat= est pkg.<br> <br> -pete<br> <br> -- <br> Pete Wright<br> <a href=3D"mailto:pete@nomadlogic.org" target=3D"_blank">pete@nomadlogic.or= g</a><br></blockquote><div><br></div><div style=3D"font-family:tahoma,sans-= serif;font-size:small" class=3D"gmail_default">Looking at pkg-status, a bui= ld of over 33K ports started on Dec. 1 shortly after 1:00 UTC. Unfortunatel= y, 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 ho= urs, so completed at about 3:00 UTC today. Agt that point, the newly update= d packages must be moved to all mirrors. Once it is confirmed that the copi= es were successful, the package should be available. Hopefully in just a fe= w hours.</div><div style=3D"font-family:tahoma,sans-serif;font-size:small" = class=3D"gmail_default"><br></div><div style=3D"font-family:tahoma,sans-ser= if;font-size:small" class=3D"gmail_default">pkg-status is your friend in le= tting 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 ti= me to figure ou what's wrong, so I can't check on whether ungoogled= -chromium packaged successfully in the last build.<br></div></div>-- <br><d= iv dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"= ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr">Kevin Oberman, Part time k= id herder and retired Network Engineer<br>E-mail: <a href=3D"mailto:rkoberm= an@gmail.com" target=3D"_blank">rkoberman@gmail.com</a><br></div><div>PGP F= ingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683</div></div></div></div= ></div></div></div></div></div> --0000000000001d221a05ef4bd81d--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vFOAUU0tLWa4GWRMCzbzaT8iNQDgeLnwWoKZ_r7xcn6Q>