[Bug 27842] New: Incorrect biblionumber handling in serials subscriptions
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Bug ID: 27842 Summary: Incorrect biblionumber handling in serials subscriptions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Serials Assignee: koha-bugs@lists.koha-community.org Reporter: nick@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org It seems that a librarian can edit the biblionumber for a given subscription, however, when receiving serials the biblionumber is pulled from the existing serials, so all new received issues are received on the old biblionumber This is problematic in light of bug 21901 - you can change the biblionumber, the serials still point to the old biblionumber - and deleting the biblio deletes the serials. Additionally, the update will delete serials where this was the case To recreate: 1 - Create a new subscription 2 - Receive an issue 3 - Edit the subscription and change the biblionumber 4 - Receive another issue 5 - SELECT * FROM serial 6 - Both have the old number 7 - Delete the old biblio 8 - The serials are deleted 9 - You also cannot now receive for this issue or generate serials -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |21901 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21901 [Bug 21901] Foreign keys are missing on the serials and subscriptions tables -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.renvoize@ptfs-europe | |.com --- Comment #1 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- Humm.. should the old serials follow the biblionumber change too.. or should the logic be changed such that newly received serials get the update bib and old one's keep the old bib? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Jonathan Druart <jonathan.druart@bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart@bugs.koha-c | |ommunity.org --- Comment #2 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- Why do we have serial.biblionumber? We should get the biblio link using serial->subscription->biblionumber -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Jonathan Druart <jonathan.druart@bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs@lists.koha-commun |jonathan.druart@bugs.koha-c |ity.org |ommunity.org Status|NEW |ASSIGNED -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Jonathan Druart <jonathan.druart@bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #3 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- Created attachment 117565 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=117565&action=edit Bug 27842: Add tests -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #4 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- Created attachment 117566 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=117566&action=edit Bug 27842: Update serial.biblionumber when a subscription is linked with another record It seems that a librarian can edit the biblionumber for a given subscription, however, when receiving serials the biblionumber is pulled from the existing serials, so all new received issues are received on the old biblionumber. This is problematic in light of bug 21901 - you can change the biblionumber, the serials still point to the old biblionumber - and deleting the biblio deletes the serials. Additionally, the update will delete serials where this was the case Test plan: 1 - Create a new subscription 2 - Receive an issue 3 - Edit the subscription and change the biblionumber 4 - Receive another issue 5 - SELECT biblionumber FROM serial => the biblionumber link must have been updated -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Peter Vashchuk <stalkernoid@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Peter Vashchuk <stalkernoid@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #117566|0 |1 is obsolete| | --- Comment #5 from Peter Vashchuk <stalkernoid@gmail.com> --- Created attachment 117567 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=117567&action=edit Bug 27842: Update serial.biblionumber when a subscription is linked with another record It seems that a librarian can edit the biblionumber for a given subscription, however, when receiving serials the biblionumber is pulled from the existing serials, so all new received issues are received on the old biblionumber. This is problematic in light of bug 21901 - you can change the biblionumber, the serials still point to the old biblionumber - and deleting the biblio deletes the serials. Additionally, the update will delete serials where this was the case Test plan: 1 - Create a new subscription 2 - Receive an issue 3 - Edit the subscription and change the biblionumber 4 - Receive another issue 5 - SELECT biblionumber FROM serial => the biblionumber link must have been updated Signed-off-by: Petro Vashchuk <stalkernoid@gmail.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Passed QA -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #117565|0 |1 is obsolete| | Attachment #117567|0 |1 is obsolete| | --- Comment #6 from Kyle M Hall <kyle@bywatersolutions.com> --- Created attachment 117677 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=117677&action=edit Bug 27842: Add tests Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #117677|0 |1 is obsolete| | --- Comment #7 from Kyle M Hall <kyle@bywatersolutions.com> --- Created attachment 117696 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=117696&action=edit Bug 27842: Add tests Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #117696|0 |1 is obsolete| | --- Comment #8 from Kyle M Hall <kyle@bywatersolutions.com> --- Created attachment 117697 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=117697&action=edit Bug 27842: Add tests Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #9 from Kyle M Hall <kyle@bywatersolutions.com> --- Created attachment 117698 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=117698&action=edit Bug 27842: Update serial.biblionumber when a subscription is linked with another record It seems that a librarian can edit the biblionumber for a given subscription, however, when receiving serials the biblionumber is pulled from the existing serials, so all new received issues are received on the old biblionumber. This is problematic in light of bug 21901 - you can change the biblionumber, the serials still point to the old biblionumber - and deleting the biblio deletes the serials. Additionally, the update will delete serials where this was the case Test plan: 1 - Create a new subscription 2 - Receive an issue 3 - Edit the subscription and change the biblionumber 4 - Receive another issue 5 - SELECT biblionumber FROM serial => the biblionumber link must have been updated Signed-off-by: Petro Vashchuk <stalkernoid@gmail.com> Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #10 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 117712 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=117712&action=edit Bug 27842: (follow-up) Correct existing serail/subscriptionhistory before deletion -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #11 from Nick Clemens <nick@bywatersolutions.com> --- I added a followup which should be tested - before we add the constraints and delete we should update serial and subscription history To test: 1 - Checkout a version before 21901 2 - Reset db 3 - Add a subscription 4 - Edit the subscription to a new biblionumber 5 - Update database 6 - Confirm the subscriptionid still has entries in serial and subscriptionhistory -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Andrew Nugged <nugged@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nugged@gmail.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Jonathan Druart <jonathan.druart@bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Signed Off --- Comment #12 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- Can someone test the last patch please? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Frank Hansen <frank.hansen@ub.lu.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |frank.hansen@ub.lu.se -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #13 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I wonder if we are on the right track here by changing the information in past serials or if this doesn't destroy useful information. Serials are known to be odd. When you look at the national serials database they have a graph view on their record detail pages where you can see how often they change their names, merge with others... divide etc. It's pretty, but also scary! And for our catalogers every change like this means a new record. So it makes sense that we can change which record a subscription is attached to. The name change would not necessarily affect the subscription itself. So could it be by design that the original biblionumber was stored? As you said, we don't actually need it, as we have the current biblionumber in the subscription. If it was thought to be for keeping some history, it could make sense and the fix would maybe to stop it from deleting the issues when the record is deleted. We could also think about updating the biblionumber of the next expected issue when the biblionumber is changed. Not sure about this - just something I was wondering about when I noticed the biblionumber in serials in the past. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Jonathan Druart <jonathan.druart@bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nicolas.legrand@bulac.fr, | |severine.queune@bulac.fr --- Comment #14 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- Nicolas, Séverine, could you give us your input on this one? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #15 from Nicolas Legrand <nicolas.legrand@bulac.fr> --- (In reply to Jonathan Druart from comment #14)
Nicolas, Séverine, could you give us your input on this one?
This is far beyond my own skills and from my point of view, understanding serials is a bit like understanding the Necronomicon. Nevertheless, Séverine is working on it with our serials specialists :). -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #16 from Nick Clemens <nick@bywatersolutions.com> --- The database update from 21901 causes data loss - while we can discuss future handling, currently a serial that changed biblios and the old record was deleted will remove all subscriptionhistory and serial entries for the subscription upon upgrade. Should I move that patch to its own bug to prevent data loss for libraries so we can move that forward? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #17 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- The data loss angle is the one I am worried about as well. With the solution proposed here we lose the former history. That's why I was thinking we might want to check on why the field was there in the first place. Should we just have a patch undoing the constraint for now? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #18 from Nick Clemens <nick@bywatersolutions.com> --- (In reply to Katrin Fischer from comment #17)
The data loss angle is the one I am worried about as well. With the solution proposed here we lose the former history. That's why I was thinking we might want to check on why the field was there in the first place.
Should we just have a patch undoing the constraint for now?
I don't think we are losing anything by setting the biblionumber to the current. In the case of a serial having had 2,3, or more biblionumbers, we are only using the first one - so while one previous connection was "preserved" any future ones were not. Even with one change preserved I don't see any evidence that it was intentional -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #19 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Nick Clemens from comment #18)
(In reply to Katrin Fischer from comment #17)
The data loss angle is the one I am worried about as well. With the solution proposed here we lose the former history. That's why I was thinking we might want to check on why the field was there in the first place.
Should we just have a patch undoing the constraint for now?
I don't think we are losing anything by setting the biblionumber to the current.
In the case of a serial having had 2,3, or more biblionumbers, we are only using the first one - so while one previous connection was "preserved" any future ones were not. Even with one change preserved I don't see any evidence that it was intentional
Can you explain about only using the first one? As I read it we are updating all of them: UPDATE serial JOIN subscription USING (subcriptionid) SET serial.biblionumber = subscription.biblionumber WHERE serial.biblionumber != subscription.biblionumber Why not just update the receive process to use the subscription for pulling the biblionumber and change the constraint to set null on delete? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #20 from Nick Clemens <nick@bywatersolutions.com> --- (In reply to Katrin Fischer from comment #19)
(In reply to Nick Clemens from comment #18)
(In reply to Katrin Fischer from comment #17)
The data loss angle is the one I am worried about as well. With the solution proposed here we lose the former history. That's why I was thinking we might want to check on why the field was there in the first place.
Should we just have a patch undoing the constraint for now?
I don't think we are losing anything by setting the biblionumber to the current.
In the case of a serial having had 2,3, or more biblionumbers, we are only using the first one - so while one previous connection was "preserved" any future ones were not. Even with one change preserved I don't see any evidence that it was intentional
Can you explain about only using the first one? As I read it we are updating all of them:
UPDATE serial JOIN subscription USING (subcriptionid) SET serial.biblionumber = subscription.biblionumber WHERE serial.biblionumber != subscription.biblionumber
Why not just update the receive process to use the subscription for pulling the biblionumber and change the constraint to set null on delete?
Sorry I meant, the serial biblionumber is always the same, i.e.: Create subscription on biblionumber 1 and recieve a serial, it uses biblionumber1 Edit subscription to use biblionumber 2 and receive a serial, it uses biblionumber 1 Edit subscription to use biblionumber 3 and receive a serial, it uses biblionumber on Edit subscription to use biblionumber 4...and so on We are not keeping a history of the biblionumber, but rather keeping only the original biblionumber I don't see that storing 'NULL' or one older biblionumber gains us much over storing the current bibloionumber -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|testopia@bugs.koha-communit |katrin.fischer@bsz-bw.de |y.org | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #21 from Katrin Fischer <katrin.fischer@bsz-bw.de> ---
Sorry I meant, the serial biblionumber is always the same, i.e.: Create subscription on biblionumber 1 and recieve a serial, it uses biblionumber1 Edit subscription to use biblionumber 2 and receive a serial, it uses biblionumber 1 Edit subscription to use biblionumber 3 and receive a serial, it uses biblionumber on Edit subscription to use biblionumber 4...and so on
We are not keeping a history of the biblionumber, but rather keeping only the original biblionumber
I don't see that storing 'NULL' or one older biblionumber gains us much over storing the current bibloionumber
Thx for clearing this up! In that case I see no issue in changing the data. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Victor Grousset/tuxayo <victor@tuxayo.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |victor@tuxayo.net --- Comment #22 from Victor Grousset/tuxayo <victor@tuxayo.net> --- I did the test plan of the 1st patch and got this result in the DB 100 is the initial bibnumber and 101 is the edited one. +----------+--------------+--------+ | serialid | biblionumber | status | +----------+--------------+--------+ | 1 | 101 | 2 | | 2 | 101 | 2 | | 3 | 100 | 1 | +----------+--------------+--------+ This is not expected right? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=28133 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #23 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Filed bug 28133 for my thoughts of a possible future use of the biblionumber field in serials. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #24 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- I bet you get it if you receive another serial item. It's because GetSubscription does not return subscription.biblionumber as the biblionumber, but subscriptionhistory.biblionumber instead. So 2 questions: - Should we update subscriptionhistory.biblionumber=subscription.biblionumber when a subscription is linked to a new biblio? - If so, what's the point of subscriptionhistory.biblionumber? Shouldn't we remove it and use the subscriptionid FK? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #25 from Victor Grousset/tuxayo <victor@tuxayo.net> ---
I bet you get it if you receive another serial item.
IIUC another serial item <=> another issue. So yes, if I got right on the step 4 of the test plan (had to impro--, hum, learn a lot about serial) -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|katrin.fischer@bsz-bw.de |tomascohen@gmail.com CC| |tomascohen@gmail.com Status|Signed Off |Passed QA -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #117712|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #117697|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #117698|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #26 from Tomás Cohen Arazi <tomascohen@gmail.com> --- Created attachment 120239 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=120239&action=edit Bug 27842: Add tests Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com> Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #27 from Tomás Cohen Arazi <tomascohen@gmail.com> --- Created attachment 120240 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=120240&action=edit Bug 27842: Update serial.biblionumber when a subscription is linked with another record It seems that a librarian can edit the biblionumber for a given subscription, however, when receiving serials the biblionumber is pulled from the existing serials, so all new received issues are received on the old biblionumber. This is problematic in light of bug 21901 - you can change the biblionumber, the serials still point to the old biblionumber - and deleting the biblio deletes the serials. Additionally, the update will delete serials where this was the case Test plan: 1 - Create a new subscription 2 - Receive an issue 3 - Edit the subscription and change the biblionumber 4 - Receive another issue 5 - SELECT biblionumber FROM serial => the biblionumber link must have been updated Signed-off-by: Petro Vashchuk <stalkernoid@gmail.com> Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com> Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #28 from Tomás Cohen Arazi <tomascohen@gmail.com> --- Created attachment 120241 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=120241&action=edit Bug 27842: (follow-up) Correct existing serail/subscriptionhistory before deletion Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Jonathan Druart <jonathan.druart+koha@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Pushed to master Version(s)| |21.05.00 released in| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 --- Comment #29 from Jonathan Druart <jonathan.druart+koha@gmail.com> --- Pushed to master for 21.05, thanks to everybody involved! -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Fridolin Somers <fridolin.somers@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version(s)|21.05.00 |21.05.00,20.11.06 released in| | CC| |fridolin.somers@biblibre.co | |m Status|Pushed to master |Pushed to stable --- Comment #30 from Fridolin Somers <fridolin.somers@biblibre.com> --- Pushed to 20.11.x for 20.11.06 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Alex Arnaud <alex.arnaud@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |28298 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28298 [Bug 28298] DBRev 19.12.00.076 broken -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Alex Arnaud <alex.arnaud@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alex.arnaud@biblibre.com --- Comment #31 from Alex Arnaud <alex.arnaud@biblibre.com> --- Hello, Changes on DBRev 19.12.00.076 break the updatedatabase (typo). I fixed that on bug 28298. Appart from that, shouldn't these changes be done in a new DBRev ? I think Koha 20.05 or 20.11 will never get the DB fix. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Fridolin Somers <fridolin.somers@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to stable |ASSIGNED Version(s)|21.05.00,20.11.06 |21.05.00 released in| | --- Comment #32 from Fridolin Somers <fridolin.somers@biblibre.com> --- I remove from 20.11.x since it needs more work -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Jonathan Druart <jonathan.druart+koha@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |Passed QA -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Jonathan Druart <jonathan.druart+koha@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Pushed to master --- Comment #33 from Jonathan Druart <jonathan.druart+koha@gmail.com> --- Please follow-up on bug 28298 ASAP. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Fridolin Somers <fridolin.somers@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version(s)|21.05.00 |21.05.00,20.11.06 released in| | Status|Pushed to master |Pushed to stable --- Comment #34 from Fridolin Somers <fridolin.somers@biblibre.com> --- Pushed to 20.11.x for 20.11.06 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Andrew Fuerste-Henry <andrew@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to stable |Pushed to oldstable Version(s)|21.05.00,20.11.06 |21.05.00,20.11.06,20.05.12 released in| | CC| |andrew@bywatersolutions.com --- Comment #35 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Pushed to 20.05.x for 20.05.12 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27842 Victor Grousset/tuxayo <victor@tuxayo.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|Pushed to oldstable |RESOLVED --- Comment #36 from Victor Grousset/tuxayo <victor@tuxayo.net> --- Just tested, 19.11.x not affected, no backport. -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org