The actual version ist "NagiosQL 3.4.0 - GIT Version: 2019-04-26" as displayed on main page. Also visible on support page as GIT code version "3.4.0-2019-04-26".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The FreeBSD port of nagiosql is marked as broken now, because the tarball is now unfetchable. When the software detects that the tarball it has has downloaded does not match what is expected for this release (i.e. the SHA256 values has changed), the install will not happen. This is for security reasons.
If a new release had been made (say 3.4.1), then 3.4.0 would still work on FreeBSD. Now it does not work. No new installs can occur until the FreeBSD port is fixed.
I have no doubt that all other package systems are now similarly broken like this.
Last edit: Dan Langille 2019-09-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have now renamed all files on sourceforge. Actually it is not possible to increment the version number without trigger the installer (and database upgrade). This should be fixed in future versions.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Has the 3.4.0 been rerolled? Does it contain the same files as it id back when it was first released?
The FreeBSD port has been marked as unfetchable.
When I investigated, size differences were observed. Specifically, https://downloads.sourceforge.net/project/nagiosql/nagiosql/NagiosQL%203.4.0/nagiosql-3.4.0.tar.bz2 was 1040465 bytes instead of the expected 1032592.
When the FreeBSD port was updated on Nov 10 2019, the size and checksum were recorded then:
I downloaded the latest tarball and compared it to what I had downloaded originally. There were differences.
Please comment on this.
details at this URL: https://gist.github.com/dlangille/a2abff5243355ce58d0d0e60f5fc1725
The actual version ist "NagiosQL 3.4.0 - GIT Version: 2019-04-26" as displayed on main page. Also visible on support page as GIT code version "3.4.0-2019-04-26".
So the answer is yes, the tarball for release 3.4.0 was released on 2019-04-26?
Please be direct.
The tarball on this page will always include all GIT hotfixes. Every time a new bugfix is released on GIT, the tarball will be recreated.
Read first post:
https://sourceforge.net/p/nagiosql/discussion/project_support/thread/2f13c060/
You can also download your tarball directly from GIT:
https://gitlab.com/wizonet/nagiosql/tree/3.4.0
I encourage you to issue a new release each time this happens. Please increment the release number.
Why?
If you don't, I know you will break the FreeBSD package, and I suspect any other package system.
The FreeBSD port of nagiosql is marked as broken now, because the tarball is now unfetchable. When the software detects that the tarball it has has downloaded does not match what is expected for this release (i.e. the SHA256 values has changed), the install will not happen. This is for security reasons.
From https://www.freshports.org/net-mgmt/nagiosql/:
BROKEN: unfetchable
IGNORE: is marked as broken: unfetchable
This is because the size and SHA256 values differ. This a security check.
If a new release had been made (say 3.4.1), then 3.4.0 would still work on FreeBSD. Now it does not work. No new installs can occur until the FreeBSD port is fixed.
I have no doubt that all other package systems are now similarly broken like this.
Last edit: Dan Langille 2019-09-02
I have now renamed all files on sourceforge. Actually it is not possible to increment the version number without trigger the installer (and database upgrade). This should be fixed in future versions.