From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-09-01
Date: Thu, 5 Sep 2019 09:24:19 +0200 [thread overview]
Message-ID: <20190905092419.2a23fe05@windsurf> (raw)
In-Reply-To: <CAFOYHZA-v1OeAoWcN1tZr6eF7oD5pD7rTMpCcnL2dtN6nwOu4w@mail.gmail.com>
Hello Chris,
On Thu, 5 Sep 2019 12:46:01 +1200
Chris Packham <judge.packham@gmail.com> wrote:
> > name | found by | link to release-monitoring.org | version | upstream
> > -------------------------------+----------+----------------------------------------------+--------------+--------------
> > eventlog | GUESS | https://release-monitoring.org/project/14684 | 0.2.12 | 3.23.1
> > syslog-ng | GUESS | https://release-monitoring.org/project/04930 | 3.22.1 | 3.23.1
>
> Any way we can feedback to release-monitoring about eventlog. They
> seem to be tracking the syslog-ng version but actually eventlog 0.2.13
> is the latest (not that I can find a working download link for it).
>
> I'll look at another bump for syslog-ng (I know the last one was only
> just applied).
release-monitoring.org is like a Wiki: anyone with an account can add
and modify projects.
However, for eventlog, how does one know about new versions ? The
Github repo at https://github.com/balabit/eventlog doesn't have any
tags, and the HTTP URL https://my.balabit.com/downloads/eventlog/ that
we use in eventlog.mk does not have listing enabled. So, there doesn't
seem to be a useful way for release-monitoring.org to detect the new
versions available.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-05 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d6cb406.1c69fb81.71217.d243SMTPIN_ADDED_MISSING@mx.google.com>
2019-09-05 0:46 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-09-01 Chris Packham
2019-09-05 7:24 ` Thomas Petazzoni [this message]
2019-09-07 11:24 ` Arnout Vandecappelle
2019-09-07 11:50 ` Thomas Petazzoni
2019-09-07 19:13 ` Arnout Vandecappelle
2019-09-09 9:29 ` Chris Packham
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=20190905092419.2a23fe05@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.