From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Re: List of available updates incomplete for "unstable" tree Date: Mon, 20 Jun 2022 20:37:54 +0000 Message-ID: <49a739d1-99d9-7531-a736-697e77f07bd5@ipfire.org> In-Reply-To: <816A6797-0765-4AA2-8FE4-CE02E39043B2@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7984962541392461463==" List-Id: --===============7984962541392461463== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Michael, thanks for your reply. > Hello, >=20 >> On 20 Jun 2022, at 10:53, Peter M=C3=BCller w= rote: >> >> Hello Michael, >> >> in conjunction with upcoming Core Update 169, I just noticed that my testi= ng machine shows >> both the Core Update itself and lynis as available updates, but not Tor, w= hich has been >> recently updated in the "next" branch. >=20 > If this is for x86_64, this might be because there have been no nightly bui= lds in the past five days. >=20 > For some reason, the builder had some issue and needed to be rebooted. Hope= fully, in a couple of hours the build should be available. I received a mail stating that the build went successful on x86_64, but night= ly.ipfire.org was not updated. :-( Will investigate on this tomorrow, if possible. Thanks, and best regards, Peter M=C3=BCller >=20 >> I presume this is due to uploading and/or signing of nightly build package= s only performed >> on a regular interval, not triggered by commits or successful builds. To e= nsure I am not >> mistaken on that front, however, I would be glad for a clarification. :-) >=20 > After the build has been uploaded, it is automatically being distributed ov= er some of our mirror servers. >=20 >> All the best, >> Peter M=C3=BCller >=20 > -Michael --===============7984962541392461463==--