From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter =?utf-8?q?M=C3=BCller?= <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: List of available updates incomplete for "unstable" tree
Date: Mon, 20 Jun 2022 09:53:29 +0000
Message-ID: <3b74de30-1db2-35e6-74df-170aa9c5045f@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6379521342144822339=="
List-Id: <development.lists.ipfire.org>

--===============6379521342144822339==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

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, whic=
h has been
recently updated in the "next" branch.

I presume this is due to uploading and/or signing of nightly build packages o=
nly performed
on a regular interval, not triggered by commits or successful builds. To ensu=
re I am not
mistaken on that front, however, I would be glad for a clarification. :-)

All the best,
Peter M=C3=BCller

--===============6379521342144822339==--