[Buildroot] [autobuild.buildroot.net] Your daily results for 2019-09-01

Chris Packham judge.packham at gmail.com
Mon Sep 9 09:29:27 UTC 2019


On Sun, Sep 8, 2019 at 7:13 AM Arnout Vandecappelle <arnout at mind.be> wrote:
>
>
>
> On 07/09/2019 13:50, Thomas Petazzoni wrote:
> > Hello,
> >
> > On Sat, 7 Sep 2019 13:24:47 +0200
> > Arnout Vandecappelle <arnout at 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.
>
>  AFAIU, release-monitoring regularly polls and will keep anything it ever
> received. So only if there are two updates between the pols, a version could be
> missed.
>
> > Also, for now release-monotoring.org still remembers about the invalid
> > versions from syslog-ng. I'll report this issue.
>
>  That's pretty annoying, since the syslog-ng version is higher...
>

Actually I've just discovered that eventlog isn't a separate package
any more[1]. Which is why we're having trouble finding it. I'll send a
patch to drop it.

[1] - https://github.com/balabit/syslog-ng/commit/3a114e1c2fd8eef1ff6644de5dc113a9e5a6587e


More information about the buildroot mailing list