Summary: | Fix search for existing/upgraded Debian package instances | ||
---|---|---|---|
Product: | Koha | Reporter: | Magnus Enger <magnus> |
Component: | Packaging | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | P5 - low | CC: | jonathan.druart, robin, tomascohen |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11596 | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 3087, 9256 | ||
Bug Blocks: |
Description
Magnus Enger
2013-04-07 17:20:52 UTC
Having the script is fine, but it might be worth calling it something else. koha-upgrade-search-fix perhaps. Better name ideas welcome :) Most/many people (i.e. those on marc21) won't have to worry about it, so it might just be worth documenting/mentioning on lists, etc. (In reply to comment #1) > Having the script is fine, but it might be worth calling it something else. > koha-upgrade-search-fix perhaps. Better name ideas welcome :) Most/many > people (i.e. those on marc21) won't have to worry about it, You have tested that, right? Bug 3087 did change syntax="usmarc" to syntax="marc21", so I'm not sure if we are better off updating for all marcflavours, to keep all config files in sync? (In reply to comment #2) > You have tested that, right? Bug 3087 did change syntax="usmarc" to > syntax="marc21", so I'm not sure if we are better off updating for all > marcflavours, to keep all config files in sync? I would have expected to hear screaming from people if it didn't work. We've also done some 3.10 deploys that could search. (In reply to comment #3) > I would have expected to hear screaming from people if it didn't work. We've > also done some 3.10 deploys that could search. Good to hear. It's still a question of if we want to keep the different configs as much in sync as possible or not, though... I think that is a real problem for some users, even if MARC21 users are the majority, so we should figure out a way to fix it in a way people don't miss. Doing it similar to 3.4 sounds logical to me. I added a reference to bug 11596. Having the missing or wrongly configured entries reported will help debugging users' problems. I'm not sure having a shell script modifying the users config files might be worth because of its possible consequences. They are not mutually exclusive anyway. Just saying. Is it fixed or still need to be fixed? (In reply to Jonathan Druart from comment #7) > Is it fixed or still need to be fixed? I haven't heard of it causing any problems lately. Lowering the priority, this is not critical. (In reply to Jonathan Druart from comment #7) > Is it fixed or still need to be fixed? Since there isn't a lot of people complaining about issues related to this, I am tempted to say we close this bug. |