All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-09-01
Date: Sat, 7 Sep 2019 13:50:36 +0200	[thread overview]
Message-ID: <20190907135036.1de67005@windsurf> (raw)
In-Reply-To: <84828989-ee8d-36ff-a7c0-a1ef61d447bd@mind.be>

Hello,

On Sat, 7 Sep 2019 13:24:47 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:

> > 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.  
> 
>  There's https://github.com/balabit/eventlog/blob/master/VERSION - can
> release-monitoring use that?

Yes, it can, and I changed eventlog accordingly:

  https://release-monitoring.org/project/14684/

The drawback with this is that it will only know about one version at a
time, contrary to a list of git tags or a list of tarballs.

Also, for now release-monotoring.org still remembers about the invalid
versions from syslog-ng. I'll report this issue.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-09-07 11:50 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
2019-09-07 11:24     ` Arnout Vandecappelle
2019-09-07 11:50       ` Thomas Petazzoni [this message]
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=20190907135036.1de67005@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.