https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26893 --- Comment #16 from Mason James <mtj@kohaaloha.com> --- (In reply to David Cook from comment #10)
(In reply to Martin Renvoize from comment #9)
In my understanding we aren't using any of those methods directly with Koha... it's rather than many of those methods are used in Mojolicious::Plugin::OpenAPI which we're using. Said plugin has been updated to reflect the changes in JSON::Validator but it also requires a new Mojolicious than we're currently supporting I think..
Hense, I don't think it's just a case of updating Koha code, but rather tracking down the versions we wish to support and pinning ourselves to them properly again.
I had a feeling that might be the case.
Alternatively, could we pin JSON::Validator to an older version?
i asked for 'pinning' advice in the debian #packaging irc channel it's impossible to pin an older package without instructing users to manually add an entry to their /etc/apt/preferences.d dir we could automate that task within koha-common, or another helper package - but that is probably considered inappropriate behaviour for a package (for security reasons) the workaround for pinning, is to name the package using the +really convention described here -> https://www.debian.org/doc/debian-policy/ch-controlfields.html -- You are receiving this mail because: You are watching all bug changes.