From nobody Wed Oct 25 11:37:25 2023 X-Original-To: freebsd-arm@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 4SFn3w4t1gz4yNgj for ; Wed, 25 Oct 2023 11:38:04 +0000 (UTC) (envelope-from furaisanjin@gmail.com) Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 4SFn3v5dvzz3Yns for ; Wed, 25 Oct 2023 11:38:03 +0000 (UTC) (envelope-from furaisanjin@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=dY5kow4W; spf=pass (mx1.freebsd.org: domain of furaisanjin@gmail.com designates 2a00:1450:4864:20::529 as permitted sender) smtp.mailfrom=furaisanjin@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-53de0d1dc46so9116189a12.3 for ; Wed, 25 Oct 2023 04:38:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698233882; x=1698838682; darn=freebsd.org; h=cc:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=S1NMgUMm67R5LQs0EjAgaSdld7YpNEh9kxQJcHpg/jk=; b=dY5kow4WI5HTo5d6MeaM0h0OZQ7NDIzMLHVppiG91c6dHcW0yZi+oSqo1xKqSBVxxL 4Y0IhC/RKw0mHo2M3JQNfa8bLi0DE0shLia3aO5DSpxpBmDDzRcj7vru+HxPZJDeD8l1 CPQBwlzqbHDZt9uvtHv57lIPVg8jTqBHfiRQm4bDHFJhQ2CYDd6tFDGHE10g4NfcJHlC 11HtBVGMg3i+1Fk+wl8jBd7UFsdp9LtdWQ5du80T2XAmqii26stCMsMVs5XTgsJkxy2m faxuRuULFayKlm08rWbx2vfxe/i92giPTgtelSlvOnZyMWNz/PBkODDtIcA+AXmVc5y+ fpQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698233882; x=1698838682; h=cc: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=S1NMgUMm67R5LQs0EjAgaSdld7YpNEh9kxQJcHpg/jk=; b=vwJSEeuUWUetq+j9g6LFApiPjXQyiL/GTBojzRXH8XaB4BkheRl1Jbq8be1zNl8J8M vKJeN6d57qUOwQfCzPuffSnM1Xl9gplvZ0uc9fVFs65jB19N13aSlc3V9MVtaXGnjNWa yeg3q5QWH3GHz7pmezkX1Olf0ke2WHfPi6gMnXKdfFiJuhjHzBUJDRWKg4cC0pRKKlw0 igIs9j1X2pdp6+p+6HYPrhfBf8+U2qdeJ2QibBBbeAmxSnyPKvnUb/xBFCLQ30kCHhvp zuG+EPvuAJ1t9fgWVZPdcjl1+m9O3NgPUiC3Q1RO/u68XBW97oGWVoa3AN+j5DAlJ1od D7fQ== X-Gm-Message-State: AOJu0YzrYAtD3i4+6KLXCpmI6M0nejlLlVamWt8IhPR0H48JLb5HTdu9 CxWzABrZylBrL+aJh6syzS85S0SRWrPvPtiTEYXpXVzfibo= X-Google-Smtp-Source: AGHT+IF01ryZzQfDzREpDgJXSkISr2N1V/DoRP8QfNhs4Dn+jvKeeu2+fuPbaw4+TisbPJLkJlNbJcGpQXwmTC5vn6g= X-Received: by 2002:a50:bae4:0:b0:53e:5044:e28d with SMTP id x91-20020a50bae4000000b0053e5044e28dmr10309464ede.31.1698233881911; Wed, 25 Oct 2023 04:38:01 -0700 (PDT) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 References: <86r0p6v8o4.fsf@bay.localnet> <86edl6uspj.fsf@bay.localnet> In-Reply-To: <86edl6uspj.fsf@bay.localnet> From: =?UTF-8?B?6aKo5L6G5pWj5Lq6?= Date: Wed, 25 Oct 2023 20:37:25 +0900 Message-ID: Subject: Re: No packages lately for arm64? Cc: freebsd-arm@freebsd.org Content-Type: multipart/alternative; boundary="00000000000046e6b1060888e321" X-Spamd-Bar: / X-Spamd-Result: default: False [-0.17 / 15.00]; MISSING_TO(2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; NEURAL_HAM_SHORT(-0.17)[-0.166]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCPT_COUNT_ONE(0.00)[1]; BLOCKLISTDE_FAIL(0.00)[2a00:1450:4864:20::529:server fail]; FREEMAIL_FROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::529:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org] X-Rspamd-Queue-Id: 4SFn3v5dvzz3Yns --00000000000046e6b1060888e321 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello all, Does anybody know what is the actual problem behind this? I had to switch quarterly to latest on 13.2 last week because perl5.32 didn't have EOL tag on quarterly. So I wasn't able to upgrade perl5 from perl5.32 to perl5.34 smoothly by "pkg upgrade" and I decided to switch to latest. And then I realized the package update frequency on latest is much worse than quarterly. It hasn't been updated for more than 1 month. Best regards, furaisanjin 2023=E5=B9=B47=E6=9C=8818=E6=97=A5(=E7=81=AB) 6:35 Carl Johnson : > Mark Millard writes: > > > On Jul 17, 2023, at 08:50, Carl Johnson wrote: > > > >> Hello, > >> I have been watching for packages for the new quarterly port builds, b= ut > >> I haven't seen anything yet. I already update my amd64 system several > >> days ago, but nothing has shown yet for arm64. I checked my logs and = I > >> installed security updates last month, but there haven't been any for > >> the last couple of weeks. When I run pkg update, I just get the > >> following: > >> > >> # pkg update > >> Updating FreeBSD repository catalogue... > >> FreeBSD repository is up to date. > >> All repositories are up to date. > >> > >> I have compared some package versions to my amd64 system and the arm64 > >> packages are definitely out of date. I am running FreeBSD 13.2-RELEAS= E > >> and all pkg configuration files are the original defaults. Is there > >> some web site I could look at to see the build status for packages? > > > > There were major problems with pkg and its performance and resource > > use in an update. Official builds for latest were stopped and > > restarted multiple times as pkg was updated to try to get past the > > issues. > > > > On 2023-Jul-13 9 builds were started, each on a separate server, each > > with 25000+ ports to build. None were quarterly. Looks like 3 > > are still not done, one being for arm64 on ampere2. The other of > > the 9 build servers are off doing other builds now. 131releng-armv7 > > started building on ampere3 but is not quarterly. It has 26000+ ports > > to build. > > > > But 131arm64's quarterly is building on ampere1 and has 12000+ of > > 25000+ to go. > > > > These notes do not cover distribution of built packages to the > > distribution servers. That adds more time after the builds and > > the status is not as easy to find. > > > > I used https://pkg-status.freebsd.org/?all=3D1&type=3Dpackage to gather > > some of the details presented. > > Mark, > Thanks for the information. I have bookmarked that so I can look it up > myself in the future. > > -- > Carl Johnson carlj@peak.org > > --00000000000046e6b1060888e321 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello all,

Does anybody know= what is the actual problem behind this? I had to switch quarterly to lates= t on 13.2 last week because perl5.32 didn't have EOL tag on quarterly. = So I wasn't able to upgrade perl5 from perl5.32 to perl5.34 smoothly by= "pkg upgrade" and I decided to switch to latest. And then I real= ized the package update frequency on latest is much worse than quarterly. I= t hasn't been updated for more than 1 month.

B= est regards,
furaisanjin

2023=E5=B9=B47=E6=9C=8818=E6=97= =A5(=E7=81=AB) 6:35 Carl Johnson <carl= j@peak.org>:
Mark Millard <marklmi@yahoo.com> writes:

> On Jul 17, 2023, at 08:50, Carl Johnson <carlj@peak.org> wrote:
>
>> Hello,
>> I have been watching for packages for the new quarterly port build= s, but
>> I haven't seen anything yet.=C2=A0 I already update my amd64 s= ystem several
>> days ago, but nothing has shown yet for arm64.=C2=A0 I checked my = logs and I
>> installed security updates last month, but there haven't been = any for
>> the last couple of weeks.=C2=A0 When I run pkg update, I just get = the
>> following:
>>
>>=C2=A0 =C2=A0 # pkg update
>>=C2=A0 =C2=A0 Updating FreeBSD repository catalogue...
>>=C2=A0 =C2=A0 FreeBSD repository is up to date.
>>=C2=A0 =C2=A0 All repositories are up to date.
>>
>> I have compared some package versions to my amd64 system and the a= rm64
>> packages are definitely out of date.=C2=A0 I am running FreeBSD 13= .2-RELEASE
>> and all pkg configuration files are the original defaults.=C2=A0 I= s there
>> some web site I could look at to see the build status for packages= ?
>
> There were major problems with pkg and its performance and resource > use in an update. Official builds for latest were stopped and
> restarted multiple times as pkg was updated to try to get past the
> issues.
>
> On 2023-Jul-13 9 builds were started, each on a separate server, each<= br> > with 25000+ ports to build. None were quarterly.=C2=A0 Looks like 3 > are still not done, one being for arm64 on ampere2. The other of
> the 9 build servers are off doing other builds now. 131releng-armv7 > started building on ampere3 but is not quarterly. It has 26000+ ports<= br> > to build.
>
> But 131arm64's quarterly is building on ampere1 and has 12000+ of<= br> > 25000+ to go.
>
> These notes do not cover distribution of built packages to the
> distribution servers. That adds more time after the builds and
> the status is not as easy to find.
>
> I used https://pkg-status.freebsd.org= /?all=3D1&type=3Dpackage to gather
> some of the details presented.

Mark,
Thanks for the information.=C2=A0 I have bookmarked that so I can look it u= p
myself in the future.

--
Carl Johnson=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 carlj@peak.org

--00000000000046e6b1060888e321--