From victor at tuxayo.net  Fri Oct  1 18:01:35 2021
From: victor at tuxayo.net (Victor Grousset/tuxayo)
Date: Fri, 1 Oct 2021 18:01:35 +0200
Subject: [Koha-devel] Can we add HTML classes to add semantic to
 elements when writing automated UI tests?
In-Reply-To: <CAJzKNY6KdtQH8hnH1adtPaZEqJVMbtzSfOU9m5awLazA=kCK-w@mail.gmail.com>
References: <78e08fe6-74d1-5c7c-ec77-f0612ab44215@tuxayo.net>
 <CAJzKNY6KdtQH8hnH1adtPaZEqJVMbtzSfOU9m5awLazA=kCK-w@mail.gmail.com>
Message-ID: <910dea2e-fb7e-a1e4-3ff8-232f10b21b96@tuxayo.net>

On 21-09-30 08:21, Jonathan Druart wrote:
> Yes, assign a class or id to the element.
> This is done several times in basic_workflow.t

great, right, I could use ids also

Cheers,

-- 
Victor Grousset/tuxayo

From martin.renvoize at ptfs-europe.com  Sat Oct  2 08:28:10 2021
From: martin.renvoize at ptfs-europe.com (Renvoize, Martin)
Date: Sat, 2 Oct 2021 07:28:10 +0100
Subject: [Koha-devel] Replacement of mailman (mailing lists)
In-Reply-To: <920f2e4d-db2a-3c54-0ce3-80e01d00e848@tuxayo.net>
References: <CAJzKNY4pkKQCoVhC_3h687X7tVhXb9p5hyUGrXiLZcKP_Ck6VQ@mail.gmail.com>
 <CAH2zftHcvQp7BCEcosDn8T_Mywa2rk+AWMpMoaHb=cDCo8vivg@mail.gmail.com>
 <048601d794c5$509b4460$f1d1cd20$@prosentient.com.au>
 <920f2e4d-db2a-3c54-0ce3-80e01d00e848@tuxayo.net>
Message-ID: <CAB7SL8AtBsXhvpv6M-bNRtMTywXA_W3HHtBHj9KkmvWsGvbRzA@mail.gmail.com>

Discourse sounds good to me too.. something to work on next cycle?

Do we have a host in mind?

On Fri, 20 Aug 2021, 12:47 am Victor Grousset/tuxayo, <victor at tuxayo.net>
wrote:

> On 21-08-19 08:42, dcook at prosentient.com.au wrote:
> > It does seem like Discourse is reasonably popular although I’ve only
> > engaged with it from the forum perspective. It looks like it does have
> > mailing list support but I don’t know what that means exactly.
>
>
> https://meta.discourse.org/t/what-is-mailing-list-mode/46008
>  > In mailing list mode you will receive one email per post, as happens
> with traditional mailing lists. This is desirable if you prefer to
> interact via email, without visiting the forum website.
>
> https://meta.discourse.org/t/what-is-mailing-list-mode/46008/10
>  > Yes, provided you configure “email reply support” appropriately
>
>
> I just checked on an instance and it's possible to watch a category. It
> would have the same effect as subscribing to a mailing list.
>
> ---
>
> Also, it's possible if it's worth the work to import a mailing list.
> https://meta.discourse.org/t/discourse-vs-email-mailing-lists/54298/1
>
> see
> => How do I import my mailing list?
>
> => My organisation manages multiple mailing lists. Can they be imported
> incrementally?
>
>
>
> Cheers,
>
> --
> Victor Grousset/tuxayo
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211002/24050932/attachment.htm>

From dcook at prosentient.com.au  Tue Oct  5 05:09:41 2021
From: dcook at prosentient.com.au (dcook at prosentient.com.au)
Date: Tue, 5 Oct 2021 14:09:41 +1100
Subject: [Koha-devel] More handy fixes in Zebra 2.2.3
Message-ID: <000601d7b996$7090a6c0$51b1f440$@prosentient.com.au>

Hi all,

 

Does it ever drive you crazy that you can't see what Zebra has indexed when
using ICU (whereas you can with CHR)?

 

I raised an issue via Github, and it looks like Adam has fixed the issue in
Zebra 2.2.3 (released yesterday).

 

https://github.com/indexdata/idzebra/commit/6fb12448757a6429b2af400b97956f8a
1130969b

https://software.indexdata.com/zebra/doc/NEWS

 

The squeaky wheel gets the oil!

 

David Cook

Senior Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia

 

Office: 02 9212 0899

Online: 02 8005 0595

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211005/aeeca757/attachment.htm>

From dcook at prosentient.com.au  Wed Oct  6 06:56:49 2021
From: dcook at prosentient.com.au (dcook at prosentient.com.au)
Date: Wed, 6 Oct 2021 15:56:49 +1100
Subject: [Koha-devel] Issues fetching from Koha Git due to Let's Encrypt
 root certificate expiry
Message-ID: <00a301d7ba6e$926aa330$b73fe990$@prosentient.com.au>

Hi all,

 

Some people might have found they aren't able to fetch from the Koha Git (in
koha-testing-docker for instance). They might be getting the following
error:

 

fatal: unable to access
'https://git.koha-community.org/Koha-community/Koha.git/': server
certificate verification failed. CAfile: none CRLfile: none

 

That seems to be due to the Let's Encrypt root certificate expiry. I imagine
the latest koha-testing-docker probably doesn't have this problem, but if
you're lazy or time poor like me, you can just run the following to get your
existing koha-testing-docker to work again:

 

apt-get update

apt-get install ca-certificates

 

Cheers,

 

David Cook

Senior Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia

 

Office: 02 9212 0899

Online: 02 8005 0595

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211006/80fe31e0/attachment.htm>

From jonathan.druart at bugs.koha-community.org  Wed Oct  6 17:28:39 2021
From: jonathan.druart at bugs.koha-community.org (Jonathan Druart)
Date: Wed, 6 Oct 2021 17:28:39 +0200
Subject: [Koha-devel] Workflow improvement suggestions for security releases
Message-ID: <CAJzKNY5Y4TiCeuTEkNSVre9LkE807mJc6wPswkppf-kzdTNo6w@mail.gmail.com>

Hello devs,

As you must know we had two hard months, several very bad bugs hit us.

The release team had to coordinate and it was not an easy task.
We noticed some flaws in the workflow and I would like to suggest some
improvements to discuss.
The main problematic issue is to backport patch series to different
stable branches.

1. LTS
I think it's time to have a Long Term Support release. We noticed that
some people are still using very old versions, having a version that
is maintained several years could help them.
We could backport critical security bugs only. 4 (5?) years would be great.

2. Communication
Once the issues have been reported and fixed, I've alerted the first
cycle of people around me. Their job was to alert a second cycle.
Should we have a list of people we trust? Ask the (general) mailing
list who wants to be in the loop? That means adding them to the
security group on bugzilla (or at least adding them when the bug has a
fix) and CC them when private discussions take place.

3. Synchronisation
Release maintainers are spread around the world (and timezones suck).
Getting feedback can take time, several days (like: "try", "don't
work", "try again", it's 3 days!).
Then when you plan to release on Wednesday, and things are only ready
on Thursday you need to wait until Monday as part of the world is
still enjoying the weekend!
I don't have a solution for that, apart from the Monday postpone or...
more anticipation.
Same problem for the time of the release, I've picked 12 UTC as the
"most convenient" slot for a release, but it won't (ofc) fit
everybody's needs. My point was that if we communicated enough
beforehand (but not publicly) it should not be a problem.
Let me know if you have ideas to improve that!

4. Infrastructure improvement
We don't have CI/Jenkins for the security repository. We need one!
That must be a top priority of the next cycle. We need to help RMaints
and make the security release process easier and less stressful.

5. Apply patches
We need a script to apply the patches on the different branches,
automatically. That's an easy bit to develop and it will help us a
lot.

6. More visibility on the status of the patches
RM and RMaints must put their progress on the bug report itself. A
comment "Will be pushed, RM had a look at this" or "Backported for..."
should be added.
That must be added to the "Release process" wiki page.

Let us know if you have any questions or remarks.

Cheers,
Jonathan

From kyle.m.hall at gmail.com  Thu Oct  7 13:15:43 2021
From: kyle.m.hall at gmail.com (Kyle Hall)
Date: Thu, 7 Oct 2021 07:15:43 -0400
Subject: [Koha-devel] Workflow improvement suggestions for security
 releases
In-Reply-To: <CAJzKNY5Y4TiCeuTEkNSVre9LkE807mJc6wPswkppf-kzdTNo6w@mail.gmail.com>
References: <CAJzKNY5Y4TiCeuTEkNSVre9LkE807mJc6wPswkppf-kzdTNo6w@mail.gmail.com>
Message-ID: <CACpVHfw8zpDd8B2hkO-fHKOrg1n+Q_efoq-C3BTLb+VB5=-ktg@mail.gmail.com>

>
> 1. LTS
> I think it's time to have a Long Term Support release. We noticed that
> some people are still using very old versions, having a version that
> is maintained several years could help them.
> We could backport critical security bugs only. 4 (5?) years would be great.
>

This has been proposed in the past. The general consensus at the time was
that we as a community want to encourage libraries to stay on the latest
versions of Koha and not to hang back on older versions.
I'm not necessarily opposed,  but such a role will require quite a
commitment.


> 2. Communication
> Once the issues have been reported and fixed, I've alerted the first
> cycle of people around me. Their job was to alert a second cycle.
> Should we have a list of people we trust? Ask the (general) mailing
> list who wants to be in the loop? That means adding them to the
> security group on bugzilla (or at least adding them when the bug has a
> fix) and CC them when private discussions take place.
>

Sounds good!


> 3. Synchronisation
> Release maintainers are spread around the world (and timezones suck).
> Getting feedback can take time, several days (like: "try", "don't
> work", "try again", it's 3 days!).
> Then when you plan to release on Wednesday, and things are only ready
> on Thursday you need to wait until Monday as part of the world is
> still enjoying the weekend!
> I don't have a solution for that, apart from the Monday postpone or...
> more anticipation.
> Same problem for the time of the release, I've picked 12 UTC as the
> "most convenient" slot for a release, but it won't (ofc) fit
> everybody's needs. My point was that if we communicated enough
> beforehand (but not publicly) it should not be a problem.
> Let me know if you have ideas to improve that!
>

We can already schedule our news posts in advance. Perhaps rmaints should
have a non-public area on the ftp server where we could put our tarballs
and such, and a cronjob that would automatically move them to the public
folder and update the symlinks at 12 UTC every day ( if there are files to
move ). I'm not sure how to synchronize the community apt server into this,
but I imagine it could be done. If we get into the habit of scheduling
everything for release at 12 UTC, security release or not, we can probably
get pretty good at it, ironing out the kinks before we have another
security release to deal with.


> 4. Infrastructure improvement
> We don't have CI/Jenkins for the security repository. We need one!
> That must be a top priority of the next cycle. We need to help RMaints
> and make the security release process easier and less stressful.
>

Agreed!


> 5. Apply patches
> We need a script to apply the patches on the different branches,
> automatically. That's an easy bit to develop and it will help us a
> lot.
>

I'm not sure what you mean? Do you mean something that would apply a bug's
patch set to say master, stable and oldstable and report on the bug if it
doesn't apply to one? Or script in qa-test-tools to do that? Something else
entirely?


> 6. More visibility on the status of the patches
> RM and RMaints must put their progress on the bug report itself. A
> comment "Will be pushed, RM had a look at this" or "Backported for..."
> should be added.
> That must be added to the "Release process" wiki page.
>

Sounds good!

Kyle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211007/57bef723/attachment.htm>

From fridolin.somers at biblibre.com  Fri Oct  8 08:17:56 2021
From: fridolin.somers at biblibre.com (Fridolin SOMERS)
Date: Thu, 7 Oct 2021 20:17:56 -1000
Subject: [Koha-devel] Issues fetching from Koha Git due to Let's Encrypt
 root certificate expiry
In-Reply-To: <00a301d7ba6e$926aa330$b73fe990$@prosentient.com.au>
References: <00a301d7ba6e$926aa330$b73fe990$@prosentient.com.au>
Message-ID: <6112e5a7-1f0c-cf11-a017-c44b15125b9d@biblibre.com>

Thanks a lot David.
This certificate expiry has many huge impacts, like some package 
repositories acess.
Be sure to upgrade all your servers.

Best regards

Le 05/10/2021 à 18:56, dcook at prosentient.com.au a écrit :
> Hi all,
> 
> Some people might have found they aren’t able to fetch from the Koha Git 
> (in koha-testing-docker for instance). They might be getting the 
> following error:
> 
> fatal: unable to access 
> 'https://git.koha-community.org/Koha-community/Koha.git/': server 
> certificate verification failed. CAfile: none CRLfile: none
> 
> That seems to be due to the Let’s Encrypt root certificate expiry. I 
> imagine the latest koha-testing-docker probably doesn’t have this 
> problem, but if you’re lazy or time poor like me, you can just run the 
> following to get your existing koha-testing-docker to work again:
> 
> apt-get update
> 
> apt-get install ca-certificates
> 
> Cheers,
> 
> David Cook
> 
> Senior Software Engineer
> 
> Prosentient Systems
> 
> Suite 7.03
> 
> 6a Glen St
> 
> Milsons Point NSW 2061
> 
> Australia
> 
> Office: 02 9212 0899
> 
> Online: 02 8005 0595
> 
> 
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
> 

-- 
Fridolin SOMERS <fridolin.somers at biblibre.com>
Software and system maintainer 🦄
BibLibre, France

From kohanews at gmail.com  Wed Oct 13 21:11:21 2021
From: kohanews at gmail.com (Koha Newsletter)
Date: Wed, 13 Oct 2021 21:11:21 +0200
Subject: [Koha-devel] Call for news - Newsletter October 2021
Message-ID: <CAEqgz_kKdhU70Kw9qEUc_FVja55AWZLU3sWVnE=ZRFMw0B6B0A@mail.gmail.com>

Hi

I'm collecting news for the October 2021 Koha Community Newsletter.
Please send anything noteworthy to:

kohanews (at) gmail (dot) com

News criteria:
* News items can be of any length.
* Images are fine.
* Anything and everything Koha.
* Submit by the 26th of the month.

Text format criteria:
* Just structured plain text, or
* HTML text to include tables or similar

For events:
* Consider adding your event to the Koha Community calendar at
https://koha-community.org/calendar/

Thank you!

Michael Kuhn
Editor, Koha Community Newsletter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211013/ee1e2068/attachment.htm>

From jonathan.druart at bugs.koha-community.org  Thu Oct 14 09:03:43 2021
From: jonathan.druart at bugs.koha-community.org (Jonathan Druart)
Date: Thu, 14 Oct 2021 09:03:43 +0200
Subject: [Koha-devel] Roles for 22.05 open
In-Reply-To: <CAJzKNY54cnPaGdvJaifhr4O6aHv1LKV8+BV_K6T_zD5NhxEBCQ@mail.gmail.com>
References: <CAJzKNY54cnPaGdvJaifhr4O6aHv1LKV8+BV_K6T_zD5NhxEBCQ@mail.gmail.com>
Message-ID: <CAJzKNY7+ht9vHhw1HF23hPsND+8Mvt0HWOzwthR8LEq1_Cyz5w@mail.gmail.com>

The election of the 22.05 team will take place during the next general
IRC meeting, on Wednesday October 20th 2021, 14:00 UTC.
https://wiki.koha-community.org/wiki/General_IRC_meeting_20_October_2021

There is still plenty of room available!


Le mer. 29 sept. 2021 à 17:12, Jonathan Druart
<jonathan.druart at bugs.koha-community.org> a écrit :
>
> Hello everybody,
>
> The roles for the 22.05 release cycle are now opened.
> The vote will take place during one of the dev meetings in October.
>
> https://wiki.koha-community.org/wiki/Roles_for_22.05
>
> The description of the roles can be found at this wiki page
> https://wiki.koha-community.org/wiki/Project_roles
>
> Regards,
> Jonathan

From martin.renvoize at ptfs-europe.com  Fri Oct 15 09:01:41 2021
From: martin.renvoize at ptfs-europe.com (Renvoize, Martin)
Date: Fri, 15 Oct 2021 08:01:41 +0100
Subject: [Koha-devel] KohaAdvent - Call for idea's
Message-ID: <CAB7SL8D+qkXcF+JTVZP_8WbV2K_4iW4g=LZBD+OuKt=iHjdsjA@mail.gmail.com>

Hi all,

We're looking to organise another Koha advent calendar series this year and
I'm trying to be a bit more organised than last year. (
https://koha-community.gitlab.io/KohaAdvent/)

Last years calendar was themed around building a plugin. This year I'd like
to suggest a broader community theme with best practice guides and how to's
including all the way's people can contribute to the project and get the
most out of the community.

With that in mind, are there any area's anyone would like us to focus on in
particular, any how-to guides you would be keen to see?  Let us know and
I'll try and find the appropriate person to write something up.

Many thanks in advance for your idea's

*Martin Renvoize, MPhys (Hons)*

<https://www.ptfs-europe.com>

Head of Development and Community Engagement



*Phone:* +44 (0) 1483 378728

*Mobile:* +44 (0) 7725 985 636

*Email:* martin.renvoize at ptfs-europe.com

www.ptfs-europe.com


*Sign up for our newsletters here <http://eepurl.com/dPjjkn> or by scanning
the QR code*



Registered in the United Kingdom No. 06416372   VAT Reg No. 925 7211 30

The information contained in this email message may be privileged,
confidential and protected from disclosure. If you are not the intended
recipient, any dissemination, distribution or copying is strictly
prohibited. If you think that you have received this email message in
error, please email the sender at info at ptfs-europe.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211015/00198fd1/attachment.htm>

From oleonard at myacpl.org  Fri Oct 15 15:33:21 2021
From: oleonard at myacpl.org (Owen Leonard)
Date: Fri, 15 Oct 2021 09:33:21 -0400
Subject: [Koha-devel] Built-in offline circulation interface
In-Reply-To: <CAO4qe2MCn92PTug24TW8yyhU9hZ3WL8dPfQorru+WMH2sYkngg@mail.gmail.com>
References: <CAO4qe2MCn92PTug24TW8yyhU9hZ3WL8dPfQorru+WMH2sYkngg@mail.gmail.com>
Message-ID: <CAO4qe2OG9dpHGL9uD==rxKbWrQhWXpUah-HgT==XqKrmWLfV=Q@mail.gmail.com>

> Does anyone use it? The one enabled by the AllowOfflineCirculation
> system preference.

This question elicited a flood of zero responses, and I'm not sure
what that means!

In any case, I've looked at this issue again and discovered that the
feature is broken in up-to-date browsers. It depends on a browser
feature, applicationCache, which is obsolete:

https://support.mozilla.org/en-US/kb/appcache-showing-uncached-or-disabled
https://www.chromestatus.com/feature/6192449487634432

I'm reading that correctly, the "built-in" offline circulation tool
will have to be rewritten.

 -- Owen

From indradg at gmail.com  Fri Oct 15 15:47:33 2021
From: indradg at gmail.com (Indranil Das Gupta)
Date: Fri, 15 Oct 2021 19:17:33 +0530
Subject: [Koha-devel] Built-in offline circulation interface
In-Reply-To: <CAO4qe2OG9dpHGL9uD==rxKbWrQhWXpUah-HgT==XqKrmWLfV=Q@mail.gmail.com>
References: <CAO4qe2MCn92PTug24TW8yyhU9hZ3WL8dPfQorru+WMH2sYkngg@mail.gmail.com>
 <CAO4qe2OG9dpHGL9uD==rxKbWrQhWXpUah-HgT==XqKrmWLfV=Q@mail.gmail.com>
Message-ID: <CAEm3SZ1KYz4ybxX=dB13YMtuOY862=DB5vD=bHuxXo3ZDPrHNw@mail.gmail.com>

Hi Owen,

Koha's offline circ capability is used quite extensively in India, often by
users still on Windows 7 boxes (msft eoled Win7 in Jan 2020 iirc), to tide
over temporary network / connectivity failure usually due to power outages.

Personally I prefer using / implementing .koc file format uploads for
offline syncs.

Cheers
-indranil



On Fri, 15 Oct, 2021, 7:03 pm Owen Leonard, <oleonard at myacpl.org> wrote:

> > Does anyone use it? The one enabled by the AllowOfflineCirculation
> > system preference.
>
> This question elicited a flood of zero responses, and I'm not sure
> what that means!
>
> In any case, I've looked at this issue again and discovered that the
> feature is broken in up-to-date browsers. It depends on a browser
> feature, applicationCache, which is obsolete:
>
> https://support.mozilla.org/en-US/kb/appcache-showing-uncached-or-disabled
> https://www.chromestatus.com/feature/6192449487634432
>
> I'm reading that correctly, the "built-in" offline circulation tool
> will have to be rewritten.
>
>  -- Owen
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211015/98e4f3b3/attachment.htm>

From oleonard at myacpl.org  Fri Oct 15 15:55:54 2021
From: oleonard at myacpl.org (Owen Leonard)
Date: Fri, 15 Oct 2021 09:55:54 -0400
Subject: [Koha-devel] Built-in offline circulation interface
In-Reply-To: <CAEm3SZ1KYz4ybxX=dB13YMtuOY862=DB5vD=bHuxXo3ZDPrHNw@mail.gmail.com>
References: <CAO4qe2MCn92PTug24TW8yyhU9hZ3WL8dPfQorru+WMH2sYkngg@mail.gmail.com>
 <CAO4qe2OG9dpHGL9uD==rxKbWrQhWXpUah-HgT==XqKrmWLfV=Q@mail.gmail.com>
 <CAEm3SZ1KYz4ybxX=dB13YMtuOY862=DB5vD=bHuxXo3ZDPrHNw@mail.gmail.com>
Message-ID: <CAO4qe2PqaUmE0PyvcpN2a0=jq_+zoVSwzmp9QCZAfAVYV9itrQ@mail.gmail.com>

> often by users still on Windows 7 boxes (msft eoled Win7 in Jan 2020 iirc)

For those users there is a Windows application:
https://github.com/bywatersolutions/koha-offline-circulation/releases/tag/v1.3.2

Is that a feasible alternative?

  -- Owen

-- 
Web Developer
Athens County Public Libraries
(740) 737-6006
https://www.myacpl.org

From indradg at gmail.com  Fri Oct 15 16:03:44 2021
From: indradg at gmail.com (Indranil Das Gupta)
Date: Fri, 15 Oct 2021 19:33:44 +0530
Subject: [Koha-devel] Built-in offline circulation interface
In-Reply-To: <CAO4qe2PqaUmE0PyvcpN2a0=jq_+zoVSwzmp9QCZAfAVYV9itrQ@mail.gmail.com>
References: <CAO4qe2MCn92PTug24TW8yyhU9hZ3WL8dPfQorru+WMH2sYkngg@mail.gmail.com>
 <CAO4qe2OG9dpHGL9uD==rxKbWrQhWXpUah-HgT==XqKrmWLfV=Q@mail.gmail.com>
 <CAEm3SZ1KYz4ybxX=dB13YMtuOY862=DB5vD=bHuxXo3ZDPrHNw@mail.gmail.com>
 <CAO4qe2PqaUmE0PyvcpN2a0=jq_+zoVSwzmp9QCZAfAVYV9itrQ@mail.gmail.com>
Message-ID: <CAEm3SZ0wnTXt03mJ8rRRZReARfZZXPYzzUESiV5X6eLvq4fgSA@mail.gmail.com>

Yes, it is.

-idg

On Fri, 15 Oct, 2021, 7:26 pm Owen Leonard, <oleonard at myacpl.org> wrote:

> > often by users still on Windows 7 boxes (msft eoled Win7 in Jan 2020
> iirc)
>
> For those users there is a Windows application:
>
> https://github.com/bywatersolutions/koha-offline-circulation/releases/tag/v1.3.2
>
> Is that a feasible alternative?
>
>   -- Owen
>
> --
> Web Developer
> Athens County Public Libraries
> (740) 737-6006
> https://www.myacpl.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211015/465bfe98/attachment.htm>

From fridolin.somers at biblibre.com  Sat Oct 16 04:59:33 2021
From: fridolin.somers at biblibre.com (Fridolin SOMERS)
Date: Fri, 15 Oct 2021 16:59:33 -1000
Subject: [Koha-devel] Time to translate: string freeze to prepare 20.11.11
 release
Message-ID: <526ce628-ee92-2ed0-5bf9-5c9a57b369bb@biblibre.com>

Hi,

String freeze is into effect 🥶

The 20.11.x maintenance branch is preparing for 20.11.11 release 📦

This means it's the right time to head over to the translation platform:
https://translate.koha-community.org/projects/

Keep in mind that translations must be done with priority on higher 
version 21.05 🔥

Happy translating 🌎🌍🌏

-- 
Fridolin SOMERS <fridolin.somers at biblibre.com>
Software and system maintainer 🦄
BibLibre, France

From bibliwho at gmail.com  Sat Oct 16 14:07:52 2021
From: bibliwho at gmail.com (Cab Vinton)
Date: Sat, 16 Oct 2021 08:07:52 -0400
Subject: [Koha-devel] Built-in offline circulation interface
In-Reply-To: <CAO4qe2PqaUmE0PyvcpN2a0=jq_+zoVSwzmp9QCZAfAVYV9itrQ@mail.gmail.com>
References: <CAO4qe2MCn92PTug24TW8yyhU9hZ3WL8dPfQorru+WMH2sYkngg@mail.gmail.com>
 <CAO4qe2OG9dpHGL9uD==rxKbWrQhWXpUah-HgT==XqKrmWLfV=Q@mail.gmail.com>
 <CAEm3SZ1KYz4ybxX=dB13YMtuOY862=DB5vD=bHuxXo3ZDPrHNw@mail.gmail.com>
 <CAO4qe2PqaUmE0PyvcpN2a0=jq_+zoVSwzmp9QCZAfAVYV9itrQ@mail.gmail.com>
Message-ID: <CABW43URV8YNLcojfkqMv6JcvO03ik4Y6y3FRVD1Hv_iD0Ok8dg@mail.gmail.com>

Fwiw, we'd somehow missed that there was a built-in capability/ system
preference. Always assumed the utility was our only option.

This functionality is an important part of Koha's feature set, so +1
to always having at least one up-to-date option available.

Cheers,

Cab Vinton, Director
Plaistow Public Library
Plaistow, NH

From victor at tuxayo.net  Sun Oct 17 16:25:40 2021
From: victor at tuxayo.net (Victor Grousset/tuxayo)
Date: Sun, 17 Oct 2021 16:25:40 +0200
Subject: [Koha-devel] Time to translate: string freeze to prepare Koha
 20.05.17 has begun
Message-ID: <c036440b-4f85-d8e0-36ae-7ea0970a4d09@tuxayo.net>

Hi, saluton, hola, bonjour,

String freeze is into effect as of now for the 20.05.x maintenance branch.

This means it's the right time to head over to the translation platform:
https://translate.koha-community.org/projects/

Reminder: if you add or change a translation in version 20.05,
then you must also copy it to 20.11 and 21.05.
Otherwise your work will be lost for future versions.


Happy translating :)

-- 
Victor Grousset/tuxayo

From kyle.m.hall at gmail.com  Mon Oct 18 00:48:46 2021
From: kyle.m.hall at gmail.com (Kyle Hall)
Date: Sun, 17 Oct 2021 18:48:46 -0400
Subject: [Koha-devel] Built-in offline circulation interface
In-Reply-To: <CABW43URV8YNLcojfkqMv6JcvO03ik4Y6y3FRVD1Hv_iD0Ok8dg@mail.gmail.com>
References: <CAO4qe2MCn92PTug24TW8yyhU9hZ3WL8dPfQorru+WMH2sYkngg@mail.gmail.com>
 <CAO4qe2OG9dpHGL9uD==rxKbWrQhWXpUah-HgT==XqKrmWLfV=Q@mail.gmail.com>
 <CAEm3SZ1KYz4ybxX=dB13YMtuOY862=DB5vD=bHuxXo3ZDPrHNw@mail.gmail.com>
 <CAO4qe2PqaUmE0PyvcpN2a0=jq_+zoVSwzmp9QCZAfAVYV9itrQ@mail.gmail.com>
 <CABW43URV8YNLcojfkqMv6JcvO03ik4Y6y3FRVD1Hv_iD0Ok8dg@mail.gmail.com>
Message-ID: <CACpVHfzgKZWgoiR7Ft9-pd4bk=OfPGx-Dyb0yit0=Xm=HCwUZQ@mail.gmail.com>

The desktop application has been rocksolid for many years now! I’ve always
shied away from the browser based I’ll find circulations simply because if
something goes wrong, like the browser crashing and losing data or
something, there’s no way to get that data back. The offline circulation
desktop application writes everything to file as you perform actions so the
data doesn’t get lost in the event of a crash.

Kyle

On Sat, Oct 16, 2021 at 8:12 AM Cab Vinton <bibliwho at gmail.com> wrote:

> Fwiw, we'd somehow missed that there was a built-in capability/ system
> preference. Always assumed the utility was our only option.
>
> This functionality is an important part of Koha's feature set, so +1
> to always having at least one up-to-date option available.
>
> Cheers,
>
> Cab Vinton, Director
> Plaistow Public Library
> Plaistow, NH
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
-- 
---
http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211017/60ca4eb4/attachment.htm>

From wainuiwitikapark at catalyst.net.nz  Mon Oct 18 01:51:37 2021
From: wainuiwitikapark at catalyst.net.nz (Wainui Witika-Park)
Date: Mon, 18 Oct 2021 12:51:37 +1300
Subject: [Koha-devel] Time to translate: string freeze to prepare Koha
 19.11.23 has begun
Message-ID: <0098a13b-8dba-dbe2-d6d2-8e619fb9eeaf@catalyst.net.nz>

Hello,

String freeze is into effect as of now for the 19.11.x maintenance
branch in preparation for the 19.11.23 release.

This means it's the right time to head over to the translation platform:
https://translate.koha-community.org/projects/

Reminder: if you add or change a translation in version 19.11, then you
must also copy it to 20.05, 20.11 and 21.05. Otherwise your work will be
lost for future versions.

Happy translating!

Wainui Witika-Park (she/her)

From dcook at prosentient.com.au  Mon Oct 18 02:20:56 2021
From: dcook at prosentient.com.au (dcook at prosentient.com.au)
Date: Mon, 18 Oct 2021 11:20:56 +1100
Subject: [Koha-devel] Built-in offline circulation interface
In-Reply-To: <CACpVHfzgKZWgoiR7Ft9-pd4bk=OfPGx-Dyb0yit0=Xm=HCwUZQ@mail.gmail.com>
References: <CAO4qe2MCn92PTug24TW8yyhU9hZ3WL8dPfQorru+WMH2sYkngg@mail.gmail.com>
 <CAO4qe2OG9dpHGL9uD==rxKbWrQhWXpUah-HgT==XqKrmWLfV=Q@mail.gmail.com>
 <CAEm3SZ1KYz4ybxX=dB13YMtuOY862=DB5vD=bHuxXo3ZDPrHNw@mail.gmail.com>
 <CAO4qe2PqaUmE0PyvcpN2a0=jq_+zoVSwzmp9QCZAfAVYV9itrQ@mail.gmail.com>
 <CABW43URV8YNLcojfkqMv6JcvO03ik4Y6y3FRVD1Hv_iD0Ok8dg@mail.gmail.com>
 <CACpVHfzgKZWgoiR7Ft9-pd4bk=OfPGx-Dyb0yit0=Xm=HCwUZQ@mail.gmail.com>
Message-ID: <022901d7c3b6$05197e60$0f4c7b20$@prosentient.com.au>

Does that mean that you actually have a lot of people using the desktop application? Interesting!

 

David Cook

Senior Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia

 

Office: 02 9212 0899

Online: 02 8005 0595

 

From: Koha-devel <koha-devel-bounces at lists.koha-community.org> On Behalf Of Kyle Hall
Sent: Monday, 18 October 2021 9:49 AM
To: Cab Vinton <bibliwho at gmail.com>
Cc: Koha Devel <koha-devel at lists.koha-community.org>
Subject: Re: [Koha-devel] Built-in offline circulation interface

 

The desktop application has been rocksolid for many years now! I’ve always shied away from the browser based I’ll find circulations simply because if something goes wrong, like the browser crashing and losing data or something, there’s no way to get that data back. The offline circulation desktop application writes everything to file as you perform actions so the data doesn’t get lost in the event of a crash.

 

Kyle

 

On Sat, Oct 16, 2021 at 8:12 AM Cab Vinton <bibliwho at gmail.com <mailto:bibliwho at gmail.com> > wrote:

Fwiw, we'd somehow missed that there was a built-in capability/ system
preference. Always assumed the utility was our only option.

This functionality is an important part of Koha's feature set, so +1
to always having at least one up-to-date option available.

Cheers,

Cab Vinton, Director
Plaistow Public Library
Plaistow, NH
_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org <mailto:Koha-devel at lists.koha-community.org> 
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

-- 

---

http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211018/d8fbce90/attachment.htm>

From jonathan.druart at bugs.koha-community.org  Mon Oct 18 09:26:58 2021
From: jonathan.druart at bugs.koha-community.org (Jonathan Druart)
Date: Mon, 18 Oct 2021 09:26:58 +0200
Subject: [Koha-devel] Workflow improvement suggestions for security
 releases
In-Reply-To: <CACpVHfw8zpDd8B2hkO-fHKOrg1n+Q_efoq-C3BTLb+VB5=-ktg@mail.gmail.com>
References: <CAJzKNY5Y4TiCeuTEkNSVre9LkE807mJc6wPswkppf-kzdTNo6w@mail.gmail.com>
 <CACpVHfw8zpDd8B2hkO-fHKOrg1n+Q_efoq-C3BTLb+VB5=-ktg@mail.gmail.com>
Message-ID: <CAJzKNY6xo9GFUx+zqFEhby-7qsMo6Cqz6aLBHnHHWYO9kDF=kA@mail.gmail.com>

Thanks for your reply, Kyle!
(And sorry for my delayed answer, your message hit the spam folder!?)

Inline replies below.

Le jeu. 7 oct. 2021 à 13:15, Kyle Hall <kyle.m.hall at gmail.com> a écrit :
>>
>> 1. LTS
>> I think it's time to have a Long Term Support release. We noticed that
>> some people are still using very old versions, having a version that
>> is maintained several years could help them.
>> We could backport critical security bugs only. 4 (5?) years would be great.
>
>
> This has been proposed in the past. The general consensus at the time was that we as a community want to encourage libraries to stay on the latest versions of Koha and not to hang back on older versions.
> I'm not necessarily opposed,  but such a role will require quite a commitment.

For 22.05, Calalyst and Wainui are offering to maintain 19.11, and
there is a gap as there is no candidate for 20.05.
So it's kind of our first LTS :)

>> 5. Apply patches
>> We need a script to apply the patches on the different branches,
>> automatically. That's an easy bit to develop and it will help us a
>> lot.
>
>
> I'm not sure what you mean? Do you mean something that would apply a bug's patch set to say master, stable and oldstable and report on the bug if it doesn't apply to one? Or script in qa-test-tools to do that? Something else entirely?

In the first step I was suggesting a script in the release-tools repo
to auto-apply a patch set on the different stable branches.
But then, our imagination is the limit :)

From s.graham4 at herts.ac.uk  Mon Oct 18 12:47:45 2021
From: s.graham4 at herts.ac.uk (Stephen Graham)
Date: Mon, 18 Oct 2021 10:47:45 +0000
Subject: [Koha-devel] Changing the lost card value
Message-ID: <LO0P265MB262027F727CF9511FD6E5E22E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>

Sorry if this is a basic question. I've searched through the Koha::Patron and C4::Members perldoc and had a quick look through the memberentry.pl code to see how this handles it, but I can't seem to work out how it done. I want to change the value of the lost card field to zero. I can see the "lost" field in the borrowers table, so could update the value directly via SQL, but there must be a Koha method that I can use to do this? Any help/advice much appreciated!

Cheers, Stephen

--------------------------------------
Stephen Graham
Library Technology Consultant
Library and Computing Services

University of Hertfordshire
Hatfield, Hertfordshire, AL10 9AB

Tel: +44(0)1707 286111
Ext: 77751
Email: s.graham4 at herts.ac.uk<mailto:s.graham4 at herts.ac.uk>
Website: herts.ac.uk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211018/9fb2d51c/attachment.htm>

From jonathan.druart at bugs.koha-community.org  Mon Oct 18 13:36:59 2021
From: jonathan.druart at bugs.koha-community.org (Jonathan Druart)
Date: Mon, 18 Oct 2021 13:36:59 +0200
Subject: [Koha-devel] Changing the lost card value
In-Reply-To: <LO0P265MB262027F727CF9511FD6E5E22E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>
References: <LO0P265MB262027F727CF9511FD6E5E22E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>
Message-ID: <CAJzKNY7gcGVDiC8jARUU=t6druuEa92XYN-szEE27aF167p1Ug@mail.gmail.com>

Hi Stephen,

You can use
  Koha::Patrons->find(42)->lost(0)->store;
to set borrowers.lost to 0 for patron with borrowernumber=42.

Cheers,
Jonathan

Le lun. 18 oct. 2021 à 12:47, Stephen Graham <s.graham4 at herts.ac.uk> a écrit :
>
> Sorry if this is a basic question. I’ve searched through the Koha::Patron and C4::Members perldoc and had a quick look through the memberentry.pl code to see how this handles it, but I can’t seem to work out how it done. I want to change the value of the lost card field to zero. I can see the “lost” field in the borrowers table, so could update the value directly via SQL, but there must be a Koha method that I can use to do this? Any help/advice much appreciated!
>
>
>
> Cheers, Stephen
>
>
>
> --------------------------------------
>
> Stephen Graham
>
> Library Technology Consultant
>
> Library and Computing Services
>
>
>
> University of Hertfordshire
>
> Hatfield, Hertfordshire, AL10 9AB
>
>
>
> Tel: +44(0)1707 286111
>
> Ext: 77751
>
> Email: s.graham4 at herts.ac.uk
>
> Website: herts.ac.uk
>
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/

From s.graham4 at herts.ac.uk  Mon Oct 18 15:03:45 2021
From: s.graham4 at herts.ac.uk (Stephen Graham)
Date: Mon, 18 Oct 2021 13:03:45 +0000
Subject: [Koha-devel] Changing the lost card value
In-Reply-To: <CAJzKNY7gcGVDiC8jARUU=t6druuEa92XYN-szEE27aF167p1Ug@mail.gmail.com>
References: <LO0P265MB262027F727CF9511FD6E5E22E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>
 <CAJzKNY7gcGVDiC8jARUU=t6druuEa92XYN-szEE27aF167p1Ug@mail.gmail.com>
Message-ID: <LO0P265MB26200F3FE1BD14A330C82298E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>

Thanks Jonathan. I understand that the find method returns a Patron object, but don't understand where lost comes from. It's not a method in Patron is it? I guess it's a shortcut to update any individual database field value?

Stephen

-----Original Message-----
From: Jonathan Druart <jonathan.druart at bugs.koha-community.org> 
Sent: 18 October 2021 12:37
To: Stephen Graham <s.graham4 at herts.ac.uk>
Cc: koha-devel <koha-devel at lists.koha-community.org>
Subject: Re: [Koha-devel] Changing the lost card value

Hi Stephen,

You can use
  Koha::Patrons->find(42)->lost(0)->store;
to set borrowers.lost to 0 for patron with borrowernumber=42.

Cheers,
Jonathan

Le lun. 18 oct. 2021 à 12:47, Stephen Graham <s.graham4 at herts.ac.uk> a écrit :
>
> Sorry if this is a basic question. I’ve searched through the Koha::Patron and C4::Members perldoc and had a quick look through the memberentry.pl code to see how this handles it, but I can’t seem to work out how it done. I want to change the value of the lost card field to zero. I can see the “lost” field in the borrowers table, so could update the value directly via SQL, but there must be a Koha method that I can use to do this? Any help/advice much appreciated!
>
>
>
> Cheers, Stephen
>
>
>
> --------------------------------------
>
> Stephen Graham
>
> Library Technology Consultant
>
> Library and Computing Services
>
>
>
> University of Hertfordshire
>
> Hatfield, Hertfordshire, AL10 9AB
>
>
>
> Tel: +44(0)1707 286111
>
> Ext: 77751
>
> Email: s.graham4 at herts.ac.uk
>
> Website: herts.ac.uk
>
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/ git : 
> https://git.koha-community.org/ bugs : 
> https://bugs.koha-community.org/

From s.graham4 at herts.ac.uk  Mon Oct 18 15:18:12 2021
From: s.graham4 at herts.ac.uk (Stephen Graham)
Date: Mon, 18 Oct 2021 13:18:12 +0000
Subject: [Koha-devel] Changing the lost card value
In-Reply-To: <LO0P265MB26200F3FE1BD14A330C82298E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>
References: <LO0P265MB262027F727CF9511FD6E5E22E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>
 <CAJzKNY7gcGVDiC8jARUU=t6druuEa92XYN-szEE27aF167p1Ug@mail.gmail.com>
 <LO0P265MB26200F3FE1BD14A330C82298E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>
Message-ID: <LO0P265MB2620154E896E5A61C4E9A462E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>

Actually I just testing this now and cannot get it to work. I'm getting an error about not being able to write to the plack-opac-error.log file. I'm logged in as the usual koha user, and it's for a non-web script - never seen that before. I guess it's not working and it's trying to log the error to the plack log. 

I have the below, it's print User has a lost card, and then bombs out.

my $user = Koha::Patrons->find($userid);
if ($user->lost) {
        print "User has a lost card\n";
        $user->lost(0)->store();
} else {
        print "NO lost card\n";
}

Stephen

-----Original Message-----
From: Stephen Graham 
Sent: 18 October 2021 14:04
To: Jonathan Druart <jonathan.druart at bugs.koha-community.org>
Cc: koha-devel <koha-devel at lists.koha-community.org>
Subject: RE: [Koha-devel] Changing the lost card value

Thanks Jonathan. I understand that the find method returns a Patron object, but don't understand where lost comes from. It's not a method in Patron is it? I guess it's a shortcut to update any individual database field value?

Stephen

-----Original Message-----
From: Jonathan Druart <jonathan.druart at bugs.koha-community.org> 
Sent: 18 October 2021 12:37
To: Stephen Graham <s.graham4 at herts.ac.uk>
Cc: koha-devel <koha-devel at lists.koha-community.org>
Subject: Re: [Koha-devel] Changing the lost card value

Hi Stephen,

You can use
  Koha::Patrons->find(42)->lost(0)->store;
to set borrowers.lost to 0 for patron with borrowernumber=42.

Cheers,
Jonathan

Le lun. 18 oct. 2021 à 12:47, Stephen Graham <s.graham4 at herts.ac.uk> a écrit :
>
> Sorry if this is a basic question. I’ve searched through the Koha::Patron and C4::Members perldoc and had a quick look through the memberentry.pl code to see how this handles it, but I can’t seem to work out how it done. I want to change the value of the lost card field to zero. I can see the “lost” field in the borrowers table, so could update the value directly via SQL, but there must be a Koha method that I can use to do this? Any help/advice much appreciated!
>
>
>
> Cheers, Stephen
>
>
>
> --------------------------------------
>
> Stephen Graham
>
> Library Technology Consultant
>
> Library and Computing Services
>
>
>
> University of Hertfordshire
>
> Hatfield, Hertfordshire, AL10 9AB
>
>
>
> Tel: +44(0)1707 286111
>
> Ext: 77751
>
> Email: s.graham4 at herts.ac.uk
>
> Website: herts.ac.uk
>
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/ git : 
> https://git.koha-community.org/ bugs : 
> https://bugs.koha-community.org/

From jonathan.druart at bugs.koha-community.org  Mon Oct 18 15:34:56 2021
From: jonathan.druart at bugs.koha-community.org (Jonathan Druart)
Date: Mon, 18 Oct 2021 15:34:56 +0200
Subject: [Koha-devel] Changing the lost card value
In-Reply-To: <LO0P265MB2620154E896E5A61C4E9A462E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>
References: <LO0P265MB262027F727CF9511FD6E5E22E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>
 <CAJzKNY7gcGVDiC8jARUU=t6druuEa92XYN-szEE27aF167p1Ug@mail.gmail.com>
 <LO0P265MB26200F3FE1BD14A330C82298E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>
 <LO0P265MB2620154E896E5A61C4E9A462E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>
Message-ID: <CAJzKNY6f1W4UVmwZFJSnvy+c36zd-4ygwtzTgP7sA40gH2a9JQ@mail.gmail.com>

The trick is in the AUTOLOAD of Koha::Object, any attributes (column's
names) will be a getter/setter.

To login as the koha user and set the correct env vars you need to use
the `koha-shell` command.

Le lun. 18 oct. 2021 à 15:18, Stephen Graham <s.graham4 at herts.ac.uk> a écrit :
>
> Actually I just testing this now and cannot get it to work. I'm getting an error about not being able to write to the plack-opac-error.log file. I'm logged in as the usual koha user, and it's for a non-web script - never seen that before. I guess it's not working and it's trying to log the error to the plack log.
>
> I have the below, it's print User has a lost card, and then bombs out.
>
> my $user = Koha::Patrons->find($userid);
> if ($user->lost) {
>         print "User has a lost card\n";
>         $user->lost(0)->store();
> } else {
>         print "NO lost card\n";
> }
>
> Stephen
>
> -----Original Message-----
> From: Stephen Graham
> Sent: 18 October 2021 14:04
> To: Jonathan Druart <jonathan.druart at bugs.koha-community.org>
> Cc: koha-devel <koha-devel at lists.koha-community.org>
> Subject: RE: [Koha-devel] Changing the lost card value
>
> Thanks Jonathan. I understand that the find method returns a Patron object, but don't understand where lost comes from. It's not a method in Patron is it? I guess it's a shortcut to update any individual database field value?
>
> Stephen
>
> -----Original Message-----
> From: Jonathan Druart <jonathan.druart at bugs.koha-community.org>
> Sent: 18 October 2021 12:37
> To: Stephen Graham <s.graham4 at herts.ac.uk>
> Cc: koha-devel <koha-devel at lists.koha-community.org>
> Subject: Re: [Koha-devel] Changing the lost card value
>
> Hi Stephen,
>
> You can use
>   Koha::Patrons->find(42)->lost(0)->store;
> to set borrowers.lost to 0 for patron with borrowernumber=42.
>
> Cheers,
> Jonathan
>
> Le lun. 18 oct. 2021 à 12:47, Stephen Graham <s.graham4 at herts.ac.uk> a écrit :
> >
> > Sorry if this is a basic question. I’ve searched through the Koha::Patron and C4::Members perldoc and had a quick look through the memberentry.pl code to see how this handles it, but I can’t seem to work out how it done. I want to change the value of the lost card field to zero. I can see the “lost” field in the borrowers table, so could update the value directly via SQL, but there must be a Koha method that I can use to do this? Any help/advice much appreciated!
> >
> >
> >
> > Cheers, Stephen
> >
> >
> >
> > --------------------------------------
> >
> > Stephen Graham
> >
> > Library Technology Consultant
> >
> > Library and Computing Services
> >
> >
> >
> > University of Hertfordshire
> >
> > Hatfield, Hertfordshire, AL10 9AB
> >
> >
> >
> > Tel: +44(0)1707 286111
> >
> > Ext: 77751
> >
> > Email: s.graham4 at herts.ac.uk
> >
> > Website: herts.ac.uk
> >
> >
> >
> > _______________________________________________
> > Koha-devel mailing list
> > Koha-devel at lists.koha-community.org
> > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> > website : https://www.koha-community.org/ git :
> > https://git.koha-community.org/ bugs :
> > https://bugs.koha-community.org/

From bibliwho at gmail.com  Mon Oct 18 15:55:49 2021
From: bibliwho at gmail.com (Cab Vinton)
Date: Mon, 18 Oct 2021 09:55:49 -0400
Subject: [Koha-devel] Changing the lost card value
In-Reply-To: <CAJzKNY7gcGVDiC8jARUU=t6druuEa92XYN-szEE27aF167p1Ug@mail.gmail.com>
References: <LO0P265MB262027F727CF9511FD6E5E22E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>
 <CAJzKNY7gcGVDiC8jARUU=t6druuEa92XYN-szEE27aF167p1Ug@mail.gmail.com>
Message-ID: <CABW43URqiFbUHZ1LbnvX9iaN3UOUraF-OB7DuLDg1XQ1KHzj5g@mail.gmail.com>

I think another option would be the Patron Import tool:
...tools/import_borrowers.pl

Cheers,

Cab Vinton, Director
Plaistow Public Library
Plaistow, NH

On Mon, Oct 18, 2021 at 9:43 AM Jonathan Druart
<jonathan.druart at bugs.koha-community.org> wrote:
>
> Hi Stephen,
>
> You can use
>   Koha::Patrons->find(42)->lost(0)->store;
> to set borrowers.lost to 0 for patron with borrowernumber=42.
>
> Cheers,
> Jonathan
>
> Le lun. 18 oct. 2021 à 12:47, Stephen Graham <s.graham4 at herts.ac.uk> a écrit :
> >
> > Sorry if this is a basic question. I’ve searched through the Koha::Patron and C4::Members perldoc and had a quick look through the memberentry.pl code to see how this handles it, but I can’t seem to work out how it done. I want to change the value of the lost card field to zero. I can see the “lost” field in the borrowers table, so could update the value directly via SQL, but there must be a Koha method that I can use to do this? Any help/advice much appreciated!
> >
> >
> >
> > Cheers, Stephen
> >
> >
> >
> > --------------------------------------
> >
> > Stephen Graham
> >
> > Library Technology Consultant
> >
> > Library and Computing Services
> >
> >
> >
> > University of Hertfordshire
> >
> > Hatfield, Hertfordshire, AL10 9AB
> >
> >
> >
> > Tel: +44(0)1707 286111
> >
> > Ext: 77751
> >
> > Email: s.graham4 at herts.ac.uk
> >
> > Website: herts.ac.uk
> >
> >
> >
> > _______________________________________________
> > Koha-devel mailing list
> > Koha-devel at lists.koha-community.org
> > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> > website : https://www.koha-community.org/
> > git : https://git.koha-community.org/
> > bugs : https://bugs.koha-community.org/
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/

From tomascohen at gmail.com  Mon Oct 18 17:36:31 2021
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Mon, 18 Oct 2021 12:36:31 -0300
Subject: [Koha-devel] Changing the lost card value
In-Reply-To: <LO0P265MB2620154E896E5A61C4E9A462E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>
References: <LO0P265MB262027F727CF9511FD6E5E22E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>
 <CAJzKNY7gcGVDiC8jARUU=t6druuEa92XYN-szEE27aF167p1Ug@mail.gmail.com>
 <LO0P265MB26200F3FE1BD14A330C82298E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>
 <LO0P265MB2620154E896E5A61C4E9A462E7BC9@LO0P265MB2620.GBRP265.PROD.OUTLOOK.COM>
Message-ID: <CABZfb=WYB0RMZ1g9foAs3zhkZx3REY_oz_gOku6ttev3-TYgaw@mail.gmail.com>

You need to run it inside koha-shell

El lun., 18 oct. 2021 12:30, Stephen Graham <s.graham4 at herts.ac.uk>
escribió:

> Actually I just testing this now and cannot get it to work. I'm getting an
> error about not being able to write to the plack-opac-error.log file. I'm
> logged in as the usual koha user, and it's for a non-web script - never
> seen that before. I guess it's not working and it's trying to log the error
> to the plack log.
>
> I have the below, it's print User has a lost card, and then bombs out.
>
> my $user = Koha::Patrons->find($userid);
> if ($user->lost) {
>         print "User has a lost card\n";
>         $user->lost(0)->store();
> } else {
>         print "NO lost card\n";
> }
>
> Stephen
>
> -----Original Message-----
> From: Stephen Graham
> Sent: 18 October 2021 14:04
> To: Jonathan Druart <jonathan.druart at bugs.koha-community.org>
> Cc: koha-devel <koha-devel at lists.koha-community.org>
> Subject: RE: [Koha-devel] Changing the lost card value
>
> Thanks Jonathan. I understand that the find method returns a Patron
> object, but don't understand where lost comes from. It's not a method in
> Patron is it? I guess it's a shortcut to update any individual database
> field value?
>
> Stephen
>
> -----Original Message-----
> From: Jonathan Druart <jonathan.druart at bugs.koha-community.org>
> Sent: 18 October 2021 12:37
> To: Stephen Graham <s.graham4 at herts.ac.uk>
> Cc: koha-devel <koha-devel at lists.koha-community.org>
> Subject: Re: [Koha-devel] Changing the lost card value
>
> Hi Stephen,
>
> You can use
>   Koha::Patrons->find(42)->lost(0)->store;
> to set borrowers.lost to 0 for patron with borrowernumber=42.
>
> Cheers,
> Jonathan
>
> Le lun. 18 oct. 2021 à 12:47, Stephen Graham <s.graham4 at herts.ac.uk> a
> écrit :
> >
> > Sorry if this is a basic question. I’ve searched through the
> Koha::Patron and C4::Members perldoc and had a quick look through the
> memberentry.pl code to see how this handles it, but I can’t seem to work
> out how it done. I want to change the value of the lost card field to zero.
> I can see the “lost” field in the borrowers table, so could update the
> value directly via SQL, but there must be a Koha method that I can use to
> do this? Any help/advice much appreciated!
> >
> >
> >
> > Cheers, Stephen
> >
> >
> >
> > --------------------------------------
> >
> > Stephen Graham
> >
> > Library Technology Consultant
> >
> > Library and Computing Services
> >
> >
> >
> > University of Hertfordshire
> >
> > Hatfield, Hertfordshire, AL10 9AB
> >
> >
> >
> > Tel: +44(0)1707 286111
> >
> > Ext: 77751
> >
> > Email: s.graham4 at herts.ac.uk
> >
> > Website: herts.ac.uk
> >
> >
> >
> > _______________________________________________
> > Koha-devel mailing list
> > Koha-devel at lists.koha-community.org
> > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> > website : https://www.koha-community.org/ git :
> > https://git.koha-community.org/ bugs :
> > https://bugs.koha-community.org/
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211018/d4487b3d/attachment.htm>

From kyle.m.hall at gmail.com  Tue Oct 19 20:13:39 2021
From: kyle.m.hall at gmail.com (Kyle Hall)
Date: Tue, 19 Oct 2021 14:13:39 -0400
Subject: [Koha-devel] Workflow improvement suggestions for security
 releases
In-Reply-To: <CAJzKNY6xo9GFUx+zqFEhby-7qsMo6Cqz6aLBHnHHWYO9kDF=kA@mail.gmail.com>
References: <CAJzKNY5Y4TiCeuTEkNSVre9LkE807mJc6wPswkppf-kzdTNo6w@mail.gmail.com>
 <CACpVHfw8zpDd8B2hkO-fHKOrg1n+Q_efoq-C3BTLb+VB5=-ktg@mail.gmail.com>
 <CAJzKNY6xo9GFUx+zqFEhby-7qsMo6Cqz6aLBHnHHWYO9kDF=kA@mail.gmail.com>
Message-ID: <CACpVHfz0Za1JsQpfkVRUxsi0DQMokb8dvpiMBcZqyH1gb2RPmQ@mail.gmail.com>

> For 22.05, Calalyst and Wainui are offering to maintain 19.11, and
> there is a gap as there is no candidate for 20.05.
> So it's kind of our first LTS :)
>

I suppose we need to understand Catalyst's upgrade strategy a bit more. It
we as a community are going to do LTS, we need to really commit to it.
19.11 will be two years out as of the 21.11 release.
Ubuntu LTS releases are every two years. If my math is correct, that would
mean that 21.11 would be the next LTS release. Does Catalyst plan on
upgrading from 19.11 to 21.11?
I'm curious how many libraries would utilize an LTS release and upgrade
bi-annually.
Do we have any metrics on what is being pulled from the community apt
server? If not, is it possible to add tracking?

In the first step I was suggesting a script in the release-tools repo
> to auto-apply a patch set on the different stable branches.
> But then, our imagination is the limit :)
>

That sounds good to me! I can imagine a new bugzilla field for "Fails to
apply to" that would be a list of release branches ( 21.05.x, 20.11.x, etc
) so we would be aware.

Kyle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211019/82d20196/attachment.htm>

From kyle.m.hall at gmail.com  Tue Oct 19 20:14:53 2021
From: kyle.m.hall at gmail.com (Kyle Hall)
Date: Tue, 19 Oct 2021 14:14:53 -0400
Subject: [Koha-devel] Built-in offline circulation interface
In-Reply-To: <022901d7c3b6$05197e60$0f4c7b20$@prosentient.com.au>
References: <CAO4qe2MCn92PTug24TW8yyhU9hZ3WL8dPfQorru+WMH2sYkngg@mail.gmail.com>
 <CAO4qe2OG9dpHGL9uD==rxKbWrQhWXpUah-HgT==XqKrmWLfV=Q@mail.gmail.com>
 <CAEm3SZ1KYz4ybxX=dB13YMtuOY862=DB5vD=bHuxXo3ZDPrHNw@mail.gmail.com>
 <CAO4qe2PqaUmE0PyvcpN2a0=jq_+zoVSwzmp9QCZAfAVYV9itrQ@mail.gmail.com>
 <CABW43URV8YNLcojfkqMv6JcvO03ik4Y6y3FRVD1Hv_iD0Ok8dg@mail.gmail.com>
 <CACpVHfzgKZWgoiR7Ft9-pd4bk=OfPGx-Dyb0yit0=Xm=HCwUZQ@mail.gmail.com>
 <022901d7c3b6$05197e60$0f4c7b20$@prosentient.com.au>
Message-ID: <CACpVHfz64Ep+oxrKiaKpsjmCt_0ktv2q=yhkU67RWygW7OBcnQ@mail.gmail.com>

Indeed! I know many ByWater partners use the desktop application.
I'd go so far to say I'm not aware of any ByWater partners using the FF
plugin or the HTML5 version at this time.

Kyle

---
http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )


On Sun, Oct 17, 2021 at 8:21 PM <dcook at prosentient.com.au> wrote:

> Does that mean that you actually have a lot of people using the desktop
> application? Interesting!
>
>
>
> David Cook
>
> Senior Software Engineer
>
> Prosentient Systems
>
> Suite 7.03
>
> 6a Glen St
>
> Milsons Point NSW 2061
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Online: 02 8005 0595
>
>
>
> *From:* Koha-devel <koha-devel-bounces at lists.koha-community.org> *On
> Behalf Of *Kyle Hall
> *Sent:* Monday, 18 October 2021 9:49 AM
> *To:* Cab Vinton <bibliwho at gmail.com>
> *Cc:* Koha Devel <koha-devel at lists.koha-community.org>
> *Subject:* Re: [Koha-devel] Built-in offline circulation interface
>
>
>
> The desktop application has been rocksolid for many years now! I’ve always
> shied away from the browser based I’ll find circulations simply because if
> something goes wrong, like the browser crashing and losing data or
> something, there’s no way to get that data back. The offline circulation
> desktop application writes everything to file as you perform actions so the
> data doesn’t get lost in the event of a crash.
>
>
>
> Kyle
>
>
>
> On Sat, Oct 16, 2021 at 8:12 AM Cab Vinton <bibliwho at gmail.com> wrote:
>
> Fwiw, we'd somehow missed that there was a built-in capability/ system
> preference. Always assumed the utility was our only option.
>
> This functionality is an important part of Koha's feature set, so +1
> to always having at least one up-to-date option available.
>
> Cheers,
>
> Cab Vinton, Director
> Plaistow Public Library
> Plaistow, NH
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
> --
>
> ---
>
> http://www.kylehall.info
> ByWater Solutions ( http://bywatersolutions.com )
> Meadville Public Library ( http://www.meadvillelibrary.org )
> Crawford County Federated Library System ( http://www.ccfls.org )
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211019/e0d538ac/attachment.htm>

From catalog at bfli.org  Tue Oct 19 20:19:32 2021
From: catalog at bfli.org (BFL Catalog)
Date: Tue, 19 Oct 2021 14:19:32 -0400
Subject: [Koha-devel] Built-in offline circulation interface
In-Reply-To: <CACpVHfz64Ep+oxrKiaKpsjmCt_0ktv2q=yhkU67RWygW7OBcnQ@mail.gmail.com>
References: <CAO4qe2MCn92PTug24TW8yyhU9hZ3WL8dPfQorru+WMH2sYkngg@mail.gmail.com>
 <CAO4qe2OG9dpHGL9uD==rxKbWrQhWXpUah-HgT==XqKrmWLfV=Q@mail.gmail.com>
 <CAEm3SZ1KYz4ybxX=dB13YMtuOY862=DB5vD=bHuxXo3ZDPrHNw@mail.gmail.com>
 <CAO4qe2PqaUmE0PyvcpN2a0=jq_+zoVSwzmp9QCZAfAVYV9itrQ@mail.gmail.com>
 <CABW43URV8YNLcojfkqMv6JcvO03ik4Y6y3FRVD1Hv_iD0Ok8dg@mail.gmail.com>
 <CACpVHfzgKZWgoiR7Ft9-pd4bk=OfPGx-Dyb0yit0=Xm=HCwUZQ@mail.gmail.com>
 <022901d7c3b6$05197e60$0f4c7b20$@prosentient.com.au>
 <CACpVHfz64Ep+oxrKiaKpsjmCt_0ktv2q=yhkU67RWygW7OBcnQ@mail.gmail.com>
Message-ID: <CAMigdodemb7KNiCuVcfo4S6VnA6n4Gz4E1eZso-3geh444t08Q@mail.gmail.com>

Desktop application has gotten us out of a couple of tight spots so we
could still operate as a lending library while we had a complete loss of
all things internet.

Wendy Sharkey
Head of Circulation/ Cataloging and IT
Bennington Free Library
101 Silver Street
Bennington, VT 05201
(802) 442-9051


On Tue, Oct 19, 2021 at 2:15 PM Kyle Hall <kyle.m.hall at gmail.com> wrote:

> Indeed! I know many ByWater partners use the desktop application.
> I'd go so far to say I'm not aware of any ByWater partners using the FF
> plugin or the HTML5 version at this time.
>
> Kyle
>
> ---
> http://www.kylehall.info
> ByWater Solutions ( http://bywatersolutions.com )
> Meadville Public Library ( http://www.meadvillelibrary.org )
> Crawford County Federated Library System ( http://www.ccfls.org )
>
>
> On Sun, Oct 17, 2021 at 8:21 PM <dcook at prosentient.com.au> wrote:
>
>> Does that mean that you actually have a lot of people using the desktop
>> application? Interesting!
>>
>>
>>
>> David Cook
>>
>> Senior Software Engineer
>>
>> Prosentient Systems
>>
>> Suite 7.03
>>
>> 6a Glen St
>>
>> Milsons Point NSW 2061
>>
>> Australia
>>
>>
>>
>> Office: 02 9212 0899
>>
>> Online: 02 8005 0595
>>
>>
>>
>> *From:* Koha-devel <koha-devel-bounces at lists.koha-community.org> *On
>> Behalf Of *Kyle Hall
>> *Sent:* Monday, 18 October 2021 9:49 AM
>> *To:* Cab Vinton <bibliwho at gmail.com>
>> *Cc:* Koha Devel <koha-devel at lists.koha-community.org>
>> *Subject:* Re: [Koha-devel] Built-in offline circulation interface
>>
>>
>>
>> The desktop application has been rocksolid for many years now! I’ve
>> always shied away from the browser based I’ll find circulations simply
>> because if something goes wrong, like the browser crashing and losing data
>> or something, there’s no way to get that data back. The offline circulation
>> desktop application writes everything to file as you perform actions so the
>> data doesn’t get lost in the event of a crash.
>>
>>
>>
>> Kyle
>>
>>
>>
>> On Sat, Oct 16, 2021 at 8:12 AM Cab Vinton <bibliwho at gmail.com> wrote:
>>
>> Fwiw, we'd somehow missed that there was a built-in capability/ system
>> preference. Always assumed the utility was our only option.
>>
>> This functionality is an important part of Koha's feature set, so +1
>> to always having at least one up-to-date option available.
>>
>> Cheers,
>>
>> Cab Vinton, Director
>> Plaistow Public Library
>> Plaistow, NH
>> _______________________________________________
>> Koha-devel mailing list
>> Koha-devel at lists.koha-community.org
>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> website : https://www.koha-community.org/
>> git : https://git.koha-community.org/
>> bugs : https://bugs.koha-community.org/
>>
>> --
>>
>> ---
>>
>> http://www.kylehall.info
>> ByWater Solutions ( http://bywatersolutions.com )
>> Meadville Public Library ( http://www.meadvillelibrary.org )
>> Crawford County Federated Library System ( http://www.ccfls.org )
>>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211019/ab6ed35a/attachment-0001.htm>

From fridolin.somers at biblibre.com  Tue Oct 19 20:51:44 2021
From: fridolin.somers at biblibre.com (Fridolin SOMERS)
Date: Tue, 19 Oct 2021 08:51:44 -1000
Subject: [Koha-devel] Roles for 22.05 open
In-Reply-To: <CAJzKNY7+ht9vHhw1HF23hPsND+8Mvt0HWOzwthR8LEq1_Cyz5w@mail.gmail.com>
References: <CAJzKNY54cnPaGdvJaifhr4O6aHv1LKV8+BV_K6T_zD5NhxEBCQ@mail.gmail.com>
 <CAJzKNY7+ht9vHhw1HF23hPsND+8Mvt0HWOzwthR8LEq1_Cyz5w@mail.gmail.com>
Message-ID: <8a4a1bcd-cdce-b1aa-c9af-4711dcd661b7@biblibre.com>

Hi,

My proposal is now on the wiki, see you at the meeting.

Best regards

Le 13/10/2021 à 21:03, Jonathan Druart a écrit :
> The election of the 22.05 team will take place during the next general
> IRC meeting, on Wednesday October 20th 2021, 14:00 UTC.
> https://wiki.koha-community.org/wiki/General_IRC_meeting_20_October_2021
> 
> There is still plenty of room available!
> 
> 
> Le mer. 29 sept. 2021 à 17:12, Jonathan Druart
> <jonathan.druart at bugs.koha-community.org> a écrit :
>>
>> Hello everybody,
>>
>> The roles for the 22.05 release cycle are now opened.
>> The vote will take place during one of the dev meetings in October.
>>
>> https://wiki.koha-community.org/wiki/Roles_for_22.05
>>
>> The description of the roles can be found at this wiki page
>> https://wiki.koha-community.org/wiki/Project_roles
>>
>> Regards,
>> Jonathan
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
> 

-- 
Fridolin SOMERS <fridolin.somers at biblibre.com>
Software and system maintainer 🦄
BibLibre, France

From chrisc at catalyst.net.nz  Tue Oct 19 20:59:06 2021
From: chrisc at catalyst.net.nz (Chris Cormack)
Date: Wed, 20 Oct 2021 07:59:06 +1300
Subject: [Koha-devel] Workflow improvement suggestions for security
 releases
In-Reply-To: <CACpVHfz0Za1JsQpfkVRUxsi0DQMokb8dvpiMBcZqyH1gb2RPmQ@mail.gmail.com>
References: <CAJzKNY5Y4TiCeuTEkNSVre9LkE807mJc6wPswkppf-kzdTNo6w@mail.gmail.com>
 <CACpVHfw8zpDd8B2hkO-fHKOrg1n+Q_efoq-C3BTLb+VB5=-ktg@mail.gmail.com>
 <CAJzKNY6xo9GFUx+zqFEhby-7qsMo6Cqz6aLBHnHHWYO9kDF=kA@mail.gmail.com>
 <CACpVHfz0Za1JsQpfkVRUxsi0DQMokb8dvpiMBcZqyH1gb2RPmQ@mail.gmail.com>
Message-ID: <68B12077-805B-466F-82B4-8D88856C1E27@catalyst.net.nz>

We have very few (I think none) 19.11  libraries left. Almost all of our libraries are either running 21.05 or in the process of upgrading). However we have committed to maintain 19.11 for the community for at least one more cycle. 

It's very low maintenance as its pretty much just security patches from here.
If no one else takes over it next cycle we will do it again.

Having an LTS release would be useful. By far the majority of Koha libraries are not with a support provider, and if we check hea, there's a large (1000+) number of libraries running a version of 19.11.

It would also be one step closer to getting into Debian proper. (a long term dream of mine) 

Chris 



On 20 October 2021 7:13:39 am NZDT, Kyle Hall <kyle.m.hall at gmail.com> wrote:
>> For 22.05, Calalyst and Wainui are offering to maintain 19.11, and
>> there is a gap as there is no candidate for 20.05.
>> So it's kind of our first LTS :)
>>
>
>I suppose we need to understand Catalyst's upgrade strategy a bit more. It
>we as a community are going to do LTS, we need to really commit to it.
>19.11 will be two years out as of the 21.11 release.
>Ubuntu LTS releases are every two years. If my math is correct, that would
>mean that 21.11 would be the next LTS release. Does Catalyst plan on
>upgrading from 19.11 to 21.11?
>I'm curious how many libraries would utilize an LTS release and upgrade
>bi-annually.
>Do we have any metrics on what is being pulled from the community apt
>server? If not, is it possible to add tracking?
>
>In the first step I was suggesting a script in the release-tools repo
>> to auto-apply a patch set on the different stable branches.
>> But then, our imagination is the limit :)
>>
>
>That sounds good to me! I can imagine a new bugzilla field for "Fails to
>apply to" that would be a list of release branches ( 21.05.x, 20.11.x, etc
>) so we would be aware.
>
>Kyle

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211020/1b8354a7/attachment.htm>

From kyle.m.hall at gmail.com  Wed Oct 20 00:59:53 2021
From: kyle.m.hall at gmail.com (Kyle Hall)
Date: Tue, 19 Oct 2021 18:59:53 -0400
Subject: [Koha-devel] Workflow improvement suggestions for security
 releases
In-Reply-To: <68B12077-805B-466F-82B4-8D88856C1E27@catalyst.net.nz>
References: <CAJzKNY5Y4TiCeuTEkNSVre9LkE807mJc6wPswkppf-kzdTNo6w@mail.gmail.com>
 <CACpVHfw8zpDd8B2hkO-fHKOrg1n+Q_efoq-C3BTLb+VB5=-ktg@mail.gmail.com>
 <CAJzKNY6xo9GFUx+zqFEhby-7qsMo6Cqz6aLBHnHHWYO9kDF=kA@mail.gmail.com>
 <CACpVHfz0Za1JsQpfkVRUxsi0DQMokb8dvpiMBcZqyH1gb2RPmQ@mail.gmail.com>
 <68B12077-805B-466F-82B4-8D88856C1E27@catalyst.net.nz>
Message-ID: <CACpVHfy-r107_cD+9bu3PbOGp_DvPgc_2-dgSjCGnZ=qJRi=bA@mail.gmail.com>

Thanks Chris!

I suppose the next question is, does a 2 year LTS cycle sound right for
Koha?

Kyle
---
http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )


On Tue, Oct 19, 2021 at 2:59 PM Chris Cormack <chrisc at catalyst.net.nz>
wrote:

> We have very few (I think none) 19.11 libraries left. Almost all of our
> libraries are either running 21.05 or in the process of upgrading). However
> we have committed to maintain 19.11 for the community for at least one more
> cycle.
>
> It's very low maintenance as its pretty much just security patches from
> here.
> If no one else takes over it next cycle we will do it again.
>
> Having an LTS release would be useful. By far the majority of Koha
> libraries are not with a support provider, and if we check hea, there's a
> large (1000+) number of libraries running a version of 19.11.
>
> It would also be one step closer to getting into Debian proper. (a long
> term dream of mine)
>
> Chris
>
>
>
> On 20 October 2021 7:13:39 am NZDT, Kyle Hall <kyle.m.hall at gmail.com>
> wrote:
>>
>>
>> For 22.05, Calalyst and Wainui are offering to maintain 19.11, and
>>> there is a gap as there is no candidate for 20.05.
>>> So it's kind of our first LTS :)
>>>
>>
>> I suppose we need to understand Catalyst's upgrade strategy a bit more.
>> It we as a community are going to do LTS, we need to really commit to it.
>> 19.11 will be two years out as of the 21.11 release.
>> Ubuntu LTS releases are every two years. If my math is correct, that
>> would mean that 21.11 would be the next LTS release. Does Catalyst plan on
>> upgrading from 19.11 to 21.11?
>> I'm curious how many libraries would utilize an LTS release and upgrade
>> bi-annually.
>> Do we have any metrics on what is being pulled from the community apt
>> server? If not, is it possible to add tracking?
>>
>> In the first step I was suggesting a script in the release-tools repo
>>> to auto-apply a patch set on the different stable branches.
>>> But then, our imagination is the limit :)
>>>
>>
>> That sounds good to me! I can imagine a new bugzilla field for "Fails to
>> apply to" that would be a list of release branches ( 21.05.x, 20.11.x, etc
>> ) so we would be aware.
>>
>> Kyle
>>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211019/6dc5dd14/attachment.htm>

From dcook at prosentient.com.au  Fri Oct 22 04:33:10 2021
From: dcook at prosentient.com.au (dcook at prosentient.com.au)
Date: Fri, 22 Oct 2021 13:33:10 +1100
Subject: [Koha-devel] Automatic Renewal Digests not working in 21.05.03
Message-ID: <063001d7c6ed$27deca60$779c5f20$@prosentient.com.au>

Hi all,

 

Has anyone got Automatic Renewal Digests to work? I've looked at the code
and at a glance it looks fine in 21.05.03, but emails aren't going out when
Digests are selected. Emails go out fine without the Digests selected.

 

Before I dig into the guts of it, I figured I'd ask if anyone else has had
this problem. 

 

Cheers,

 

David Cook

Senior Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia

 

Office: 02 9212 0899

Online: 02 8005 0595

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211022/e30df55a/attachment.htm>

From victor at tuxayo.net  Fri Oct 22 16:44:42 2021
From: victor at tuxayo.net (Victor Grousset/tuxayo)
Date: Fri, 22 Oct 2021 16:44:42 +0200
Subject: [Koha-devel] Translation platform sync delay: 2nd call to
 translators to prepare this month's minor release
Message-ID: <073d233c-fc0e-4aa5-c306-12e70e5fa8d3@tuxayo.net>

Hi,

Due to a delay in getting the platform in sync with the to-be-released 
code, the new strings came Wednesday. So translators are advised to take 
another look to translate these:
https://translate.koha-community.org/

The minor releases of 21.05.x 20.11.x 20.05.x 19.11.x will be around the 
27th.

Happy translating :)

-- 
Victor Grousset/tuxayo

From katrin.fischer.83 at web.de  Sat Oct 23 11:22:41 2021
From: katrin.fischer.83 at web.de (Katrin Fischer)
Date: Sat, 23 Oct 2021 11:22:41 +0200
Subject: [Koha-devel] Koha Improvement idea for the Task scheduler
 feature
In-Reply-To: <AM9P191MB195378BDF6D334B5612EC80D9EA89@AM9P191MB1953.EURP191.PROD.OUTLOOK.COM>
References: <AM9P191MB19536F51E71D729C46087E519EF99@AM9P191MB1953.EURP191.PROD.OUTLOOK.COM>
 <AM9P191MB195378BDF6D334B5612EC80D9EA89@AM9P191MB1953.EURP191.PROD.OUTLOOK.COM>
Message-ID: <19c5f105-a726-0cab-c707-388e7eadb839@web.de>

Hi Ola,

sorry for the late reply. Would you mind adding the screenshots to the
existing bug for the task scheduler?

*Bug 3935*
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3935> -
Schedule tasks periodically

I think they could be useful as mock-ups/ideas for a future development.

Katrin

On 28.09.21 10:13, Ola Andersson wrote:
>
> Kia ora Everyone,
>
> I had a look at the Task scheduler in our version of Koha (20.11) and
> have a few improvements in mind:
>
> By Adding a “when to send” dimension it would become possible to use
> the Task scheduler for repetitive (cron) reports.. E.g. We use our
> local task scheduler to send picking lists to staff to have books
> picked that have reservations/holds and that are to be transferred
> from the library to another branch.
>
> These below are the main “when to send” values available to pick from
> in our local service doing similar job as Task scheduler:
>
> *case **"OnRequest"*:
> *case **"OnContentChange"*:
> *case **"OnContentChangeOnceDaily"*:
> *case **"OnContentChangeEveryHour"*:
> *case **"WDOnContentChangeEveryHour"*: (WD = Week days – Mon-Fri)
> *case **"WDOnContentChangeEveryHour0717"*:
> *case **"OnContentChangeEveryHour0720"*:
> *case **"OnContentChangeEveryMonday"*:
> *case **"FirstDayEveryMonth"*:
> *case **"FirstDayEveryQuarter"*:
> *case **"EveryMonday"*:
> *case **"EveryTuesday"*:
> *case **"EveryWednesday"*:
> *case **"EveryThursday"*:
> *case **"EveryFriday"*:
> *case **"EverySaturday"*:
> *case **"EverySunday"*:
> *case **"EveryWorkDay"*:
> *case **"EveryDay"*:
>
> The options using “OnContentChange” all uses crc32 checksums of the
> report content to validate if the report content has changed from last
> run or not.
>
> These are the database field we use for our local version of “Task
> scheduler”:
>
> It would be great if we could extend the task scheduler in line with
> this above.! I am here mainly submitting an idea and will not be able
> to develop the features..
>
> Ola Andersson
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211023/997cae5e/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 15705 bytes
Desc: not available
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211023/997cae5e/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 46688 bytes
Desc: not available
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211023/997cae5e/attachment-0003.png>

From victor at tuxayo.net  Mon Oct 25 23:46:02 2021
From: victor at tuxayo.net (Victor Grousset/tuxayo)
Date: Mon, 25 Oct 2021 23:46:02 +0200
Subject: [Koha-devel] Any support provider doing yearly major upgrades on
 XX.05 versions?
Message-ID: <1a2ce874-cc60-9076-b819-3e9b9d964a36@tuxayo.net>

Hi :)

I know about people upgrading every 6 month, so every major version.
And others upgrading yearly on XX.11 version to do the upgrade before 
summer when the version has had a lot user feedback.
And I'm wondering if there are some people doing the same but with XX.05 
? And at which moment of the year?

Cheers,

-- 
Victor Grousset/tuxayo

From victor at tuxayo.net  Wed Oct 27 23:54:16 2021
From: victor at tuxayo.net (Victor Grousset/tuxayo)
Date: Wed, 27 Oct 2021 23:54:16 +0200
Subject: [Koha-devel] Koha 20.05.17 released
Message-ID: <1c155b91-f417-14d2-9798-21e768de5c10@tuxayo.net>

Hello! :)

The Koha Community is happy to announce the release of Koha 20.05.17

The full release notes can be found at:
https://koha-community.org/koha-20-05-17-released/

Debian packages should be available shortly.

Thanks to everyone involved :)


Cheers,

-- 
Victor Grousset/tuxayo

From wainuiwitikapark at catalyst.net.nz  Fri Oct 29 00:03:50 2021
From: wainuiwitikapark at catalyst.net.nz (Wainui Witika-Park)
Date: Fri, 29 Oct 2021 11:03:50 +1300
Subject: [Koha-devel] Koha 19.11.23 released
Message-ID: <B60253E8-FABD-4AD1-9D80-E83FDC48FECD@catalyst.net.nz>

Hello everyone!

The Koha community is proud to announce the release of version 19.11.23.

The full release notes can be found at:
https://koha-community.org/koha-19-11-23-released/

Thank you to everyone involved!

Cheers,

Wainui Witika-Park (she/her)


From fridolin.somers at biblibre.com  Fri Oct 29 00:35:35 2021
From: fridolin.somers at biblibre.com (Fridolin SOMERS)
Date: Thu, 28 Oct 2021 12:35:35 -1000
Subject: [Koha-devel] Release of Koha 20.11.11
Message-ID: <28b7601f-6c59-6b0d-e35f-221e7058328e@biblibre.com>

Hi everyone 🤗

The Koha community is proud to announce the release of Koha 20.11.11 🚀

It is a maintenance release 🛠️

The full release notes are available here 📜
https://koha-community.org/koha-20-11-11-released/

The Debian packages will soon be available 🌼

Next month is end of cycle and begin of new one.
20.11.12 will be my last release because I upgrade to Release Manager, 
see https://wiki.koha-community.org/wiki/Roles_for_22.05

Best regards 🌊

-- 
Fridolin SOMERS <fridolin.somers at biblibre.com>
Software and system maintainer 🦄
BibLibre, France

From kyle.m.hall at gmail.com  Fri Oct 29 13:46:05 2021
From: kyle.m.hall at gmail.com (Kyle Hall)
Date: Fri, 29 Oct 2021 07:46:05 -0400
Subject: [Koha-devel] Koha 21.05.05 released
Message-ID: <CACpVHfw29rKhX_YtPJMShb0H-dGDcpWL2fmPKR69_PFkXyA_0A@mail.gmail.com>

The Koha community is proud to announce the release of version 21.05.05.
This is a maintenance release and contains many bug fixes.
Thank you very much to everyone involved in this release!

The release notes can be found at
https://koha-community.org/koha-21-05-05-released/

Kyle

---
http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211029/57a96147/attachment.htm>

From mtj at kohaaloha.com  Sat Oct 30 02:38:14 2021
From: mtj at kohaaloha.com (Mason James)
Date: Sat, 30 Oct 2021 13:38:14 +1300
Subject: [Koha-devel] =?utf-8?q?Koha_packages_are_available_=F0=9F=8E=81?=
Message-ID: <98493f86-2b15-a193-3ae6-490ae34a4d5c@kohaaloha.com>

kia ora community,
the latest Koha packages are available

cheers, Mason

From semarie-koha at latrappe.fr  Sat Oct 30 17:13:55 2021
From: semarie-koha at latrappe.fr (=?utf-8?Q?S=C3=A9bastien?= Marie)
Date: Sat, 30 Oct 2021 17:13:55 +0200
Subject: [Koha-devel] Koha 21.05.05 released
In-Reply-To: <CACpVHfw29rKhX_YtPJMShb0H-dGDcpWL2fmPKR69_PFkXyA_0A@mail.gmail.com>
References: <CACpVHfw29rKhX_YtPJMShb0H-dGDcpWL2fmPKR69_PFkXyA_0A@mail.gmail.com>
Message-ID: <YX1hCZxyZcyrx7zz@local>

On Fri, Oct 29, 2021 at 07:46:05AM -0400, Kyle Hall wrote:
> The Koha community is proud to announce the release of version 21.05.05.
> This is a maintenance release and contains many bug fixes.
> Thank you very much to everyone involved in this release!
> 
> The release notes can be found at
> https://koha-community.org/koha-21-05-05-released/
> 

I have a problem while updating from 21.05.04 to 21.05.05. koha keep
asking for upgrading the database.

It seems that the commit which increment the version for 21.05.05
release miss updating installer/data/mysql/updatedatabase.pl too.

https://github.com/Koha-Community/Koha/commit/ba30e76d1a08ef84e66583cd4638f6150ffdeee2

I upgraded using debian package.

Thanks.
-- 
Sebastien Marie

From kohanews at gmail.com  Sat Oct 30 19:54:54 2021
From: kohanews at gmail.com (Koha Newsletter)
Date: Sat, 30 Oct 2021 19:54:54 +0200
Subject: [Koha-devel] Koha Community Newsletter: October 2021
Message-ID: <CAEqgz_=hJSCh0JV2RT6LotHqp3tXaOim7hqSox0KxfKMT-4u9g@mail.gmail.com>

The Koha Community Newsletter for October 2021 is here:

* https://koha-community.org/koha-community-newsletter-october-2021/

Many thanks to everyone who submitted articles and news to this newsletter!

Please feel free to email me with any corrections or suggestions.
--
Michael Kuhn
Editor, Koha Community Newsletter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211030/5f6419d7/attachment.htm>

From david.nind at gmail.com  Sun Oct 31 02:02:10 2021
From: david.nind at gmail.com (David Nind)
Date: Sun, 31 Oct 2021 13:02:10 +1300
Subject: [Koha-devel] Koha 21.05.05 released
In-Reply-To: <YX1hCZxyZcyrx7zz@local>
References: <CACpVHfw29rKhX_YtPJMShb0H-dGDcpWL2fmPKR69_PFkXyA_0A@mail.gmail.com>
 <YX1hCZxyZcyrx7zz@local>
Message-ID: <CAK5OMPe=ac_kQaspssZKptojL-cg_oueWb-TXkmqLFmNtn1jdA@mail.gmail.com>

Please see bug 29378 comment #3 for a temporary work around:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378

Packages will be fixed as soon as possible.

David Nind

On Sun, 31 Oct 2021 at 04:14, Sébastien Marie <semarie-koha at latrappe.fr>
wrote:

> On Fri, Oct 29, 2021 at 07:46:05AM -0400, Kyle Hall wrote:
> > The Koha community is proud to announce the release of version 21.05.05.
> > This is a maintenance release and contains many bug fixes.
> > Thank you very much to everyone involved in this release!
> >
> > The release notes can be found at
> > https://koha-community.org/koha-21-05-05-released/
> >
>
> I have a problem while updating from 21.05.04 to 21.05.05. koha keep
> asking for upgrading the database.
>
> It seems that the commit which increment the version for 21.05.05
> release miss updating installer/data/mysql/updatedatabase.pl too.
>
>
> https://github.com/Koha-Community/Koha/commit/ba30e76d1a08ef84e66583cd4638f6150ffdeee2
>
> I upgraded using debian package.
>
> Thanks.
> --
> Sebastien Marie
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211031/15b3b455/attachment.htm>

From mtj at kohaaloha.com  Sun Oct 31 02:06:32 2021
From: mtj at kohaaloha.com (Mason James)
Date: Sun, 31 Oct 2021 14:06:32 +1300
Subject: [Koha-devel] [Koha] Web install issue with 21.05.05.000
In-Reply-To: <00e901d7cddf$f0810f70$d1832e50$@bouldermasons.org>
References: <00ce01d7cdda$3e2e5f30$ba8b1d90$@bouldermasons.org>
 <40b815dd-2679-d52a-efdb-1128c73d8f80@web.de>
 <00e901d7cddf$f0810f70$d1832e50$@bouldermasons.org>
Message-ID: <3ff3bc61-a95c-a363-433d-a7850f9fd0aa@kohaaloha.com>

hi folks

i've pushed a new package, that should fix this issue


On 31/10/21 11:46 am, Bruce Yelen wrote:
> Hi Katrin,
>
> Many thanks.  I applied the update as stated in the bug report, and all appears to be well.  I promise to do a better job next time of searching the bug database.
>
> - Bruce
>
> -----Original Message-----
> From: Koha <koha-bounces at lists.katipo.co.nz> On Behalf Of Katrin Fischer
> Sent: Saturday, October 30, 2021 4:09 PM
> To: koha at lists.katipo.co.nz
> Subject: Re: [Koha] Web install issue with 21.05.05.000
>
> Hi Bruce,
>
> please see *Bug 29378*
> <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378> for a temporary workaround. Packages will be fixed as soon as possible.
>
> Katrin
>
> On 31.10.21 00:05, Bruce Yelen wrote:
>> I just upgraded my test system from 21.05.04.003 to 21.05.05.000 using
>> the Debian package.  After the web installer updates the database, it
>> returns the message "Everything went okay.  Update done.  However when
>> clicking "Continue to log in to Koha", you're immediate taken to the
>> "Web installer > Check Perl dependencies" screen again, and the entire
>> process repeats.  If I exit the web browser, and go back in, I'm taken
>> to the "Welcome to the Koha
>> 21.05 web installer" screen again, asking for the library.koha user
>> and master password.  So, while obviously a bug, what would be the
>> proper action at this point?  Should I run the script
>> "koha-upgrade-schema" to try and set things to normal?
>>
>>
>>
>> And again, an object lesson to always try out upgrades in test prior
>> to touching your live production system!
>>
>>
>>
>> Thanks!
>>
>>
>>
>> Bruce
>>
>> _______________________________________________
>>
>> Koha mailing listhttp://koha-community.org Koha at lists.katipo.co.nz
>> Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha
> _______________________________________________
>
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
>
> _______________________________________________
>
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha