Hello Michael,
in conjunction with upcoming Core Update 169, I just noticed that my testing machine shows both the Core Update itself and lynis as available updates, but not Tor, which has been recently updated in the "next" branch.
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 ensure I am not mistaken on that front, however, I would be glad for a clarification. :-)
All the best, Peter Müller
Hello,
On 20 Jun 2022, at 10:53, Peter Müller peter.mueller@ipfire.org wrote:
Hello Michael,
in conjunction with upcoming Core Update 169, I just noticed that my testing machine shows both the Core Update itself and lynis as available updates, but not Tor, which has been recently updated in the "next" branch.
If this is for x86_64, this might be because there have been no nightly builds in the past five days.
For some reason, the builder had some issue and needed to be rebooted. Hopefully, 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 ensure 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üller
-Michael
Hello Michael,
thanks for your reply.
Hello,
On 20 Jun 2022, at 10:53, Peter Müller peter.mueller@ipfire.org wrote:
Hello Michael,
in conjunction with upcoming Core Update 169, I just noticed that my testing machine shows both the Core Update itself and lynis as available updates, but not Tor, which has been recently updated in the "next" branch.
If this is for x86_64, this might be because there have been no nightly builds in the past five days.
For some reason, the builder had some issue and needed to be rebooted. Hopefully, in a couple of hours the build should be available.
I received a mail stating that the build went successful on x86_64, but nightly.ipfire.org was not updated. :-( Will investigate on this tomorrow, if possible.
Thanks, and best regards, Peter Müller
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 ensure 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üller
-Michael
-
Michael Tremer -
Peter Müller