From nobody Thu Dec 08 07:18:15 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 4NSQVc43Nwz4jx0T for ; Thu, 8 Dec 2022 07:18:32 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NSQVb4KGpz3tH9 for ; Thu, 8 Dec 2022 07:18:31 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=fENnWVFl; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::b2a as permitted sender) smtp.mailfrom=kob6558@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yb1-xb2a.google.com with SMTP id d131so617273ybh.4 for ; Wed, 07 Dec 2022 23:18:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=+b08Ph3MrP6sHzJgxHrPuvmm1Df6YpBXMYnSiN8A3w0=; b=fENnWVFlgRR4ypLrmx16reSIMF0khvZhPFJ3HpM22TEMEbQ0cau4BIdLsNVPn+ECLq rhGeCfEZLXuhO+rJtkjAgy0JjGdvQIA/WJijc+ZU3Evvbkcd3SxnkI4lCO38UDZnUBB1 9TmiwtHVPFEBPID5YksiKDc6mUEjNFx0CP7w5psNkIv/YVU0B4+7e14aw7U8nvG9hwPU IOE5pc/62lsdwa1k6TTWdTnmov/y4y8b0h1IUO7JwX8g8BaeW8ZDLs6Vi0YOual86VEd KK1KhLVjKwP3WT5YHWJFP81LIl91d5o0HmD2B82D2QrsYVwDrYr85RUSq62eYI96WfHn BKsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+b08Ph3MrP6sHzJgxHrPuvmm1Df6YpBXMYnSiN8A3w0=; b=dMkBaBSshNn8b+rR8PHMdwPmq9TJ5ih9XKZh0u3U4A+VADYQFF7Zq5DiUeRHBmtJAw nZR2kXjoI0lc7T2lM5EuzQx7VY9rSsp7pZeYFp2bw/hgp2RCCgqXGjJGTc8vBIgzJlbT zAWTIqBvhMgJ9RHxFmMDu4sfWwPQ0WF7DjFeoHrOE15UO9CquaymW90uR7FZmv3yNIEa UUjaaVcGe4QQ8TjrZKu0ETjWasSG+e+7ZCnl/hSK8isDXKPedPvm4RQlLdUKmdyRUFKQ I6Jj3kKHewktlQ1aOndWk876mImP8nzkkfSZgchzP8Wn3RgYp0vJLG+5tueZq0lLVLjX 3ZEw== X-Gm-Message-State: ANoB5pmMDsJ6+BArlc/lFuPjCcvCFZgFrCh/oblUbiM1i1l8Wov6RbsG QD45Fa4S6q8iaq5JEjpw27SWrzb9cpPW4RQlD/Of9q6N X-Google-Smtp-Source: AA0mqf5p34bceSgDDHnJfLXSGjXg49aWHE/uPks3gYm1sVcplnV4q9Lkp1pZ+mlugHqiYK+75Du+GoU7dA2yYh/SiWc= X-Received: by 2002:a25:d0c:0:b0:6f2:3fbc:a30c with SMTP id 12-20020a250d0c000000b006f23fbca30cmr58756840ybn.573.1670483910925; Wed, 07 Dec 2022 23:18:30 -0800 (PST) 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 References: <20221206015513.wslttnr5ccltepdu@reflect.0x1eef.test> <20221206235141.vn3kn5ox7a43emm5@topanga> In-Reply-To: <20221206235141.vn3kn5ox7a43emm5@topanga> From: Kevin Oberman Date: Wed, 7 Dec 2022 23:18:15 -0800 Message-ID: Subject: Re: When will a new (ungoogled-)chromium package become available ? To: Pete Wright Cc: 0x1eef <0x1eef@protonmail.com>, freebsd-questions@freebsd.org Content-Type: multipart/alternative; boundary="0000000000001d221a05ef4bd81d" X-Spamd-Result: default: False [-0.72 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.98)[0.985]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b2a:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; FREEMAIL_CC(0.00)[protonmail.com,freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4NSQVb4KGpz3tH9 X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N --0000000000001d221a05ef4bd81d Content-Type: text/plain; charset="UTF-8" On Tue, Dec 6, 2022 at 3:51 PM Pete Wright 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
On Tue, Dec 6, 2022 at 3:51 PM = Pete Wright <pete@nomadlogic.org<= /a>> wrote:
On Tue, Dec 06, 2022 at 01:55:17AM +0000, 0x1ee= f 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/fa51d48be7f6c709ee7be36d0764fa318a= 840bdb
>
> Patch 2:
> https:/= /github.com/freebsd/freebsd-ports/commit/2528c6e55b7bb30d4ad48bd32f68e18bd4= 23761b
>
> 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 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.

Interestingly enough as of a few mins ago my local system picked up the lat= est pkg.

-pete

--
Pete Wright
pete@nomadlogic.or= g

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.

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.
--
Kevin Oberman, Part time k= id herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP F= ingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
--0000000000001d221a05ef4bd81d--