[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libssh-0.9.4 release archives report 0.9.3
[Thread Prev] | [Thread Next]
- Subject: Re: libssh-0.9.4 release archives report 0.9.3
- From: Andreas Schneider <asn@xxxxxxxxxxxxxx>
- Reply-to: libssh@xxxxxxxxxx
- Date: Tue, 14 Apr 2020 18:33:58 +0200
- To: libssh@xxxxxxxxxx, Jakub Jelen <jjelen@xxxxxxxxxx>
On Tuesday, 14 April 2020 18:16:59 CEST Jakub Jelen wrote: > On Tue, 2020-04-14 at 11:00 -0400, Anderson Sasaki wrote: > > ----- Original Message ----- > > > > > From: "Heiko Thiery" <heiko.thiery@xxxxxxxxx> > > > To: libssh@xxxxxxxxxx > > > Sent: Tuesday, April 14, 2020 3:02:23 PM > > > Subject: libssh-0.9.4 release archives report 0.9.3 > > > > > > Hi all, > > > > > > the release targets for 0.9.4 that can be downloaded from > > > https://git.libssh.org/projects/libssh.git report a lib version > > > 0.9.3. > > > > > > https://git.libssh.org/projects/libssh.git/snapshot/libssh-0.9.4.tar.gz > > > https://git.libssh.org/projects/libssh.git/snapshot/libssh-0.9.4.tar.xz > > > https://git.libssh.org/projects/libssh.git/snapshot/libssh-0.9.4.zip > > > > > > Seems to be a mistake?! > > > > Thank you for reporting. > > > > It seems the LIBSSH_VERSION_MICRO in include/libssh/libssh.h was not > > bumped before the release. We need to avoid this in the future by > > having the version information in a single place. > > The same happened also for 0.8.4. It is already tracked in the > following bug: > > https://bugs.libssh.org/T226 We should have a libssh_version.h.cmake which fills just the version data and gets included in libssh.h Andreas -- Andreas Schneider asn@xxxxxxxxxxxxxx GPG-ID: 8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D
Re: libssh-0.9.4 release archives report 0.9.3 | Heiko Thiery <heiko.thiery@xxxxxxxxx> |
libssh-0.9.4 release archives report 0.9.3 | Heiko Thiery <heiko.thiery@xxxxxxxxx> |
Re: libssh-0.9.4 release archives report 0.9.3 | Anderson Sasaki <ansasaki@xxxxxxxxxx> |
Re: libssh-0.9.4 release archives report 0.9.3 | Jakub Jelen <jjelen@xxxxxxxxxx> |