https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36424
Katrin Fischer <katrin.fisc...@bsz-bw.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #19 from Katrin Fischer <katrin.fisc...@bsz-bw.de> ---
(In reply to Pablo AB from comment #18)
> I asked on chat,
> https://chat.koha-community.org/koha-community/pl/drr98y7z13dqxj8mrpjbj8f6je
> giving more details. The issue happen on two instances on two different
> hosts, one of them a production server which I never tried to upgrade out of
> 22.05.x. I have no clue why I did get to have a .06/development and a 040.
> The other host/instance (test/sandbox) have the same strange version.
>
> Not sure also how to solve it either. Just an UPDATE to version, changing
> the `22.0600040` to `22.0500000`? All the schema upgrades are idempotent?
>
> It seems that it's just me, so maybe this bug should be closed.
You could take a backup and try that. The database updates should be
idempotent.
Important bit is to really pay attention on the output of the update script to
see where it gets stuck and resolve any issues found before continuing.
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
