The rules are as follows:
- the releases version of NaviServer and the modules tar files pm
sourceforge
work together
- the head version on bitbucket are likely to match for the major modules
(not all modules are adjusted immediately to every change).
The same is also true for nswebpush: the released version from sourceforge
should work (was running e.g. a while on openacs.org), the tip versions
are as
well working together (currently running on openacs.org). The changes
are due
to changes in the relatively young ns_crypto support in NaviServer.
The best solution is to produce a new release of NaviServer (just a
matter of
work, not sure, when this can sneak in.
all the best
.gn
On 23.12.19 08:46, Wolfgang Winkler wrote:
Hello!
I think the tip nswebpush version in the repository does not work with
NaviServer 4.99.18.
ns_crypto::eckey sharedsecret
and
ns_base64urldecode -binary
return an error.
I think you could just change the minimal NaviServer version in the
Readme to 4.99.19.
Regards,
Wolfgang
--
*Wolfgang Winkler*
Geschäftsführung
wolfgang.wink...@digital-concepts.com
mobil +43.699.19971172
dc:*büro*
digital concepts Novak Winkler OG
Software & Design
Landstraße 68, 5. Stock, 4020 Linz
www.digital-concepts.com <http://www.digital-concepts.com>
tel +43.732.997117.72
tel +43.699.1997117.2
Firmenbuchnummer: 192003h
Firmenbuchgericht: Landesgericht Linz
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
--
Univ.Prof. Dr. Gustaf Neumann
WU Vienna
Institute of Information Systems and New Media
Welthandelsplatz 1, A-1020 Vienna, Austria
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
