From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: List of available updates incomplete for "unstable" tree Date: Mon, 20 Jun 2022 16:11:30 +0100 Message-ID: <816A6797-0765-4AA2-8FE4-CE02E39043B2@ipfire.org> In-Reply-To: <3b74de30-1db2-35e6-74df-170aa9c5045f@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6757520109372430713==" List-Id: --===============6757520109372430713== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, > On 20 Jun 2022, at 10:53, Peter M=C3=BCller wr= ote: >=20 > Hello Michael, >=20 > in conjunction with upcoming Core Update 169, I just noticed that my testin= g machine shows > both the Core Update itself and lynis as available updates, but not Tor, wh= ich has been > recently updated in the "next" branch. If this is for x86_64, this might be because there have been no nightly build= s in the past five days. For some reason, the builder had some issue and needed to be rebooted. Hopefu= lly, in a couple of hours the build should be available. > I presume this is due to uploading and/or signing of nightly build packages= only performed > on a regular interval, not triggered by commits or successful builds. To en= sure I am not > mistaken on that front, however, I would be glad for a clarification. :-) After the build has been uploaded, it is automatically being distributed over= some of our mirror servers. > All the best, > Peter M=C3=BCller -Michael --===============6757520109372430713==--