I recovered my old database (since I did not know what had changed with
the busted install), pushed all the old koha to the side, reinstalled
koha-common, and tried again. It did crash and burn early on, but I
could see what it was doing and managed to manually do the task the
bug-fix was tryi
Ooh. Nice. Thanks. Yes, those files all had 2015 timestamps on them.
And, yes, there were a few of them.
I did a bit of a search and found a lot of files from 2015. Some of
them are school logo files, but most of them are from a legacy Koha install.
Thanks. That gives me a good starting-
Hi Tim,
I am wondering about the existance of this file:
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/local_cover_images.pl
You should not have any files in the atomicupdate directory.
Could this be from a previous update? Have you checked the contents?
Katrin
On 14.
I forgot to add the results of searching for that key:
++---+--+--+--+-+--+
| CONSTRAINT_CATALOG | CONSTRAINT_SCHEMA | CONSTRAINT_NAME |
TABLE_SCHEMA | TABLE_NAME | CONSTRAINT_TYPE | EN
Well, it appears that the issue is with this file:
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/local_cover_images.pl
When I manually try to run the sql "create table", I am getting:
ERROR 1826 (HY000): Duplicate foreign key constraint name
'bibliocoverimage_fk1'
The
and Koha is 24.1101000 at
/usr/share/koha/lib/C4/Auth.pm line 766.
This seems to me like a bug. Can anyone confirm it?
Best Regards,
Paulo Neto
-Mensagem original-
De: Koha Em Nome De René Seindal
Enviada: 14 de janeiro de 2025 12:51
Para: Koha
Assunto: Re: [Koha] Upgrade to 24.11.01
Hi again,
A short follow-up.
The update was from 24.05.03 to 24.11.01.
I hadn't upgraded to 24.11.00 first - but that is no longer available in
the repository.
For now, I have rolled back everything. Next time I'll upgrade on a copy
of the VM :-)
René
On 14/01/2025 11.55, René Seindal wr
Hang on, I just reran the upgrade, and it succeeded. Please ignore this
message.
Daniel
On 7/16/24 10:09 AM, Daniel Owens wrote:
I was upgrading my packages on Ubuntu this morning and the upgrade
failed. The step that failed was:
Upgrade to 23.12.00.044 [14:48:14]: Bug 36120 - Add pic
Hi Anke,
assuming you will do a test run of the update anyway, I don't think
there is an advantage in updating to 22.05 first. It's very common to
jump over multiple versions and you should always end up with the exact
same database structure, no matter where you are coming from.
Hope this helps
Hey,
Le jeu. 20 juil. 2023 à 10:40, Bruns, Anke a écrit :
> Hi all,
>
> we are considering an upgrade from 22.05 to 23.05 - in your experience
> would
> it be good to upgrade directly or to go first to 22.11 and then from there
> to 23.05?
>
I usually find it pretty straightforward to jump vers
Druart
mailto:jonathan.dru...@bugs.koha-community.org>>
Enviada: 6 de junho de 2023 11:06
Para: Paulo Neto mailto:pn...@dgadr.pt>>
Cc: koha mailto:koha@lists.katipo.co.nz>>
Assunto: Re: [Koha] upgrade error running koha-upgrade-schema
Hi Paulo,
You have values in illrequests.ill
Hi Paulo,
You have values in illrequests.illrequests_safk that are not defined in the
authorised_values values.
Regards,
Jonathan
Le mar. 6 juin 2023 à 11:20, Paulo Neto a écrit :
> Hello all,
>
> I've been trying to upgrade my koha 18.11 to version 22.11.
>
> When i run the comand koha-upgrade-
hi Taimoor,
what koha version are you upgrading from/to?
what does the following command say?
$ sudo koha-mysql library -e ' select value from systempreferences where variable =
"version" '
++
| value |
++
| 21.1117000 | <
++
On 12/04/23 3
On 3/15/23 23:44, Mason James wrote:
On 15/03/23 11:22 am, Bruce A. Metcalf wrote:
On 3/14/23 01:05, Mason James wrote:
On 14/03/23 5:53 pm, Mason James wrote:
On 13/03/23 5:13 am, Bruce A. Metcalf wrote:
On 3/12/23 10:34, Katrin Fischer wrote:
There is a log3perl.conf file in my /etc/koha
On 15/03/23 11:22 am, Bruce A. Metcalf wrote:
On 3/14/23 01:05, Mason James wrote:
On 14/03/23 5:53 pm, Mason James wrote:
On 13/03/23 5:13 am, Bruce A. Metcalf wrote:
On 3/12/23 10:34, Katrin Fischer wrote:
There is a log3perl.conf file in my /etc/koha/sites/(instance)/ directory, and
it
On 15/03/23 11:22 am, Bruce A. Metcalf wrote:
On 3/14/23 01:05, Mason James wrote:
On 14/03/23 5:53 pm, Mason James wrote:
On 13/03/23 5:13 am, Bruce A. Metcalf wrote:
On 3/12/23 10:34, Katrin Fischer wrote:
There is a log3perl.conf file in my /etc/koha/sites/(instance)/ directory, and
it
On 3/14/23 01:05, Mason James wrote:
On 14/03/23 5:53 pm, Mason James wrote:
On 13/03/23 5:13 am, Bruce A. Metcalf wrote:
On 3/12/23 10:34, Katrin Fischer wrote:
To review, an upgrade to 21.11 (OldOldStable) and Debian 10 results
in [Internal Server Error] screens.
the short version is that
On 14/03/23 5:53 pm, Mason James wrote:
On 13/03/23 5:13 am, Bruce A. Metcalf wrote:
On 3/12/23 10:34, Katrin Fischer wrote:
the internal server error will resolve to something more meaningful in
the logs. Check your logs on the server for the full error message.
I've looked at the tail of
On 13/03/23 5:13 am, Bruce A. Metcalf wrote:
On 3/12/23 10:34, Katrin Fischer wrote:
the internal server error will resolve to something more meaningful in
the logs. Check your logs on the server for the full error message.
I've looked at the tail of all logs in /var/log/koha/(instance)/, bu
On 3/12/23 10:34, Katrin Fischer wrote:
the internal server error will resolve to something more meaningful in
the logs. Check your logs on the server for the full error message.
I've looked at the tail of all logs in /var/log/koha/(instance)/, but
most are empty and the others don't give me
Hi Bruce,
the internal server error will resolve to something more meaningful in
the logs. Check your logs on the server for the full error message.
Hope this helps,
Katrin
On 11.03.23 20:48, Asst. Sec. Bruce A. Metcalf wrote:
Hi gang
Back again after a forced suspension of work.
I am tryin
Hi gang
Back again after a forced suspension of work.
I am trying to upgrade from Koha 21.05 on Debian 9 to 21.11
(OldOldStable) on Debian 10.
The upgrade appears to go through, but both public and staff interface
display [Internal Server Error].
System was working fine on 21.05/9, and all
Le 17 février 2023 11:09:33 GMT+00:00, "Chief Librarian, SAIACS"
a écrit :
>E: Failed to fetch
>http://security.ubuntu.com/ubuntu/pool/main/a/apache2/apache2-data_2.4.41-4ubuntu3.13_all.deb
> 500 Internal Server Error [IP: 185.125.190.39 80]
>E: Unable to fetch some archives, maybe run apt-get
Koha Upgrade the old stable version.
https://libpowertech.blogspot.com/2019/11/how-to-upgrade-koha.html
https://wiki.koha-community.org/wiki/Koha_on_Debian
On Mon, Feb 13, 2023 at 1:21 PM Laxmi Lal Menaria
wrote:
> Good Morning All!
>
> We have installed koha - 17.11.02, and would like to upgrad
I just changed the language setting to English (en) and removed the
(eng-GB) translation. Now the menus are correct in the system preferences.
Our production system is running 22.05.05 and it also has the same problem
with menus (the test site is on 22.11).
Is there a bug already filed?
I wonder
Hi Elaine,
you mention problems with the translations - does everything work ok
with English (en) or are the problems with the system preferences also
present there?
If the problem is present without translations too, could you create a
report and show the results?
SELECT * from systempreferenc
Jonathan Druart wrote:
> Yes, definitely, it must be owned by the $INSTANCE-koha user
PETRIDIS wrote:
Just checked my system’s files and log4perl.conf is indeed owned by root,
however has rw set for all.
FWIW, in order to get back to work, I restored from backup and found:
-rw-r--r-- 1 r
Just checked my system’s files and log4perl.conf is indeed owned by root,
however has rw set for all.
Στις Τετ 30 Νοε 2022 στις 9:24 πμ ο χρήστης Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> έγραψε:
> Yes, definitely, it must be owned by the $INSTANCE-koha user
>
> Le lun. 28 nov.
Yes, definitely, it must be owned by the $INSTANCE-koha user
Le lun. 28 nov. 2022 à 21:38, Bruce A. Metcalf
a écrit :
> On 11/28/22 16:52, Jonathan Druart wrote:
>
> > Did you upgrade using the debian packages?
>
>
> Yes; always.
>
>
> > The error is saying you don't have the log4perl config fi
On 11/28/22 16:52, Jonathan Druart wrote:
Did you upgrade using the debian packages?
Yes; always.
The error is saying you don't have the log4perl config file, which
needs to be at /etc/koha/sites/$INSTANCE/log4perl.conf
This file exists, but I note that it's owned by "root", and not
"i
Did you upgrade using the debian packages?
The error is saying you don't have the log4perl config file, which
needs to be at /etc/koha/sites/$INSTANCE/log4perl.conf
Le lun. 28 nov. 2022 à 15:34, Bruce A. Metcalf
a écrit :
>
> On 11/28/22 15:07, Jonathan Druart wrote:
>
> > Did you restart koha-c
On 11/28/22 15:07, Jonathan Druart wrote:
Did you restart koha-common?
Yes, I rebooted the whole virtual machine. No change.
Do you have an error in the Koha logs?
intranet-error.log
[Mon Nov 28 09:30:06.112562 2022] [cgi:error] [pid 13388] [client ... ]
AH01215: Configuration not def
Hello,
Did you restart koha-common? Do you have an error in the Koha logs?
Run the following command for watch the logs: tail -f /var/log/koha/*/*.log
Regards,
Jonathan
Le lun. 28 nov. 2022 à 13:19, Bruce A. Metcalf
a écrit :
>
> Greetings,
>
> Yes, I'm slow on the uptake, I've been running old
key
constraint 'reserves_ibfk_4'
Any other thoughts?
Thanks again!
Steve
From: Evan Mungai Njoroge
Sent: Wednesday, October 05, 2022 2:16 AM
To: Steve Nickerson
Cc: koha
Subject: Re: [Koha] Upgrade assistance
I had the same issue upgrading from Koha 22.05.04.001 to 22.05.05.00
Evan Mungai Njoroge
Sent: Wednesday, October 05, 2022 2:16 AM
To: Steve Nickerson
Cc: koha
Subject: Re: [Koha] Upgrade assistance
I had the same issue upgrading from Koha 22.05.04.001 to 22.05.05.000.
This came in handy -
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31086
I had the same issue upgrading from Koha 22.05.04.001 to 22.05.05.000.
This came in handy -
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31086
*SOLUTION:*
Log in to MySQL/Maria, change database to the instance DB;
Run;
*ALTER TABLE reserves MODIFY COLUMN `branchcode` varchar(10) COL
Hi D. Gnanasekaran
You wrote:
> I am using the version 19.05 and would like to upgrade to the higher
> versions. May I know the step by step procedures for the upgrade?
> with thanks,
You will find the official upgrading instructions at
https://wiki.koha-community.org/wiki/Koha_on_Debian#Upgrad
ara: Tomas Cohen Arazi ; koha
Asunto: Re: [Koha] Upgrade to 21.11 - problems with extensions (coverflow and
Koha as a CMS)
Hi Tomas.
Thank you so much. The coverflow is running.
Now I have to figure out how to make the static pages work again. Does anyone
know how to do this?
Thank you for your h
p.m.
Para: Isabel Pineda
CC: koha
Asunto: Re: [Koha] Upgrade to 21.11 - problems with extensions (coverflow and
Koha as a CMS)
There is a comment on the coverflow configuration page about how to choose an
id as the selector. It is important to use double quotes around the "#selector"
b
There is a comment on the coverflow configuration page about how to choose
an id as the selector. It is important to use double quotes around the
"#selector" because the configuration is in YAML format and as such the #
symbol is considered a comment (i.e. Is not taken into account).
Hope it dices
Hi Tom,
a) we assume that if we wanted to move from 19.11 to 20.11, we would have to do
it in two stages, i.e. first to 20.05 and subsequently to 20.11 - is this a
correct assumption?; and
It should automatically upgrade the missing versions (first 20.05 then
20.11). I don't think you will ne
Hi Tom,
a) we assume that if we wanted to move from 19.11 to 20.11, we would have to do
it in two stages, i.e. first to 20.05 and subsequently to 20.11 - is this a
correct assumption?; and
It should automatically upgrade the missing versions (first 20.05 then
20.11). I don't think you will ne
Hi Tom,
also, some information on the upgrade process can be found here:
https://wiki.koha-community.org/wiki/Koha_on_Debian#Upgrade
Katrin
On 23.08.21 17:29, Katrin Fischer wrote:
Hi Tom,
others might add to this, but
a) you don't need to update from one version to another in steps/stages.
Hi Tom,
others might add to this, but
a) you don't need to update from one version to another in steps/stages.
You can directly update from 19.11 to 20.11.
b) the update will take care of the database changes required for all
instances of a Koha installation.
That said, it's always recommended
Hi there.
I strongly advise you to:
1. Find and dump the koha database (I assume MySQL engine)
2. Move from installing software on baremetal to docker containers
Cheers.
Javier
On Mon, 23 Aug 2021 at 16:50, Tom Burke wrote:
> Hello the list
>
> I am a new volunteer IT help for a small numbe
sabel Pineda
-Mensaje original-
De: Koha [mailto:koha-boun...@lists.katipo.co.nz] En nombre de Mark Alexander
Enviado el: viernes, 25 de junio de 2021 06:24 p.m.
Para: koha
Asunto: Re: [Koha] Upgrade OS - Ubuntu 18.04 to 20.04
Excerpts from Alvaro Cornejo's message of 2021-06-25 18:2
de junio de 2021 05:26 p.m.
Para: Isabel Pineda
CC: koha@lists.katipo.co.nz
Asunto: Re: [Koha] Upgrade OS - Ubuntu 18.04 to 20.04
Hi Isabel,
We also use a VPS provider (Linode) for the koha hosting.
What we do when migrating to a major version is to create a new VPS, install
everything from
hi Mesfin
this page looks helpful...
https://mariadb.com/kb/en/troubleshooting-row-size-too-large-errors-with-innodb
On 28/06/21 8:17 pm, Mesfin Teshome wrote:
Greetings everyone, I have been trying to upgrade Koha 20.05.06.000 to the latest
version for some time now and every time I tr
Excerpts from Alvaro Cornejo's message of 2021-06-25 18:25:51 -0500:
> We also use a VPS provider (Linode) for the koha hosting.
>
> What we do when migrating to a major version is to create a new VPS,
> install everything from scratch, move the DB from the old system to the new
> one, do the DB c
Hi Isabel,
We also use a VPS provider (Linode) for the koha hosting.
What we do when migrating to a major version is to create a new VPS,
install everything from scratch, move the DB from the old system to the new
one, do the DB conversion and test that everything goes as expected.
As is a secon
...and searching my old email...I found:
from :
Tomas Cohen Arazi
"I suggest you create an empty instance named the same as the 'old one', so
all configuration files are fresh.
Then adjust apache and friends, rsync the /var/lib/koha/ dir,
load a DB dump and run koha-upgrade-schema "
This is from
Hi,
we had access to the Koha source code so we looked up there what changes
were done to kohastructure.sql and in our case we were lucky that we
could discard all the changes there. So basically what we did then was a
set of SQL queries that reverted the DB schema back to kohastructure.sql
from c
It's not stuck at 17.12.00.000 (Tē tōia, tē haumatia), but the next
one: 17.12.00.001 (Bug 19724 - Add [deleted]biblio_metadata.timestamp)
It can be a bit long depending on the size of your DB. Try again and
be patient :)
Le ven. 11 sept. 2020 à 09:57, vinod mishra a écrit :
>
> Hello
>
> Why upg
On 10/09/2020 08:24, Jonathan Druart wrote:
> Late hi!
No problem, better late than never!
> Yes Nigel, your upgrade steps are exactly what need to be done.
> However step "10" must be "restart all the things", which is:
> memcached, apache2 and plack.
OK... useful to know. I had done a machine
Late hi!
Yes Nigel, your upgrade steps are exactly what need to be done.
However step "10" must be "restart all the things", which is:
memcached, apache2 and plack.
And, optionally, 11. check the about page if everything is ok ("server
information" and "system information" tabs)
Enjoy the new fea
Thanks Nigel for reporting your success. I have an upgrade from Ubuntu 16.04 /
Koha 17.11 and wonder about such things. In need to clone my VM and try and
upgrade but I’ve been putting t off...
Your success of a much harder upgrade is very encouraging.
Regards
Alex Shepherd
Sent from my iPad
On 09/09/2020 17:24, Nigel Titley wrote:
>
>> And answering my own question, it looks like it might be possible to
>> export the book inventory in MARC format and the Patrons as a CSV file.
>> And possibly the transactions in an offline format? If the worst comes
>> to the worst I can lose the t
> And answering my own question, it looks like it might be possible to
> export the book inventory in MARC format and the Patrons as a CSV file.
> And possibly the transactions in an offline format? If the worst comes
> to the worst I can lose the transactions.
>
> Does that sound like a plan?
A
On 09/09/2020 15:34, Nigel Titley wrote:
> I'm running an extremely antique version of Koha 3.08.07 on Debian Squeeze.
>
> For various reasons (mainly the fact that the system is enormously
> stable) nothing has been upgraded for a long while but it's getting to
> the point where I need to upgra
Hi Heinrich,
You should replace your database/instance name where needed.
The backup I was referring to is a mysqldump of your original DB 16.11.
See below other comments,
Regards,
Alvaro
||
Stay safe / C
Hallo Alvaro,
I run my server as a vmware virtual machine - so it is very easy for me
to return to a snapshot.
Following your advice (but starting with the current state virtual
machine running koha 17.11 ) I did
#sudo koha-upgrade-schema YourInstance
#sudo koha-rebuild-zebra -v -f YourInstance
Hi Heinrich
It seems the db upgrade schema had an error in the upgrade process.
I'll suggest you try to run the db upgrade schema to see if that works.
Always do a DB backup before tweaking it.
#sudo koha-upgrade-schema YourInstance
Then recreate your index
#sudo koha-rebuild-zebra -v -f YourIns
Hi Alex,
We just move from Ubuntu 16.04 to 18.04, koha from 17.05 to 19.11 and went
from a 1core 2GB Ram box to a 2 core 4 GB Ram box.
What we did was to install everything from scratch in a new Linode and
then move the DB from old machine to the new one. Do all tests needed and
when satisfied,
Dear Michael,
Thanks a lot, it works.
Regards,
Zahid Hossain Shoeb
--
Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailma
Hi Zahid Hossain
> How to upgrade Koha 18.05.x to Koha 18.11.x on Debian 9?
> I have tried but the changes happened from 18.05.05.000 to
> 18.05.11.000 only.
> The commands were -
>
> apt-get update
> apt-get upgrade
> apt-get install koha-common
> koha-rebuild-zebra -v -f
>
> I have not provide
Did you run:
$ sudo apt update
before trying to upgrade?
El mié., 23 ene. 2019 a las 8:00, user233162 ()
escribió:
> Hi,
>
> I have instance of Koha 17.11.05 installed on an Ubuntu
> 16.04 LTS. I would like to upgrade Koha to the current
> version 18.11., but I get the error:
>
> sudo apt-get
Hmm, how did you setup your debian repositories; to follow suit or codename
(https://wiki.koha-community.org/wiki/Debian#Set_up_package_sources) ?.
Either way I'm surprised by your results.. If your tracking by codename and
it's set to 17.11 I would have expected a significantly more recent 17.11
Many thanks, Salvo!
The update to Koha 18.11 worked after I issued the command
sudo apt install libhttp-oai-3.27-perl
as you kindly suggested.
I chose to maintain my old /etc/koha/koha-sites.conf , although a later
comparison with koha-sites.conf.dpkg-dist as provided by the new package
did
Koha version: 17.11.06.000
-- Thank you Sir
Info added to Bugzilla as per Mr. Druarts' request.
On Fri, Jun 15, 2018 at 10:18 AM, Tomas Cohen Arazi
wrote:
> So it is trying to upgrade you to 18.05. Are you sure you want that? I
> suggest that you replace 'stable' with '17.11' for now.
Please comment with your info on
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20826
On Fri, 15 Jun 2018 at 11:03 Scott Owen wrote:
> deb http://debian.koha-community.org/koha stable main
>
> On Fri, Jun 15, 2018 at 9:55 AM, Tomas Cohen Arazi
> wrote:
>
> > Can you share your /etc/a
So it is trying to upgrade you to 18.05. Are you sure you want that? I
suggest that you replace 'stable' with '17.11' for now.
Kind regards.
El vie., 15 jun. 2018 a las 11:03, Scott Owen () escribió:
>
>
>
> deb http://debian.koha-community.org/koha stable main
>
> On Fri, Jun 15, 2018 at 9:55 A
deb http://debian.koha-community.org/koha stable main
On Fri, Jun 15, 2018 at 9:55 AM, Tomas Cohen Arazi
wrote:
> Can you share your /etc/apt/sources.list.d/koha.list config?
>
> El vie., 15 jun. 2018 a las 10:39, Scott Owen ()
> escribió:
>
>> Hi all,
>>
>> I'm trying to upgrade my Koha version
Can you share your /etc/apt/sources.list.d/koha.list config?
El vie., 15 jun. 2018 a las 10:39, Scott Owen () escribió:
> Hi all,
>
> I'm trying to upgrade my Koha version...but got stopped at the following:
>
>
> root@Pine:~# sudo apt-get install koha-common
> Reading package lists... Done
> Bui
OK, a restart of memcached did the trick.
Should have thought of that earlier
Clint.
clint.deckard wrote:
Thanks for the reply Liz,
Yes the instance did exist with koha-create --create-db, I used
koha-remove then koha-restore. The instances are the same name and it is
not 'instance' :)
The
Thanks for the reply Liz,
Yes the instance did exist with koha-create --create-db, I used
koha-remove then koha-restore. The instances are the same name and it is
not 'instance' :)
The odd thing is that I migrated a number of instances with the same
process two weeks ago without issue, but th
On 15/01/18 11:55, clint.deckard wrote:
> Following an upgrade form 16.05 to 17.11 using the packages (and
> koha-restore) on Debian Jessie I get the following error when trying
> to access the staff or opac interface;
> "DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed:
> Access
On 12/07/17 21:17, Mesfin Teshome wrote:
Dear all,Can I upgraded Koha 3.12 directly to Koha 17.05? I am currently
running Koha 3.12 on Ubuntu 14.04. I will really appreciate your help and
feedback on this. Thank you.Regards,Mesfin
You'll need to be very careful.
First, current versions o
It usually takes a few days after a release until it is published to the debian
repositories.
You can view the publshed contents any at any time:
http://debian.koha-community.org/koha/dists/stable/main/binary-amd64/Packages
Petter Goksøyr Åsen
Deichmanske bibliotek / Oslo Public Library
Hi
The Koha release was 2 days ago, but you should wait until the packages are
release, so.. .a litle more of patient ;)
2016-11-24 10:54 GMT+01:00 anjoze :
> Hi all,
> I'm trying to upgrade from version 16.05.05 to latest.
> 2 days ago was released version 16.11.
> I'm using Ubuntu 16.04LTS wit
: [Koha] Upgrade from 3.18 to 3.20.07.000 - Now getting Loading ..
you may continue scanning in Circulation Checkout
Hi,
Il 14/01/2016 09:48, Admire Mutsikiwa ha scritto:
> I have upgrade my Koha system running on Debian 8.2 from Koha 3.18 to
> 3.20.07 . Now which checking out a book it i
Hi,
Il 14/01/2016 09:48, Admire Mutsikiwa ha scritto:
I have upgrade my Koha system running on Debian 8.2 from Koha 3.18 to
3.20.07 . Now which checking out a book it is not displaying the table with
the checkout details such as the due date. Instead, it is displaying the
message
"Loading .
On Thu, Nov 19, 2015 at 7:16 AM, Mark Tompsett wrote:
> Greetings,
>
> Indranil's suggested process direction seems good.
>
> Though, sometimes an upgrade is an opportunity to lose the junk.
> However, perhaps you may wish to take this opportunity to do a fresh
> install, and import cleaned MARC r
Thank you - clean install sounds like a very good option. Is there an easy way
to export the data I need or is it more the case copying the database tables
from old instance to the new?
Best Regards
Damien Mannix
Senior Systems Administrator
Email Reference | M02...E
AMOG Pty Ltd
19 Bus
Greetings,
Indranil's suggested process direction seems good.
Though, sometimes an upgrade is an opportunity to lose the junk.
However, perhaps you may wish to take this opportunity to do a fresh
install, and import cleaned MARC records into the fresh install? I would
also take note of any oth
Hi Damien,
On Thu, Nov 19, 2015 at 6:47 AM, Indranil Das Gupta wrote:
> Hi Damien,
>
> On Thu, Nov 19, 2015 at 6:30 AM, damienm
> wrote:
>> Hi,
>>
>> I'm new to Koha and have inherited a very old koha install. I'm wanting to
>> move the instance to a new VM and thought it may be a good opportu
Hi Damien,
On Thu, Nov 19, 2015 at 6:30 AM, damienm wrote:
> Hi,
>
> I'm new to Koha and have inherited a very old koha install. I'm wanting to
> move the instance to a new VM and thought it may be a good opportunity to
> upgrade too. Can anyone please assist in the recommend steps to do so?
>
>
Could you have a look at the DB backup you did before the update and
confirm there is a primary key on the reserve table?
2015-09-01 11:42 GMT+01:00 vinod mishra :
> Thanks Dear Jonathan,
>
> So may i know what exactly to do step by step to overcome the situation as i
> am trying nut due to my tec
Thanks Dear Jonathan,
So may i know what exactly to do step by step to overcome the situation as
i am trying nut due to my technical limitations i could not able to do.
Thanking You.
On Tue, Sep 1, 2015 at 2:12 PM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:
> Hi Vinod,
>
Hi Vinod,
As it said in the error, you already had a primary key defined on the table.
old_reserves shouldn't have a primary key on old_reserves before 3.09.00.025.
Note that there was a bug in this update database entry, have a look
at bug 10185. But it exists in 3.20.*
Regards,
Jonathan
2015-
* Lenora Oftedahl (o...@critfc.org) wrote:
> We're upgrading to 3.18, but we are not having any luck with getting the
> Search to work. Found the bit about 941$n=1, but we're not sure what that
> means and where that goes.
>
Hi Lenora
We are going to need some more information, how was your K
The latest release of 3.16 (3.16.4) fixed some bugs - I would recommend
you install that.
We are usually fairly early adopters of the new versions, but one of the
bugs in 3.16 was a blocker for us (and has now been fixed). We will be
changing our system over from 3.14.06 to 3.16.4 shortly. Af
Hi Jack,
On Tue, Oct 7, 2014 at 5:55 AM, vinod kumar wrote:
> upgrade to 3.14
When 3.18 is released sometime next month, 3.16 will become Koha's
'old stable' release. If you is going to upgrade now, it makes little
sense to go for a version that is slated to go out of active
development / bugfi
upgrade to 3.14
On Tue, Oct 7, 2014 at 7:32 AM, jmorash wrote:
> We are currently running version 3.12. Would it be recommended or
> advisable to upgrade to 3.14 or 3.16?
> What are the differences?
>
> Thanks Jack
>
> Sent via the Samsung GALAXY S® 5, an AT&T 4G LTE smartphone
> _
Hi!
The following page on the wiki tries to explain how to "migrate" from a
non-packages install to a packages install:
http://wiki.koha-community.org/wiki/Moving_an_installation_from_a_regular_install_to_the_Debian_packages
I am not sure how many people habe used that page yet, so there might be
Hi Greg,
On Mon, Jun 9, 2014 at 8:52 PM, Greg Ashe wrote:
> Is it possible to transfer the Koha database from old machine to the new
> machine in a simple manner (eg dump entire database from old and restore to
> new)?
Yes, have a look here
http://lists.katipo.co.nz/public/koha/2012-June/03311
Mark,
Thank you. I want to use packages but my current installation is from tarball
which was done since 3.0. I am now on 3.12. How do I switch to package without
losing my current installation and configuration
Mesfin
Free
Sent from Yahoo Mail on Android
___
Greetings,
On Fri, Jun 6, 2014 at 3:56 PM, Mesfin Teshome wrote:
How do I upgrade from source installation using Koha repository or is
my option to upgrade using tar file only? My installation is Koha 3.12
which was installed using the tar file.
I would recommend trying to move away from a
You can upgrade the Koha by following the instructions in
http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_tarball#Upgrade_Instructions
.
Dibyendra Hyoju
On Fri, Jun 6, 2014 at 3:56 PM, Mesfin Teshome wrote:
> Dear all,
>How do I upgrade from source installation using Koha repository o
To follow up on this a bit more, some of my problems were from strict
checking in MySQL (see separate post) but a lot of others fall into
these categories:
- Tables which already exist
- Columns which already exist
- Unable to write duplicate keys
Some of these might be OK to let ride. Others
Joel Ewy schreef op vr 02-05-2014 om 01:48 [+]:
> I followed the instructions at:
> http://wiki.koha-community.org/wiki/Moving_an_installation_from_a_regular_install_to_the_Debian_packages
> and imported a backup of the database into a new instance. I can now run
> the programs to update the d
1 - 100 of 143 matches
Mail list logo
