public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: List of available updates incomplete for "unstable" tree
Date: Mon, 20 Jun 2022 16:11:30 +0100	[thread overview]
Message-ID: <816A6797-0765-4AA2-8FE4-CE02E39043B2@ipfire.org> (raw)
In-Reply-To: <3b74de30-1db2-35e6-74df-170aa9c5045f@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]

Hello,

> On 20 Jun 2022, at 10:53, Peter Müller <peter.mueller(a)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

  reply	other threads:[~2022-06-20 15:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20  9:53 Peter Müller
2022-06-20 15:11 ` Michael Tremer [this message]
2022-06-20 20:37   ` Peter Müller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=816A6797-0765-4AA2-8FE4-CE02E39043B2@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox