* [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-09-01 [not found] <5d6cb406.1c69fb81.71217.d243SMTPIN_ADDED_MISSING@mx.google.com> @ 2019-09-05 0:46 ` Chris Packham 2019-09-05 7:24 ` Thomas Petazzoni 0 siblings, 1 reply; 6+ messages in thread From: Chris Packham @ 2019-09-05 0:46 UTC (permalink / raw) To: buildroot Hi Thomas & All, On Mon, Sep 2, 2019 at 6:17 PM Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote: > > Hello, > > Outdated packages > ================= > > This is the list of packages for which a new version has been detected > and for which you are a registered developer. Please help us improving > the quality of Buildroot by bumping these packages to their latest > version. Thanks! > > 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). ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-09-01 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 0 siblings, 1 reply; 6+ messages in thread From: Thomas Petazzoni @ 2019-09-05 7:24 UTC (permalink / raw) To: buildroot 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-09-01 2019-09-05 7:24 ` Thomas Petazzoni @ 2019-09-07 11:24 ` Arnout Vandecappelle 2019-09-07 11:50 ` Thomas Petazzoni 0 siblings, 1 reply; 6+ messages in thread From: Arnout Vandecappelle @ 2019-09-07 11:24 UTC (permalink / raw) To: buildroot On 05/09/2019 09:24, Thomas Petazzoni wrote: > 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. There's https://github.com/balabit/eventlog/blob/master/VERSION - can release-monitoring use that? Regards, Arnout ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-09-01 2019-09-07 11:24 ` Arnout Vandecappelle @ 2019-09-07 11:50 ` Thomas Petazzoni 2019-09-07 19:13 ` Arnout Vandecappelle 0 siblings, 1 reply; 6+ messages in thread From: Thomas Petazzoni @ 2019-09-07 11:50 UTC (permalink / raw) To: buildroot 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-09-01 2019-09-07 11:50 ` Thomas Petazzoni @ 2019-09-07 19:13 ` Arnout Vandecappelle 2019-09-09 9:29 ` Chris Packham 0 siblings, 1 reply; 6+ messages in thread From: Arnout Vandecappelle @ 2019-09-07 19:13 UTC (permalink / raw) To: buildroot On 07/09/2019 13:50, Thomas Petazzoni wrote: > 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. 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... Regards, Arnout ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-09-01 2019-09-07 19:13 ` Arnout Vandecappelle @ 2019-09-09 9:29 ` Chris Packham 0 siblings, 0 replies; 6+ messages in thread From: Chris Packham @ 2019-09-09 9:29 UTC (permalink / raw) To: buildroot On Sun, Sep 8, 2019 at 7:13 AM Arnout Vandecappelle <arnout@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@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 ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-09-09 9:29 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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
2019-09-07 19:13 ` Arnout Vandecappelle
2019-09-09 9:29 ` Chris Packham
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox