[Koha-bugs] [Bug 13937] Add an Elasticsearch-compatible Z39.50/SRU daemon that can inject item status MARC subfields

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937

--- Comment #202 from David Cook <dcook at prosentient.com.au> ---
(In reply to Ere Maijala from comment #199)
> The path is in a config file, so hard-coding it there there doesn't seem
> quite proper. It doesn't seem possible to specify it programmatically.
> Anyway, it wouldn't help since YAZ 4 and 5 handle some error conditions
> differently, unless I remove the offending tests. That's of course possible
> too, but I would rather not do that unless it's the last option.
> 

I think I don't know enough about the particular test in question to really
continue the conversation. I figured it was a case of providing a configuration
value to a function in the test, but it sounds like perhaps it's a Zebra config
file and that it's an integration test, so I see how that could be tricky. I
withdraw my suggestion heh.

> Now, this strays from the main topic a bit, but as far as I can tell last
> YAZ 4 release was in 2013. That's pretty ancient. Could we decide not to fix
> the tests for such an old version?

That's an interesting question. Looking at
https://packages.debian.org/search?keywords=yaz, I see YAZ 4 is used in Jessie
and Stretch, but Buster and Bullseye use YAZ 5. 

Perhaps we could specify a YAZ 4 run time dependency and YAZ 5 as a build
dependency in the Debian control file? 

But then we probably should be building on the same OSes that we're supporting
at run time, so I think perhaps we do have to support YAZ 4 behaviour until we
don't support Debian Stretch anymore?

-- 
You are receiving this mail because:
You are watching all bug changes.