From info at bywatersolutions.com  Thu Jun  1 01:44:19 2023
From: info at bywatersolutions.com (Brendan Gallagher)
Date: Wed, 31 May 2023 16:44:19 -0700
Subject: [Koha-devel] Koha 23.05 released
In-Reply-To: <814ec646-fceb-97b6-b05e-1bcd1e0f96e3@devinim.com.tr>
References: <CABZfb=WKrU3=in8c=PgTSHQZzob=49JzTcm+dbktpeCKT9URVA@mail.gmail.com>
 <814ec646-fceb-97b6-b05e-1bcd1e0f96e3@devinim.com.tr>
Message-ID: <CANGWTFQSf6RsPxH1paMgK3VZJDwvXKKurHDoyy_dgTcVjnMYVA@mail.gmail.com>

Congratulations!

On Wed, May 31, 2023 at 1:19 PM DevinimKoha <kohadevinim at devinim.com.tr>
wrote:

> Congratulations and thanks to everyone!
> On 31.05.2023 22:49, Tomas Cohen Arazi wrote:
>
> The Koha community is proud to announce the release of Koha 23.05.00.
>
> Koha 23.05.00 is a major release, that comes with many new features.
>
> It includes 26 new features, 145 enhancements, 701 bugfixes.
>
> The full release notes are available here:
> https://koha-community.org/koha-23-05-released/
>
> Debian packages should be available soon
>
> Best regards
>
> --
> Tomás Cohen Arazi
> Theke Solutions (http://theke.io)
> ✆ +54 9351 3513384
> GPG: B2F3C15F
>
> _______________________________________________
> Koha-devel mailing listKoha-devel at lists.koha-community.orghttps://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/
>


-- 
---------------------------------------------------------------------------------------------------------------
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Office: Portland, OR - Office: Trumbull, CT
Phone # (888) 900-8944
https://bywatersolutions.com <http://bywatersolutions.com>
brendan at bywatersolutions.com <info at bywatersolutions.com>

Follow us:
<https://www.facebook.com/ByWaterSolutions/>
<https://www.instagram.com/bywatersolutions/>
<https://www.youtube.com/user/bywatersolutions>
<https://twitter.com/ByWaterSolution>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230531/038a9d8d/attachment.htm>

From M.de.Rooy at rijksmuseum.nl  Thu Jun  1 08:09:59 2023
From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy)
Date: Thu, 1 Jun 2023 06:09:59 +0000
Subject: [Koha-devel] Koha 23.05 released
In-Reply-To: <CABZfb=WKrU3=in8c=PgTSHQZzob=49JzTcm+dbktpeCKT9URVA@mail.gmail.com>
References: <CABZfb=WKrU3=in8c=PgTSHQZzob=49JzTcm+dbktpeCKT9URVA@mail.gmail.com>
Message-ID: <AM0PR05MB50445BD0AAF2786086FDA7C5CE499@AM0PR05MB5044.eurprd05.prod.outlook.com>

Really great, Tomas. Thanks!

________________________________
Van: Koha-devel <koha-devel-bounces at lists.koha-community.org> namens Tomas Cohen Arazi <tomascohen at gmail.com>
Verzonden: woensdag 31 mei 2023 21:49
Aan: koha-devel <koha-devel at lists.koha-community.org>
Onderwerp: [Koha-devel] Koha 23.05 released

The Koha community is proud to announce the release of Koha 23.05.00.

Koha 23.05.00 is a major release, that comes with many new features.

It includes 26 new features, 145 enhancements, 701 bugfixes.

The full release notes are available here:
https://koha-community.org/koha-23-05-released/

Debian packages should be available soon

Best regards

--
Tomás Cohen Arazi
Theke Solutions (http://theke.io<http://theke.io/>)
✆ +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230601/5099bdc3/attachment-0001.htm>

From jonathan.field at ptfs-europe.com  Thu Jun  1 09:54:09 2023
From: jonathan.field at ptfs-europe.com (Field, Jonathan)
Date: Thu, 1 Jun 2023 08:54:09 +0100
Subject: [Koha-devel] Koha 23.05 released
In-Reply-To: <CABZfb=WKrU3=in8c=PgTSHQZzob=49JzTcm+dbktpeCKT9URVA@mail.gmail.com>
References: <CABZfb=WKrU3=in8c=PgTSHQZzob=49JzTcm+dbktpeCKT9URVA@mail.gmail.com>
Message-ID: <CAGatkyEE=horsj1uSe9H=DpeLV4jvzNcxD6jJmvXbn9ZvUEcqw@mail.gmail.com>

Great work Tomas (and ALL the team who have been involved in this!).
Appreciate it is a huge amount of work for you so we thank you.
Lots to be excited about in this release!
Jonathan

On Wed, 31 May 2023 at 20:50, Tomas Cohen Arazi <tomascohen at gmail.com>
wrote:

> The Koha community is proud to announce the release of Koha 23.05.00.
>
> Koha 23.05.00 is a major release, that comes with many new features.
>
> It includes 26 new features, 145 enhancements, 701 bugfixes.
>
> The full release notes are available here:
> https://koha-community.org/koha-23-05-released/
>
> Debian packages should be available soon
>
> Best regards
>
> --
> Tomás Cohen Arazi
> Theke Solutions (http://theke.io)
> ✆ +54 9351 3513384
> GPG: B2F3C15F
> _______________________________________________
> 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/
>


-- 

Jonathan Field

Managing Director

PTFS Europe

[image: Phone icon] M: +44 7919 372002 | T: +44 1483 378728 ext. 1000

[image: Email icon] jonathan.field at ptfs-europe.com

[image: Link icon] www.ptfs-europe.com

[image: Click to open Twitter] <https://twitter.com/PTFSEurope> [image:
Click to open YouTube] <https://www.youtube.com/@PTFSEurope>

[image: Click to open PTFS Europe webpage] <https://www.ptfs-europe.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230601/3e9420b3/attachment.htm>

From tomascohen at gmail.com  Thu Jun  1 13:35:02 2023
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Thu, 1 Jun 2023 08:35:02 -0300
Subject: [Koha-devel] A case against our release dates
Message-ID: <CABZfb=Up=icXSbLYubWqJ_L3kRFXMc7EDbdTpY+OAfomJ6DAmA@mail.gmail.com>

Hi all. Having served as Release Manager for the project a couple times,
I'd like to ask y'all to think about the dates we've chosen and have stuck
to the last few years for our releases.

I know they are somehow aligned with our regular yearly meetings, and one
each semester. But my experience says:

- We all want to implement things we discuss in the Hackfest, but the
release is too close. So we either push too late in the cycle, or need to
cool down our brains/ideas for 'after the release in two months'.
- The other scenario, which I suffered a lot recently (and will soon) is
summer holidays in the northern hemisphere: you're all out when we should
be pushing the riskier things to have enough time to fix things, and we end
up rushing things... on the last third of the cycle.

I don't have a proposal right now, but wanted to say my perception is the
dates are not ideal as-is. And hear back from you all.

Cheers!

-- 
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230601/0db4d3ea/attachment.htm>

From philippe.blouin at inlibro.com  Thu Jun  1 17:46:19 2023
From: philippe.blouin at inlibro.com (Philippe Blouin)
Date: Thu, 1 Jun 2023 11:46:19 -0400
Subject: [Koha-devel] A case against our release dates
In-Reply-To: <CABZfb=Up=icXSbLYubWqJ_L3kRFXMc7EDbdTpY+OAfomJ6DAmA@mail.gmail.com>
References: <CABZfb=Up=icXSbLYubWqJ_L3kRFXMc7EDbdTpY+OAfomJ6DAmA@mail.gmail.com>
Message-ID: <15248aa7-ae2a-4df4-9c2e-1a1ed8ca04ba@inlibro.com>

Of course I'm coming with my northern hemisphere perspective, and have 
no horse in the race really as being far from RM, but I always thought 
those dates were the best available.

Seems earlier (04, april) makes it closer to the hackfest you referred.  
Later makes it closer to summer holidays.

Were you considering breaking the equal split in time, having a small 
and a big release each year?  November for the big, and march for the 
small, the hackfest starting the next cycle ? Thinking outside the box...


Philippe Blouin,
Directeur de la technologie

Tél.  : (833) 465-4276, poste 230
philippe.blouin at inLibro.com

inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>
On 2023-06-01 07:35, Tomas Cohen Arazi wrote:
> Hi all. Having served as Release Manager for the project a couple 
> times, I'd like to ask y'all to think about the dates we've chosen and 
> have stuck to the last few years for our releases.
>
> I know they are somehow aligned with our regular yearly meetings, and 
> one each semester. But my experience says:
>
> - We all want to implement things we discuss in the Hackfest, but the 
> release is too close. So we either push too late in the cycle, or need 
> to cool down our brains/ideas for 'after the release in two months'.
> - The other scenario, which I suffered a lot recently (and will soon) 
> is summer holidays in the northern hemisphere: you're all out when we 
> should be pushing the riskier things to have enough time to fix 
> things, and we end up rushing things... on the last third of the cycle.
>
> I don't have a proposal right now, but wanted to say my perception is 
> the dates are not ideal as-is. And hear back from you all.
>
> Cheers!
>
> -- 
> Tomás Cohen Arazi
> Theke Solutions (http://theke.io)
> ✆ +54 9351 3513384
> GPG: B2F3C15F
>
> _______________________________________________
> 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/20230601/2d6b2c07/attachment.htm>

From tomascohen at gmail.com  Thu Jun  1 17:51:43 2023
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Thu, 1 Jun 2023 12:51:43 -0300
Subject: [Koha-devel] A case against our release dates
In-Reply-To: <15248aa7-ae2a-4df4-9c2e-1a1ed8ca04ba@inlibro.com>
References: <CABZfb=Up=icXSbLYubWqJ_L3kRFXMc7EDbdTpY+OAfomJ6DAmA@mail.gmail.com>
 <15248aa7-ae2a-4df4-9c2e-1a1ed8ca04ba@inlibro.com>
Message-ID: <CABZfb=Wng=u=n0qbY7i=2Cvi4gzG1oi3mSQXic_u+AsYP3C6NQ@mail.gmail.com>

My personal feeling is we should have a release right before the hackfest.
So the hackfest sets the path for the next cycle. That could mean moving
the hackfest a couple a bit later too

Add for the second part of the year, I'm not sure yet. I just have the
perception everyone is out in the months we are expected to do the bigger
changes, and we end up doing them close to the release date.

El jue, 1 jun 2023 12:46, Philippe Blouin <philippe.blouin at inlibro.com>
escribió:

> Of course I'm coming with my northern hemisphere perspective, and have no
> horse in the race really as being far from RM, but I always thought those
> dates were the best available.
>
> Seems earlier (04, april) makes it closer to the hackfest you referred.
> Later makes it closer to summer holidays.
>
> Were you considering breaking the equal split in time, having a small and
> a big release each year?  November for the big, and march for the small,
> the hackfest starting the next cycle ?  Thinking outside the box...
>
>
> Philippe Blouin,
> Directeur de la technologie
>
> Tél.  : (833) 465-4276, poste 230
> philippe.blouin at inLibro.com
> inLibro | pour esprit libre | www.inLibro.com
> On 2023-06-01 07:35, Tomas Cohen Arazi wrote:
>
> Hi all. Having served as Release Manager for the project a couple times,
> I'd like to ask y'all to think about the dates we've chosen and have stuck
> to the last few years for our releases.
>
> I know they are somehow aligned with our regular yearly meetings, and one
> each semester. But my experience says:
>
> - We all want to implement things we discuss in the Hackfest, but the
> release is too close. So we either push too late in the cycle, or need to
> cool down our brains/ideas for 'after the release in two months'.
> - The other scenario, which I suffered a lot recently (and will soon) is
> summer holidays in the northern hemisphere: you're all out when we should
> be pushing the riskier things to have enough time to fix things, and we end
> up rushing things... on the last third of the cycle.
>
> I don't have a proposal right now, but wanted to say my perception is the
> dates are not ideal as-is. And hear back from you all.
>
> Cheers!
>
> --
> Tomás Cohen Arazi
> Theke Solutions (http://theke.io)
> ✆ +54 9351 3513384
> GPG: B2F3C15F
>
> _______________________________________________
> Koha-devel mailing listKoha-devel at lists.koha-community.orghttps://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/20230601/565a9cdb/attachment-0001.htm>

From dcook at prosentient.com.au  Fri Jun  2 02:14:48 2023
From: dcook at prosentient.com.au (David Cook)
Date: Fri, 2 Jun 2023 10:14:48 +1000
Subject: [Koha-devel] A case against our release dates
In-Reply-To: <CABZfb=Wng=u=n0qbY7i=2Cvi4gzG1oi3mSQXic_u+AsYP3C6NQ@mail.gmail.com>
References: <CABZfb=Up=icXSbLYubWqJ_L3kRFXMc7EDbdTpY+OAfomJ6DAmA@mail.gmail.com>
 <15248aa7-ae2a-4df4-9c2e-1a1ed8ca04ba@inlibro.com>
 <CABZfb=Wng=u=n0qbY7i=2Cvi4gzG1oi3mSQXic_u+AsYP3C6NQ@mail.gmail.com>
Message-ID: <050f01d994e7$4698b730$d3ca2590$@prosentient.com.au>

I think that it never hurts to review an established tradition!

 

In the southern hemisphere, I often catch up on a lot of work in December as many clients go on holiday early, and then I have my summer holidays in January. In April, I’ll take the latest point release of the November version (e.g. XX.11.03), and base local work off that, since it’s new but not *too new* (ie buggy). 

 

If the community did releases in February/March and August/September… I’d probably use the August/September release as my local code base for February-April since February/March would be “too new”/bleeding edge for me. 

 

Of course, August/September is right after northern hemisphere summer holidays… which might mean it’s a smaller release or it’s less stable as it has fewer eyes on it… 

 

And if the release was in February/March, would Hackfest be about setting the path for the next cycle, or would it be fixing all the bugs in the release that just came out a few weeks earlier?

 

Would December Christmas holidays negatively impact a February/March release?

 

Maybe it’s just human nature to leave big changes too close to the release date? We always think there will be lots of time, and then we rush to do things at the last minute? 

 

In any case, I think it’s worthwhile reviewing what we’re doing.

 

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 Tomas Cohen Arazi
Sent: Friday, 2 June 2023 1:52 AM
To: Philippe Blouin <philippe.blouin at inlibro.com>
Cc: koha-devel <koha-devel at lists.koha-community.org>
Subject: Re: [Koha-devel] A case against our release dates

 

My personal feeling is we should have a release right before the hackfest. So the hackfest sets the path for the next cycle. That could mean moving the hackfest a couple a bit later too

 

Add for the second part of the year, I'm not sure yet. I just have the perception everyone is out in the months we are expected to do the bigger changes, and we end up doing them close to the release date.

 

El jue, 1 jun 2023 12:46, Philippe Blouin <philippe.blouin at inlibro.com <mailto:philippe.blouin at inlibro.com> > escribió:

Of course I'm coming with my northern hemisphere perspective, and have no horse in the race really as being far from RM, but I always thought those dates were the best available.

Seems earlier (04, april) makes it closer to the hackfest you referred.  Later makes it closer to summer holidays.

Were you considering breaking the equal split in time, having a small and a big release each year?  November for the big, and march for the small, the hackfest starting the next cycle ?  Thinking outside the box...

 

Philippe Blouin,
Directeur de la technologie

Tél.  : (833) 465-4276, poste 230
philippe.blouin at inLibro.com <mailto:philippe.blouin at inLibro.com>  

inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>  

On 2023-06-01 07:35, Tomas Cohen Arazi wrote:

Hi all. Having served as Release Manager for the project a couple times, I'd like to ask y'all to think about the dates we've chosen and have stuck to the last few years for our releases. 

 

I know they are somehow aligned with our regular yearly meetings, and one each semester. But my experience says:

 

- We all want to implement things we discuss in the Hackfest, but the release is too close. So we either push too late in the cycle, or need to cool down our brains/ideas for 'after the release in two months'.

- The other scenario, which I suffered a lot recently (and will soon) is summer holidays in the northern hemisphere: you're all out when we should be pushing the riskier things to have enough time to fix things, and we end up rushing things... on the last third of the cycle.


 

I don't have a proposal right now, but wanted to say my perception is the dates are not ideal as-is. And hear back from you all.

 

Cheers!

 

-- 

Tomás Cohen Arazi

Theke Solutions (http://theke.io <http://theke.io/> )
✆ +54 9351 3513384
GPG: B2F3C15F

 

_______________________________________________
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/

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

From dcook at prosentient.com.au  Fri Jun  2 05:18:37 2023
From: dcook at prosentient.com.au (David Cook)
Date: Fri, 2 Jun 2023 13:18:37 +1000
Subject: [Koha-devel] Configuration inheritance/override
Message-ID: <053201d99500$eca07e60$c5e17b20$@prosentient.com.au>

Hi all,

 

I think that we've all noticed that it's easy to add a new configuration
item to koha-conf.xml for new instances, but that it's much harder to update
koha-conf.xml when upgrading existing instances.

 

A strategy that I (and others) have used on other projects is to have a
core/base configuration file with defaults, and then the local config file
is used to override those defaults on a per-instance basis. 

 

The core/base config file can be replaced as part of a Debian package
upgrade, and it can be used to push out updated configuration to all
instances with 1 click.

 

This methodology also means that the local config file can often be fairly
small too as it's only overriding specific configuration items. 

 

Anyway, it's easier said than done for Koha, but it's a thought, especially
as we move forward. I know this is a problem that we bump into often in Koha
and it would help to solve it.

 

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/20230602/f869d8c9/attachment.htm>

From M.de.Rooy at rijksmuseum.nl  Fri Jun  2 08:54:08 2023
From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy)
Date: Fri, 2 Jun 2023 06:54:08 +0000
Subject: [Koha-devel] A case against our release dates
In-Reply-To: <CABZfb=Wng=u=n0qbY7i=2Cvi4gzG1oi3mSQXic_u+AsYP3C6NQ@mail.gmail.com>
References: <CABZfb=Up=icXSbLYubWqJ_L3kRFXMc7EDbdTpY+OAfomJ6DAmA@mail.gmail.com>
 <15248aa7-ae2a-4df4-9c2e-1a1ed8ca04ba@inlibro.com>
 <CABZfb=Wng=u=n0qbY7i=2Cvi4gzG1oi3mSQXic_u+AsYP3C6NQ@mail.gmail.com>
Message-ID: <AM6PR05MB5045E606AB4991EC9DBC16D1CE4EA@AM6PR05MB5045.eurprd05.prod.outlook.com>

I opt for keeping the release dates as-is. There will be no date that suits everyone.

A hackfest in March allows you to sign off on all stuff that gets in the queues after say December, and could reach .05.

New devs from the hackfest should not be pushed hastily in the .05 but have all chance to be pushed in July/August, and tested before the .11.

Just my idea.

Marcel

________________________________
Van: Koha-devel <koha-devel-bounces at lists.koha-community.org> namens Tomas Cohen Arazi <tomascohen at gmail.com>
Verzonden: donderdag 1 juni 2023 17:51
Aan: Philippe Blouin <philippe.blouin at inlibro.com>
CC: koha-devel <koha-devel at lists.koha-community.org>
Onderwerp: Re: [Koha-devel] A case against our release dates

My personal feeling is we should have a release right before the hackfest. So the hackfest sets the path for the next cycle. That could mean moving the hackfest a couple a bit later too

Add for the second part of the year, I'm not sure yet. I just have the perception everyone is out in the months we are expected to do the bigger changes, and we end up doing them close to the release date.

El jue, 1 jun 2023 12:46, Philippe Blouin <philippe.blouin at inlibro.com<mailto:philippe.blouin at inlibro.com>> escribió:

Of course I'm coming with my northern hemisphere perspective, and have no horse in the race really as being far from RM, but I always thought those dates were the best available.

Seems earlier (04, april) makes it closer to the hackfest you referred.  Later makes it closer to summer holidays.

Were you considering breaking the equal split in time, having a small and a big release each year?  November for the big, and march for the small, the hackfest starting the next cycle ?  Thinking outside the box...


Philippe Blouin,
Directeur de la technologie

Tél.  : (833) 465-4276, poste 230
philippe.blouin at inLibro.com<mailto:philippe.blouin at inLibro.com>

inLibro | pour esprit libre | www.inLibro.com<http://www.inlibro.com/>
On 2023-06-01 07:35, Tomas Cohen Arazi wrote:
Hi all. Having served as Release Manager for the project a couple times, I'd like to ask y'all to think about the dates we've chosen and have stuck to the last few years for our releases.

I know they are somehow aligned with our regular yearly meetings, and one each semester. But my experience says:

- We all want to implement things we discuss in the Hackfest, but the release is too close. So we either push too late in the cycle, or need to cool down our brains/ideas for 'after the release in two months'.
- The other scenario, which I suffered a lot recently (and will soon) is summer holidays in the northern hemisphere: you're all out when we should be pushing the riskier things to have enough time to fix things, and we end up rushing things... on the last third of the cycle.

I don't have a proposal right now, but wanted to say my perception is the dates are not ideal as-is. And hear back from you all.

Cheers!

--
Tomás Cohen Arazi
Theke Solutions (http://theke.io<http://theke.io/>)
✆ +54 9351 3513384
GPG: B2F3C15F



_______________________________________________
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/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230602/8aab1efd/attachment-0001.htm>

From mtj at kohaaloha.com  Fri Jun  2 13:39:21 2023
From: mtj at kohaaloha.com (Mason James)
Date: Fri, 2 Jun 2023 23:39:21 +1200
Subject: [Koha-devel] =?utf-8?q?Koha_23=2E05_packages_are_available_?=
 =?utf-8?b?8J+OgQ==?=
Message-ID: <3f4883c3-379e-6498-4a0c-5734a0eb4078@kohaaloha.com>

kia ora community,

the latest Koha 23.05 packages are available

an installation guide is below...
   https://wiki.koha-community.org/wiki/Koha_on_Debian


cheers, Mason

From philippe.blouin at inlibro.com  Wed Jun  7 23:10:15 2023
From: philippe.blouin at inlibro.com (Philippe Blouin)
Date: Wed, 7 Jun 2023 17:10:15 -0400
Subject: [Koha-devel] Rewrite of URLs, flushing all empty arguments
Message-ID: <075afd84-c73b-edd7-8f55-f8a6eb2262f3@inlibro.com>

Hello all!

New issue (in 22.05 here, but might be anywhere):

https://somedomain.net/cgi-bin/koha/tools/letter.pl?op=delete_confirm 
<https://v22-test-intranet.hapax.inlibro.net/cgi-bin/koha/tools/letter.pl?op=delete_confirm>_&*branchcode=*&module=suggestions&code=ACCEPTED_

When somedomain is onto one of our debian box (bullseye, 11), the 
branchcode= disappears on landing.  Be it on the connection page or 
letter.pl, we do not have the branchcode= anymore, and the code throws 
an error (branchcode being undefined)

When running onto our laptops (Ubuntu) that doesn't happen.

We have no custom RewriteRule, so I'm trying to figure out WHERE this 
rewrite comes from.

All suggestions welcomed,

Best regards,

-- 
Philippe Blouin,
Directeur de la technologie

Tél.  : (833) 465-4276, poste 230
philippe.blouin at inLibro.com

inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230607/787402f4/attachment.htm>

From michael.hafen at washk12.org  Wed Jun  7 23:17:27 2023
From: michael.hafen at washk12.org (Michael Hafen)
Date: Wed, 7 Jun 2023 15:17:27 -0600
Subject: [Koha-devel] Rewrite of URLs, flushing all empty arguments
In-Reply-To: <075afd84-c73b-edd7-8f55-f8a6eb2262f3@inlibro.com>
References: <075afd84-c73b-edd7-8f55-f8a6eb2262f3@inlibro.com>
Message-ID: <CAAh7UdnFjYZ45AfTgRfCk9rqiM-mrHFR0rC5Fjnre=5iPPKwJA@mail.gmail.com>

There are many layers interacting here.  First is apache recieving the
request, where it passes through any apache modules that are loaded, then
it's passed to cgi or fcgi (you haven't mentioned whether you have plack
enabled, but you probably do), then it's passed to Koha's codebase.  There
could be version differences between Debian and Ubuntu in either Apache
modules or Perl CGI/FCGI modules that would cause an empty get variable to
be dropped.  The perl module versions would be the first thing I'd check.

On Wed, Jun 7, 2023 at 3:10 PM Philippe Blouin <philippe.blouin at inlibro.com>
wrote:

> Hello all!
>
> New issue (in 22.05 here, but might be anywhere):
>
> https://somedomain.net/cgi-bin/koha/tools/letter.pl?op=delete_confirm
> <https://v22-test-intranet.hapax.inlibro.net/cgi-bin/koha/tools/letter.pl?op=delete_confirm>
> *&branchcode=&module=suggestions&code=ACCEPTED*
>
> When somedomain is onto one of our debian box (bullseye, 11), the
> branchcode= disappears on landing.  Be it on the connection page or
> letter.pl, we do not have the branchcode= anymore, and the code throws an
> error (branchcode being undefined)
>
> When running onto our laptops (Ubuntu) that doesn't happen.
>
> We have no custom RewriteRule, so I'm trying to figure out WHERE this
> rewrite comes from.
>
> All suggestions welcomed,
>
> Best regards,
> --
> Philippe Blouin,
> Directeur de la technologie
>
> Tél.  : (833) 465-4276, poste 230
> philippe.blouin at inLibro.com
> inLibro | pour esprit libre | www.inLibro.com
> _______________________________________________
> 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/
>


-- 
Michael Hafen
Washington County School District Technology Department
Systems Analyst
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230607/62299c5a/attachment.htm>

From dcook at prosentient.com.au  Thu Jun  8 01:38:44 2023
From: dcook at prosentient.com.au (David Cook)
Date: Thu, 8 Jun 2023 09:38:44 +1000
Subject: [Koha-devel] Rewrite of URLs, flushing all empty arguments
In-Reply-To: <CAAh7UdnFjYZ45AfTgRfCk9rqiM-mrHFR0rC5Fjnre=5iPPKwJA@mail.gmail.com>
References: <075afd84-c73b-edd7-8f55-f8a6eb2262f3@inlibro.com>
 <CAAh7UdnFjYZ45AfTgRfCk9rqiM-mrHFR0rC5Fjnre=5iPPKwJA@mail.gmail.com>
Message-ID: <096c01d99999$3d5b4d20$b811e760$@prosentient.com.au>

First things first, Philippe, you haven’t given enough information about the problem. 

 

For instance:

http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm <http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&branchcode=&module=suggestions&code=ACCEPTED> &branchcode=&module=suggestions&code=ACCEPTED

http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm <http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&module=suggestions&code=ACCEPTED> &module=suggestions&code=ACCEPTED

 

On koha-testing-docker, which admittedly is a later version, neither of these raise an error, although the second link won’t work as expected. So you should look at the actual error message in your log, and try to work it out from there. It might be that it’s a known issue that’s been fixed upstream already. 

 

Not sure what you mean by “the connection page”. Is that the login screen for letter.pl or something else? 

 

When you say “the branchcode= disappears on landing”, it’s not clear what you mean. Take a look at the Network tab on your browser and see if there are any redirects. You can also increase the logging on your Apache to see what exactly it’s doing: https://httpd.apache.org/docs/2.4/mod/core.html#loglevel. 

 

Maybe that problem instance has some Javascript running that is interfering with the location URL. You can add breakpoints in your browser so that it pauses at certain points in the process of loading. 

 

My suggestion would be doing some hands-on troubleshooting. Work the problem. The truth is out there.

 

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 Michael Hafen
Sent: Thursday, 8 June 2023 7:17 AM
To: Philippe Blouin <philippe.blouin at inlibro.com>
Cc: koha-devel at lists.koha-community.org
Subject: Re: [Koha-devel] Rewrite of URLs, flushing all empty arguments

 

There are many layers interacting here.  First is apache recieving the request, where it passes through any apache modules that are loaded, then it's passed to cgi or fcgi (you haven't mentioned whether you have plack enabled, but you probably do), then it's passed to Koha's codebase.  There could be version differences between Debian and Ubuntu in either Apache modules or Perl CGI/FCGI modules that would cause an empty get variable to be dropped.  The perl module versions would be the first thing I'd check.

 

On Wed, Jun 7, 2023 at 3:10 PM Philippe Blouin <philippe.blouin at inlibro.com <mailto:philippe.blouin at inlibro.com> > wrote:

Hello all!

New issue (in 22.05 here, but might be anywhere):

 <https://v22-test-intranet.hapax.inlibro.net/cgi-bin/koha/tools/letter.pl?op=delete_confirm> https://somedomain.net/cgi-bin/koha/tools/letter.pl?op=delete_confirm&branchcode=&module=suggestions&code=ACCEPTED

When somedomain is onto one of our debian box (bullseye, 11), the branchcode= disappears on landing.  Be it on the connection page or letter.pl <http://letter.pl> , we do not have the branchcode= anymore, and the code throws an error (branchcode being undefined)

When running onto our laptops (Ubuntu) that doesn't happen.

We have no custom RewriteRule, so I'm trying to figure out WHERE this rewrite comes from.  

All suggestions welcomed,

Best regards,

-- 

Philippe Blouin,
Directeur de la technologie

Tél.  : (833) 465-4276, poste 230
philippe.blouin at inLibro.com <mailto:philippe.blouin at inLibro.com>  

inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>  

_______________________________________________
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/



-- 

Michael Hafen

Washington County School District Technology Department

Systems Analyst

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

From mtj at kohaaloha.com  Thu Jun  8 03:05:13 2023
From: mtj at kohaaloha.com (Mason James)
Date: Thu, 8 Jun 2023 13:05:13 +1200
Subject: [Koha-devel] Rewrite of URLs, flushing all empty arguments
In-Reply-To: <075afd84-c73b-edd7-8f55-f8a6eb2262f3@inlibro.com>
References: <075afd84-c73b-edd7-8f55-f8a6eb2262f3@inlibro.com>
Message-ID: <c389ca56-3164-8320-14e8-4377ae79b1b3@kohaaloha.com>

On 8/06/23 9:10 am, Philippe Blouin wrote:
> Hello all!
> 
> New issue (in 22.05 here, but might be anywhere):
> 
> https://somedomain.net/cgi-bin/koha/tools/letter.pl?op=delete_confirm <https://v22-test-intranet.hapax.inlibro.net/cgi-bin/koha/tools/letter.pl?op=delete_confirm>_&*branchcode=*&module=suggestions&code=ACCEPTED_
> 
> When somedomain is onto one of our debian box (bullseye, 11), the branchcode= disappears on landing.  Be it on the connection page or letter.pl, we do not have the branchcode= anymore, and the code throws an error (branchcode being undefined)
> 
> When running onto our laptops (Ubuntu) that doesn't happen.

hi Philippe

which specific koha version, and ubuntu version?

From philippe.blouin at inlibro.com  Thu Jun  8 18:03:26 2023
From: philippe.blouin at inlibro.com (Philippe Blouin)
Date: Thu, 8 Jun 2023 12:03:26 -0400
Subject: [Koha-devel] Rewrite of URLs, flushing all empty arguments
In-Reply-To: <096c01d99999$3d5b4d20$b811e760$@prosentient.com.au>
References: <075afd84-c73b-edd7-8f55-f8a6eb2262f3@inlibro.com>
 <CAAh7UdnFjYZ45AfTgRfCk9rqiM-mrHFR0rC5Fjnre=5iPPKwJA@mail.gmail.com>
 <096c01d99999$3d5b4d20$b811e760$@prosentient.com.au>
Message-ID: <1f6744d4-bb83-931f-c73e-198cfe9856f1@inlibro.com>

Hi David,

Yes, connection being the login page.  Any call to it with &variable=& 
will get see its empty variable get flushed, as you summarized with

http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&branchcode=&module=suggestions&code=ACCEPTED 
<http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&branchcode=&module=suggestions&code=ACCEPTED>

http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&module=suggestions&code=ACCEPTED 
<http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&module=suggestions&code=ACCEPTED> 


The fact that it's not just branchcode, but any toto= or whatever= that 
gets flushed, seem to point to an apache setting.

BUT my question was really: is Koha doing it ?  seems not, by your 
answers.  Is Apache doing it by default (new version...), my googling 
doesn't point to that, obviously.

No redirect/rewrite in network.

But again, you're telling me it's not Koha, so I'll dig.

PS yes, the second link doesn't work.  We created a fix, but I didn't 
like it because I wanted to explore the root cause.

Philippe Blouin,
Directeur de la technologie

Tél.  : (833) 465-4276, poste 230
philippe.blouin at inLibro.com

inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>
On 2023-06-07 19:38, David Cook wrote:
>
> First things first, Philippe, you haven’t given enough information 
> about the problem.
>
> For instance:
>
> http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&branchcode=&module=suggestions&code=ACCEPTED 
> <http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&branchcode=&module=suggestions&code=ACCEPTED>
>
> http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&module=suggestions&code=ACCEPTED 
> <http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&module=suggestions&code=ACCEPTED>
>
> On koha-testing-docker, which admittedly is a later version, neither 
> of these raise an error, although the second link won’t work as 
> expected. So you should look at the actual error message in your log, 
> and try to work it out from there. It might be that it’s a known issue 
> that’s been fixed upstream already.
>
> Not sure what you mean by “the connection page”. Is that the login 
> screen for letter.pl or something else?
>
> When you say “the branchcode= disappears on landing”, it’s not clear 
> what you mean. Take a look at the Network tab on your browser and see 
> if there are any redirects. You can also increase the logging on your 
> Apache to see what exactly it’s doing: 
> https://httpd.apache.org/docs/2.4/mod/core.html#loglevel.
>
> Maybe that problem instance has some Javascript running that is 
> interfering with the location URL. You can add breakpoints in your 
> browser so that it pauses at certain points in the process of loading.
>
> My suggestion would be doing some hands-on troubleshooting. Work the 
> problem. The truth is out there.
>
> 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 *Michael Hafen
> *Sent:* Thursday, 8 June 2023 7:17 AM
> *To:* Philippe Blouin <philippe.blouin at inlibro.com>
> *Cc:* koha-devel at lists.koha-community.org
> *Subject:* Re: [Koha-devel] Rewrite of URLs, flushing all empty arguments
>
> There are many layers interacting here. First is apache recieving the 
> request, where it passes through any apache modules that are loaded, 
> then it's passed to cgi or fcgi (you haven't mentioned whether you 
> have plack enabled, but you probably do), then it's passed to Koha's 
> codebase.  There could be version differences between Debian and 
> Ubuntu in either Apache modules or Perl CGI/FCGI modules that would 
> cause an empty get variable to be dropped.  The perl module versions 
> would be the first thing I'd check.
>
> On Wed, Jun 7, 2023 at 3:10 PM Philippe Blouin 
> <philippe.blouin at inlibro.com> wrote:
>
>     Hello all!
>
>     New issue (in 22.05 here, but might be anywhere):
>
>     https://somedomain.net/cgi-bin/koha/tools/letter.pl?op=delete_confirm
>     <https://v22-test-intranet.hapax.inlibro.net/cgi-bin/koha/tools/letter.pl?op=delete_confirm>_&*branchcode=*&module=suggestions&code=ACCEPTED_
>
>     When somedomain is onto one of our debian box (bullseye, 11), the
>     branchcode= disappears on landing. Be it on the connection page or
>     letter.pl <http://letter.pl>, we do not have the branchcode=
>     anymore, and the code throws an error (branchcode being undefined)
>
>     When running onto our laptops (Ubuntu) that doesn't happen.
>
>     We have no custom RewriteRule, so I'm trying to figure out WHERE
>     this rewrite comes from.
>
>     All suggestions welcomed,
>
>     Best regards,
>
>     -- 
>
>     Philippe Blouin,
>     Directeur de la technologie
>
>     Tél.  : (833) 465-4276, poste 230
>     philippe.blouin at inLibro.com
>
>     inLibro | pour esprit libre | www.inLibro.com
>     <http://www.inLibro.com>
>
>     _______________________________________________
>     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/
>
>
>
> -- 
>
> Michael Hafen
>
> Washington County School District Technology Department
>
> Systems Analyst
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230608/4bded968/attachment.htm>

From jonathan.druart at bugs.koha-community.org  Thu Jun  8 21:15:40 2023
From: jonathan.druart at bugs.koha-community.org (Jonathan Druart)
Date: Thu, 8 Jun 2023 21:15:40 +0200
Subject: [Koha-devel] Rewrite of URLs, flushing all empty arguments
In-Reply-To: <1f6744d4-bb83-931f-c73e-198cfe9856f1@inlibro.com>
References: <075afd84-c73b-edd7-8f55-f8a6eb2262f3@inlibro.com>
 <CAAh7UdnFjYZ45AfTgRfCk9rqiM-mrHFR0rC5Fjnre=5iPPKwJA@mail.gmail.com>
 <096c01d99999$3d5b4d20$b811e760$@prosentient.com.au>
 <1f6744d4-bb83-931f-c73e-198cfe9856f1@inlibro.com>
Message-ID: <CAJzKNY6bCV8WC6Qs2M5gRmcpOfrm_iozkDMEdrs=LsJ1BOPY1Q@mail.gmail.com>

Have a look at bug 25548 maybe?
It has been backported but maybe your apache config is not correct (see the
RewriteRule)?

Le jeu. 8 juin 2023 à 18:03, Philippe Blouin <philippe.blouin at inlibro.com>
a écrit :

> Hi David,
>
> Yes, connection being the login page.  Any call to it with &variable=&
> will get see its empty variable get flushed, as you summarized with
>
>
> http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&branchcode=&module=suggestions&code=ACCEPTED
>
> http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&module=suggestions&code=ACCEPTED
>
> The fact that it's not just branchcode, but any toto= or whatever= that
> gets flushed, seem to point to an apache setting.
>
> BUT my question was really: is Koha doing it ?  seems not, by your
> answers.  Is Apache doing it by default (new version...), my googling
> doesn't point to that, obviously.
>
> No redirect/rewrite in network.
>
> But again, you're telling me it's not Koha, so I'll dig.
>
> PS yes, the second link doesn't work.  We created a fix, but I didn't like
> it because I wanted to explore the root cause.
> Philippe Blouin,
> Directeur de la technologie
>
> Tél.  : (833) 465-4276, poste 230
> philippe.blouin at inLibro.com
> inLibro | pour esprit libre | www.inLibro.com
> On 2023-06-07 19:38, David Cook wrote:
>
> First things first, Philippe, you haven’t given enough information about
> the problem.
>
>
>
> For instance:
>
>
> http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&branchcode=&module=suggestions&code=ACCEPTED
>
>
> http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&module=suggestions&code=ACCEPTED
>
>
>
> On koha-testing-docker, which admittedly is a later version, neither of
> these raise an error, although the second link won’t work as expected. So
> you should look at the actual error message in your log, and try to work it
> out from there. It might be that it’s a known issue that’s been fixed
> upstream already.
>
>
>
> Not sure what you mean by “the connection page”. Is that the login screen
> for letter.pl or something else?
>
>
>
> When you say “the branchcode= disappears on landing”, it’s not clear what
> you mean. Take a look at the Network tab on your browser and see if there
> are any redirects. You can also increase the logging on your Apache to see
> what exactly it’s doing:
> https://httpd.apache.org/docs/2.4/mod/core.html#loglevel.
>
>
>
> Maybe that problem instance has some Javascript running that is
> interfering with the location URL. You can add breakpoints in your browser
> so that it pauses at certain points in the process of loading.
>
>
>
> My suggestion would be doing some hands-on troubleshooting. Work the
> problem. The truth is out there.
>
>
>
> 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>
> <koha-devel-bounces at lists.koha-community.org> *On Behalf Of *Michael Hafen
> *Sent:* Thursday, 8 June 2023 7:17 AM
> *To:* Philippe Blouin <philippe.blouin at inlibro.com>
> <philippe.blouin at inlibro.com>
> *Cc:* koha-devel at lists.koha-community.org
> *Subject:* Re: [Koha-devel] Rewrite of URLs, flushing all empty arguments
>
>
>
> There are many layers interacting here.  First is apache recieving the
> request, where it passes through any apache modules that are loaded, then
> it's passed to cgi or fcgi (you haven't mentioned whether you have plack
> enabled, but you probably do), then it's passed to Koha's codebase.  There
> could be version differences between Debian and Ubuntu in either Apache
> modules or Perl CGI/FCGI modules that would cause an empty get variable to
> be dropped.  The perl module versions would be the first thing I'd check.
>
>
>
> On Wed, Jun 7, 2023 at 3:10 PM Philippe Blouin <
> philippe.blouin at inlibro.com> wrote:
>
> Hello all!
>
> New issue (in 22.05 here, but might be anywhere):
>
> https://somedomain.net/cgi-bin/koha/tools/letter.pl?op=delete_confirm
> <https://v22-test-intranet.hapax.inlibro.net/cgi-bin/koha/tools/letter.pl?op=delete_confirm>
> *&branchcode=&module=suggestions&code=ACCEPTED*
>
> When somedomain is onto one of our debian box (bullseye, 11), the
> branchcode= disappears on landing.  Be it on the connection page or
> letter.pl, we do not have the branchcode= anymore, and the code throws an
> error (branchcode being undefined)
>
> When running onto our laptops (Ubuntu) that doesn't happen.
>
> We have no custom RewriteRule, so I'm trying to figure out WHERE this
> rewrite comes from.
>
> All suggestions welcomed,
>
> Best regards,
>
> --
>
> Philippe Blouin,
> Directeur de la technologie
>
> Tél.  : (833) 465-4276, poste 230
> philippe.blouin at inLibro.com
>
> inLibro | pour esprit libre | www.inLibro.com
>
> _______________________________________________
> 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/
>
>
>
> --
>
> Michael Hafen
>
> Washington County School District Technology Department
>
> Systems Analyst
>
> _______________________________________________
> 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/20230608/ca475d8f/attachment-0001.htm>

From philippe.blouin at inlibro.com  Thu Jun  8 21:29:00 2023
From: philippe.blouin at inlibro.com (Philippe Blouin)
Date: Thu, 8 Jun 2023 15:29:00 -0400
Subject: [Koha-devel] Rewrite of URLs, flushing all empty arguments
In-Reply-To: <CAJzKNY6bCV8WC6Qs2M5gRmcpOfrm_iozkDMEdrs=LsJ1BOPY1Q@mail.gmail.com>
References: <075afd84-c73b-edd7-8f55-f8a6eb2262f3@inlibro.com>
 <CAAh7UdnFjYZ45AfTgRfCk9rqiM-mrHFR0rC5Fjnre=5iPPKwJA@mail.gmail.com>
 <096c01d99999$3d5b4d20$b811e760$@prosentient.com.au>
 <1f6744d4-bb83-931f-c73e-198cfe9856f1@inlibro.com>
 <CAJzKNY6bCV8WC6Qs2M5gRmcpOfrm_iozkDMEdrs=LsJ1BOPY1Q@mail.gmail.com>
Message-ID: <b0e25368-a60e-4e4b-e611-08a0e1854ee2@inlibro.com>

Merci!!!!!!!

Yeah, that's exactly it.

I got sidetracked by reproducing it in prod, but it seems that it was on 
an old installation.  Recent ones do not have the problem. It'll be very 
easy to fix.

Big thanks!

Philippe Blouin,
Directeur de la technologie

Tél.  : (833) 465-4276, poste 230
philippe.blouin at inLibro.com

inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>
On 2023-06-08 15:15, Jonathan Druart wrote:
> Have a look at bug 25548 maybe?
> It has been backported but maybe your apache config is not correct 
> (see the RewriteRule)?
>
> Le jeu. 8 juin 2023 à 18:03, Philippe Blouin 
> <philippe.blouin at inlibro.com> a écrit :
>
>     Hi David,
>
>     Yes, connection being the login page.  Any call to it with
>     &variable=& will get see its empty variable get flushed, as you
>     summarized with
>
>     http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&branchcode=&module=suggestions&code=ACCEPTED
>     <http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&branchcode=&module=suggestions&code=ACCEPTED>
>
>     http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&module=suggestions&code=ACCEPTED
>     <http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&module=suggestions&code=ACCEPTED>
>
>
>     The fact that it's not just branchcode, but any toto= or whatever=
>     that gets flushed, seem to point to an apache setting.
>
>     BUT my question was really: is Koha doing it ?  seems not, by your
>     answers.  Is Apache doing it by default (new version...), my
>     googling doesn't point to that, obviously.
>
>     No redirect/rewrite in network.
>
>     But again, you're telling me it's not Koha, so I'll dig.
>
>     PS yes, the second link doesn't work.  We created a fix, but I
>     didn't like it because I wanted to explore the root cause.
>
>     Philippe Blouin,
>     Directeur de la technologie
>
>     Tél.  : (833) 465-4276, poste 230
>     philippe.blouin at inLibro.com
>
>     inLibro | pour esprit libre | www.inLibro.com
>     <http://www.inLibro.com>
>     On 2023-06-07 19:38, David Cook wrote:
>>
>>     First things first, Philippe, you haven’t given enough
>>     information about the problem.
>>
>>     For instance:
>>
>>     http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&branchcode=&module=suggestions&code=ACCEPTED
>>     <http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&branchcode=&module=suggestions&code=ACCEPTED>
>>
>>     http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&module=suggestions&code=ACCEPTED
>>     <http://localhost:8081/cgi-bin/koha/tools/letter.pl?op=delete_confirm&module=suggestions&code=ACCEPTED>
>>
>>     On koha-testing-docker, which admittedly is a later version,
>>     neither of these raise an error, although the second link won’t
>>     work as expected. So you should look at the actual error message
>>     in your log, and try to work it out from there. It might be that
>>     it’s a known issue that’s been fixed upstream already.
>>
>>     Not sure what you mean by “the connection page”. Is that the
>>     login screen for letter.pl <http://letter.pl> or something else?
>>
>>     When you say “the branchcode= disappears on landing”, it’s not
>>     clear what you mean. Take a look at the Network tab on your
>>     browser and see if there are any redirects. You can also increase
>>     the logging on your Apache to see what exactly it’s doing:
>>     https://httpd.apache.org/docs/2.4/mod/core.html#loglevel.
>>
>>     Maybe that problem instance has some Javascript running that is
>>     interfering with the location URL. You can add breakpoints in
>>     your browser so that it pauses at certain points in the process
>>     of loading.
>>
>>     My suggestion would be doing some hands-on troubleshooting. Work
>>     the problem. The truth is out there.
>>
>>     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>
>>     <mailto:koha-devel-bounces at lists.koha-community.org> *On Behalf
>>     Of *Michael Hafen
>>     *Sent:* Thursday, 8 June 2023 7:17 AM
>>     *To:* Philippe Blouin <philippe.blouin at inlibro.com>
>>     <mailto:philippe.blouin at inlibro.com>
>>     *Cc:* koha-devel at lists.koha-community.org
>>     *Subject:* Re: [Koha-devel] Rewrite of URLs, flushing all empty
>>     arguments
>>
>>     There are many layers interacting here.  First is apache
>>     recieving the request, where it passes through any apache modules
>>     that are loaded, then it's passed to cgi or fcgi (you haven't
>>     mentioned whether you have plack enabled, but you probably do),
>>     then it's passed to Koha's codebase. There could be version
>>     differences between Debian and Ubuntu in either Apache modules or
>>     Perl CGI/FCGI modules that would cause an empty get variable to
>>     be dropped.  The perl module versions would be the first thing
>>     I'd check.
>>
>>     On Wed, Jun 7, 2023 at 3:10 PM Philippe Blouin
>>     <philippe.blouin at inlibro.com> wrote:
>>
>>         Hello all!
>>
>>         New issue (in 22.05 here, but might be anywhere):
>>
>>         https://somedomain.net/cgi-bin/koha/tools/letter.pl?op=delete_confirm
>>         <https://v22-test-intranet.hapax.inlibro.net/cgi-bin/koha/tools/letter.pl?op=delete_confirm>_&*branchcode=*&module=suggestions&code=ACCEPTED_
>>
>>         When somedomain is onto one of our debian box (bullseye, 11),
>>         the branchcode= disappears on landing.  Be it on the
>>         connection page or letter.pl <http://letter.pl>, we do not
>>         have the branchcode= anymore, and the code throws an error
>>         (branchcode being undefined)
>>
>>         When running onto our laptops (Ubuntu) that doesn't happen.
>>
>>         We have no custom RewriteRule, so I'm trying to figure out
>>         WHERE this rewrite comes from.
>>
>>         All suggestions welcomed,
>>
>>         Best regards,
>>
>>         -- 
>>
>>         Philippe Blouin,
>>         Directeur de la technologie
>>
>>         Tél.  : (833) 465-4276, poste 230
>>         philippe.blouin at inLibro.com
>>
>>         inLibro | pour esprit libre | www.inLibro.com
>>         <http://www.inLibro.com>
>>
>>         _______________________________________________
>>         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/
>>
>>
>>
>>     -- 
>>
>>     Michael Hafen
>>
>>     Washington County School District Technology Department
>>
>>     Systems Analyst
>>
>     _______________________________________________
>     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/20230608/781e075a/attachment-0001.htm>

From dcook at prosentient.com.au  Fri Jun  9 02:03:38 2023
From: dcook at prosentient.com.au (David Cook)
Date: Fri, 9 Jun 2023 10:03:38 +1000
Subject: [Koha-devel] Integrating MarcEdit on Linux with Koha
Message-ID: <0a6801d99a65$e1a4ab20$a4ee0160$@prosentient.com.au>

Hi all,

 

Recently, I've been running the MarcEdit CLI tool cmarcedit.exe on Linux
(using mono) to run task automations that were created by librarians using
MarcEdit on Windows. 

 

I'm hoping to put together a Koha plugin to allow librarians to upload the
tasks and choose which Koha MARC records to run them on. (In this case, it
will be for export purposes rather than in-place updates, but easy enough
for someone to change.)

 

Does anyone think that sounds interesting? 

 

(Once the Koha REST API builds up a bit more for biblios/items and search, I
was thinking of getting in touch with Terry Reese to see about improving the
Koha integration in MarcEdit as well.)

 

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/20230609/13f4faf4/attachment.htm>

From tomascohen at gmail.com  Fri Jun  9 05:47:03 2023
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Fri, 9 Jun 2023 00:47:03 -0300
Subject: [Koha-devel] Integrating MarcEdit on Linux with Koha
In-Reply-To: <0a6801d99a65$e1a4ab20$a4ee0160$@prosentient.com.au>
References: <0a6801d99a65$e1a4ab20$a4ee0160$@prosentient.com.au>
Message-ID: <CABZfb=U1YQhxmckGxk6RKfOd0ATKnvguQhJkKQ66Qk7x2TCOYQ@mail.gmail.com>

It would be cool. I wasn't lucky when I contacted them offering to provide
an API. Good luck!

El jue, 8 jun 2023 21:04, David Cook <dcook at prosentient.com.au> escribió:

> Hi all,
>
>
>
> Recently, I’ve been running the MarcEdit CLI tool cmarcedit.exe on Linux
> (using mono) to run task automations that were created by librarians using
> MarcEdit on Windows.
>
>
>
> I’m hoping to put together a Koha plugin to allow librarians to upload the
> tasks and choose which Koha MARC records to run them on. (In this case, it
> will be for export purposes rather than in-place updates, but easy enough
> for someone to change.)
>
>
>
> Does anyone think that sounds interesting?
>
>
>
> (Once the Koha REST API builds up a bit more for biblios/items and search,
> I was thinking of getting in touch with Terry Reese to see about improving
> the Koha integration in MarcEdit as well.)
>
>
>
> 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/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230609/10bc8bb1/attachment.htm>

From dcook at prosentient.com.au  Fri Jun  9 06:22:44 2023
From: dcook at prosentient.com.au (David Cook)
Date: Fri, 9 Jun 2023 14:22:44 +1000
Subject: [Koha-devel] Useful fix for client IP address in plack.log for
 anyone running Koha behind a proxy
Message-ID: <0aaa01d99a8a$0a3f5f70$1ebe1e50$@prosentient.com.au>

Hi all,

 

Koha::Middleware::RealIP gives you the real client IP address in the Koha
code when running Koha behind a proxy. However, I noticed that this real
client IP address wasn't showing up in plack.log, and it really started to
bug me.

 

I discovered that Koha::Middleware::SetEnv was compromising the flow of the
$env variable through the Plack middlewares, but I've fixed it:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33967

 

It was a crazy-making problem, but it was a very simple fix, and it will
make your plack.log files much more useful. 

 

Simple yet comprehensive test plan too, so I hope that folk take a look at
it. 

 

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/20230609/bb5eb603/attachment.htm>

From kohanews at gmail.com  Tue Jun 13 09:07:38 2023
From: kohanews at gmail.com (Koha Newsletter)
Date: Tue, 13 Jun 2023 09:07:38 +0200
Subject: [Koha-devel] Call for news - Newsletter June 2023
Message-ID: <CAEqgz_nFYKhO8qRB_VsqOn3P-rfKipVj8SHcrAiT6NFnrYonQg@mail.gmail.com>

Hi

I'm collecting news for the June 2023 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/20230613/8a51e401/attachment.htm>

From wrobertson1981 at yahoo.co.nz  Wed Jun 14 02:38:21 2023
From: wrobertson1981 at yahoo.co.nz (Waylon Robertson)
Date: Wed, 14 Jun 2023 00:38:21 +0000 (UTC)
Subject: [Koha-devel] koha docker debian container
In-Reply-To: <30ee5d76-de4b-fd0d-3414-c44b59cb07dc@kohaaloha.com>
References: <289109367.2740214.1683012797535.ref@mail.yahoo.com>
 <289109367.2740214.1683012797535@mail.yahoo.com>
 <30ee5d76-de4b-fd0d-3414-c44b59cb07dc@kohaaloha.com>
Message-ID: <1874016324.2314931.1686703101875@mail.yahoo.com>

 what if I want to connect to an existing mysql/mariadb server, that's external to the docker?

    On Thursday, 4 May 2023 at 03:23:48 pm NZST, Mason James <mtj at kohaaloha.com> wrote:  
 
 On 2/05/23 7:33 pm, Waylon Robertson wrote:
> is there a pre-rollled bullseye docker container with koha, elasticsearch, and memcache all pre-setup and ready to go, somewhere? one that i can koha-create, then import a old koha database into?
> 
> _______________________________________________
> 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/

hi Waylon

you should look at loading your *.sql into KTD
  https://gitlab.com/koha-community/koha-testing-docker


https://hub.docker.com/r/koha/koha-testing/tags
https://hub.docker.com/r/koha/koha-testing/tags?page=1&name=bullseye
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230614/0773d5f4/attachment.htm>

From dcook at prosentient.com.au  Thu Jun 15 05:47:38 2023
From: dcook at prosentient.com.au (David Cook)
Date: Thu, 15 Jun 2023 13:47:38 +1000
Subject: [Koha-devel] Long-running inventory.pl causing timeout? There's a
 solution...
Message-ID: <017701d99f3c$269b0cd0$73d12670$@prosentient.com.au>

Hi all,

 

I imagine everyone has encountered situations where a long-running
inventory.pl has caused a timeout?

 

Well, at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31744 I
have a solution (ie workaround).

 

It requires running inventory.pl in CGI mode and without compression, so
that it can stream null data out until the actual inventory output is ready.


 

This prevents proxies from timing out while waiting for the inventory to
process and print out its output. It works for both HTML and CSV output too.

 

Ideally, it would be nice to have inventory.pl process in the background,
but I think this is a very practical workaround that keep inventory.pl
working until we can implement that more ideal solution.

 

I'm going to have some libraries test the solution behind their corporate
HTTP forward proxies and I'll let folks know on Bugzilla how that goes. I'm
optimistic since all my testing has gone well so far. 

 

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/20230615/9abc90ab/attachment.htm>

From tomascohen at gmail.com  Thu Jun 15 13:38:13 2023
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Thu, 15 Jun 2023 08:38:13 -0300
Subject: [Koha-devel] git-bz update
Message-ID: <CABZfb=VhtCPUAhTBAfZpzWd9b_3=V1iPuT4k11qd94F8vyFPVQ@mail.gmail.com>

Hi all, I wanted to mention that the 'apply_on_cascade' branch for git-bz
has been updated with a merge request from Andrii and Slava to upgrade it
to Python 3. It should be bundled in the latest KTD.

Kudos for them, and any issues you may find, please file a report on the
project site [1].

Best regards

[1] https://gitlab.com/koha-community/git-bz

-- 
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230615/6fc29c91/attachment.htm>

From nigel at titley.com  Thu Jun 15 19:11:50 2023
From: nigel at titley.com (Nigel Titley)
Date: Thu, 15 Jun 2023 18:11:50 +0100
Subject: [Koha-devel] Conflict between libossp-uuid-perl and
 libdata-uuid-perl
Message-ID: <c196dd01-696c-d0c4-e929-85a5feef586c@titley.com>

I'm currently running 22.05.13-1 (oldoldstable) on Ubuntu Focal and I'm 
trying to update to 22.11.06-3 (oldstable) and perhaps eventually to stable

However I'm getting the following complaint from apt

The following packages have unmet dependencies:
  libossp-uuid-perl : Conflicts: libdata-uuid-perl
E: Broken packages

As far as I can see the sympa package depends on libossp-uuid-perl and 
koha depends on libdata-uuid-perl

Before I start the laborious process of moving either Koha or Sympa to a 
different machine can anyone suggest a fix?

It looks like koha introduced a dependency on libdata-uuid-perl between 
oldoldstable and oldstable

Thanks for any help that anyone can offer

Nigel

From dcook at prosentient.com.au  Fri Jun 16 01:59:50 2023
From: dcook at prosentient.com.au (David Cook)
Date: Fri, 16 Jun 2023 09:59:50 +1000
Subject: [Koha-devel] Conflict between libossp-uuid-perl and
 libdata-uuid-perl
In-Reply-To: <c196dd01-696c-d0c4-e929-85a5feef586c@titley.com>
References: <c196dd01-696c-d0c4-e929-85a5feef586c@titley.com>
Message-ID: <024001d99fe5$8188be90$849a3bb0$@prosentient.com.au>

Hi Nigel,

I've bumped into this conflict before (https://irc.koha-community.org/out.pl?channel=koha;date=2023-01-11).

The libdata-uuid-perl package is required by libtest-dbix-class-perl, which is required for the koha-common package, although it really shouldn't be... we haven't gotten around to separating out the dependencies. 

Locally, what I do is patch debian/control and generate my own Debian packages, but that may or may not be an option for you. 

Unfortunately, the shortest path for you might be to move one of your systems to a different machine, but this is a topic that certainly needs some work...

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

-----Original Message-----
From: Koha-devel <koha-devel-bounces at lists.koha-community.org> On Behalf Of Nigel Titley
Sent: Friday, 16 June 2023 3:12 AM
To: koha-devel <koha-devel at lists.koha-community.org>
Subject: [Koha-devel] Conflict between libossp-uuid-perl and libdata-uuid-perl

I'm currently running 22.05.13-1 (oldoldstable) on Ubuntu Focal and I'm trying to update to 22.11.06-3 (oldstable) and perhaps eventually to stable

However I'm getting the following complaint from apt

The following packages have unmet dependencies:
  libossp-uuid-perl : Conflicts: libdata-uuid-perl
E: Broken packages

As far as I can see the sympa package depends on libossp-uuid-perl and koha depends on libdata-uuid-perl

Before I start the laborious process of moving either Koha or Sympa to a different machine can anyone suggest a fix?

It looks like koha introduced a dependency on libdata-uuid-perl between oldoldstable and oldstable

Thanks for any help that anyone can offer

Nigel
_______________________________________________
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 nigel at titley.com  Fri Jun 16 12:51:52 2023
From: nigel at titley.com (Nigel Titley)
Date: Fri, 16 Jun 2023 11:51:52 +0100
Subject: [Koha-devel] Conflict between libossp-uuid-perl and
 libdata-uuid-perl
In-Reply-To: <024001d99fe5$8188be90$849a3bb0$@prosentient.com.au>
References: <c196dd01-696c-d0c4-e929-85a5feef586c@titley.com>
 <024001d99fe5$8188be90$849a3bb0$@prosentient.com.au>
Message-ID: <cceab3fc-ce34-61e6-c439-ba0b8a814d82@titley.com>

Hi David

On 16/06/2023 00:59, David Cook wrote:
> Hi Nigel,
> 
> I've bumped into this conflict before (https://irc.koha-community.org/out.pl?channel=koha;date=2023-01-11).

That irc fragment was quite helpful. apt-cache rdepends confirms that 
it's libsoap-lite-perl that's pulling in the libossp-uuid-perl and it's 
sympa (amongst others) that's pulling in libsoap-lite-perl

> 
> The libdata-uuid-perl package is required by libtest-dbix-class-perl, which is required for the koha-common package, although it really shouldn't be... we haven't gotten around to separating out the dependencies.
> 
> Locally, what I do is patch debian/control and generate my own Debian packages, but that may or may not be an option for you.

Well, I probably could do it. I certainly could with a little diligent 
reading of documentation but I'm trying to keep this production system 
as clean as possible. So probably best just to wait for you guys to get 
around to sorting out the dependency in your copious spare time. There's 
no great panic anyway. I was just trying to get my production system a 
bit closer to stable.

> Unfortunately, the shortest path for you might be to move one of your systems to a different machine, but this is a topic that certainly needs some work...

I'm getting a little annoyed with Sympa anyway, the documentation is a 
mess, it has a tendency to leave zombie processes lying around, and its 
maintainers never answer questions. I may revert back to mailman. Which 
may fix the problem.

Thanks for the quick response

Nigel

> 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
> 
> -----Original Message-----
> From: Koha-devel <koha-devel-bounces at lists.koha-community.org> On Behalf Of Nigel Titley
> Sent: Friday, 16 June 2023 3:12 AM
> To: koha-devel <koha-devel at lists.koha-community.org>
> Subject: [Koha-devel] Conflict between libossp-uuid-perl and libdata-uuid-perl
> 
> I'm currently running 22.05.13-1 (oldoldstable) on Ubuntu Focal and I'm trying to update to 22.11.06-3 (oldstable) and perhaps eventually to stable
> 
> However I'm getting the following complaint from apt
> 
> The following packages have unmet dependencies:
>    libossp-uuid-perl : Conflicts: libdata-uuid-perl
> E: Broken packages
> 
> As far as I can see the sympa package depends on libossp-uuid-perl and koha depends on libdata-uuid-perl
> 
> Before I start the laborious process of moving either Koha or Sympa to a different machine can anyone suggest a fix?
> 
> It looks like koha introduced a dependency on libdata-uuid-perl between oldoldstable and oldstable
> 
> Thanks for any help that anyone can offer
> 
> Nigel
> _______________________________________________
> 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 dcook at prosentient.com.au  Mon Jun 19 03:47:06 2023
From: dcook at prosentient.com.au (David Cook)
Date: Mon, 19 Jun 2023 11:47:06 +1000
Subject: [Koha-devel] Inventory improvements
Message-ID: <008901d9a24f$f4b6d840$de2488c0$@prosentient.com.au>

Hi all,

 

It's probably not the right time of year for inventory.pl improvements, but
I've got a raft of changes for improving inventory.pl:

 

Bug 31744 - Inventory tool can take a long time and never complete

Bug 33989 - Inventory tool performs unnecessary authorized value lookups

Bug 34051 - Koha::AuthorisedValues->get_description_by_koha_field not
caching results for non-existent values

 

If you dislike how slow inventory.pl is and how it has a tendency to timeout
in managed IT environments, then you'll probably like these changes. I've
applied the first 2 locally, and my librarians are much happier as a result.

 

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/20230619/c43d80c0/attachment.htm>

From dcook at prosentient.com.au  Tue Jun 20 06:36:00 2023
From: dcook at prosentient.com.au (David Cook)
Date: Tue, 20 Jun 2023 14:36:00 +1000
Subject: [Koha-devel] Synchronizing a Koha database with kohastructure.sql
 (Bug 34064)
Message-ID: <013f01d9a330$c4bbf3f0$4e33dbd0$@prosentient.com.au>

Hi all,

 

I think we've all encountered issues with a Koha database being out of sync
with kohastructure.sql, and it's not a fun experience to have. Today, I ran
into items.paidfor columns that have survived long past a 20.11.00 upgrade.
While looking to resolve that across all my instances, I was thinking how
there could be other quirks as well, so I thought it would be nice to have
an audit script:

 

"Bug 34064 - Compare kohastructure.sql against current database using
database audit script"

 

It's not 100% perfect, but it does a very good job of detecting differences
between a live Koha database and kohastructure.sql, and provides suggestions
on how to remedy the database. 

 

It could be further improved, but I'm quite happy with this first draft. I'd
like to be able to run it using koha-foreach to get a sense of how in-sync
my Koha databases are on a server.

 

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/20230620/1e3d84aa/attachment.htm>

From M.de.Rooy at rijksmuseum.nl  Tue Jun 20 13:08:01 2023
From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy)
Date: Tue, 20 Jun 2023 11:08:01 +0000
Subject: [Koha-devel] Synchronizing a Koha database with
 kohastructure.sql (Bug 34064)
In-Reply-To: <013f01d9a330$c4bbf3f0$4e33dbd0$@prosentient.com.au>
References: <013f01d9a330$c4bbf3f0$4e33dbd0$@prosentient.com.au>
Message-ID: <AM0PR05MB50442EDBF7FD12D7C6925077CE5CA@AM0PR05MB5044.eurprd05.prod.outlook.com>

We already have misc/devel/update_dbix_class_files.pl.
Copy your Koha/Schema/Result before running. Or run it on a gitified install.
Compare changes.
________________________________
Van: David Cook <dcook at prosentient.com.au>
Verzonden: dinsdag 20 juni 2023 06:36
Aan: 'koha-devel' <koha-devel at lists.koha-community.org>
CC: Marcel de Rooy <M.de.Rooy at rijksmuseum.nl>; 'Tomas Cohen Arazi' <tomascohen at theke.io>; 'Jonathan Druart' <jonathan.druart at bugs.koha-community.org>
Onderwerp: Synchronizing a Koha database with kohastructure.sql (Bug 34064)


Hi all,



I think we’ve all encountered issues with a Koha database being out of sync with kohastructure.sql, and it’s not a fun experience to have. Today, I ran into items.paidfor columns that have survived long past a 20.11.00 upgrade. While looking to resolve that across all my instances, I was thinking how there could be other quirks as well, so I thought it would be nice to have an audit script:



“Bug 34064 - Compare kohastructure.sql against current database using database audit script”



It’s not 100% perfect, but it does a very good job of detecting differences between a live Koha database and kohastructure.sql, and provides suggestions on how to remedy the database.



It could be further improved, but I’m quite happy with this first draft. I’d like to be able to run it using koha-foreach to get a sense of how in-sync my Koha databases are on a server.



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/20230620/8f5a2c13/attachment.htm>

From dcook at prosentient.com.au  Wed Jun 21 01:37:21 2023
From: dcook at prosentient.com.au (David Cook)
Date: Wed, 21 Jun 2023 09:37:21 +1000
Subject: [Koha-devel] Synchronizing a Koha database with
 kohastructure.sql (Bug 34064)
In-Reply-To: <AM0PR05MB50442EDBF7FD12D7C6925077CE5CA@AM0PR05MB5044.eurprd05.prod.outlook.com>
References: <013f01d9a330$c4bbf3f0$4e33dbd0$@prosentient.com.au>
 <AM0PR05MB50442EDBF7FD12D7C6925077CE5CA@AM0PR05MB5044.eurprd05.prod.outlook.com>
Message-ID: <01bc01d9a3d0$3517fd70$9f47f850$@prosentient.com.au>

I thought about using the DBIx::Class files, but that gets messy on a server
with many Koha databases, which all have their own upgrade histories. The
DBIx::Class files also don't include all database information. 

 

I wanted a solution that could analyse and compare for me in a production
environment without needing any cleanup. 

 

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: Marcel de Rooy <M.de.Rooy at rijksmuseum.nl> 
Sent: Tuesday, June 20, 2023 9:08 PM
To: David Cook <dcook at prosentient.com.au>; 'koha-devel'
<koha-devel at lists.koha-community.org>
Cc: 'Tomas Cohen Arazi' <tomascohen at theke.io>; 'Jonathan Druart'
<jonathan.druart at bugs.koha-community.org>
Subject: Re: Synchronizing a Koha database with kohastructure.sql (Bug
34064)

 

We already have misc/devel/update_dbix_class_files.pl.

Copy your Koha/Schema/Result before running. Or run it on a gitified
install.

Compare changes.

  _____  

Van: David Cook <dcook at prosentient.com.au <mailto:dcook at prosentient.com.au>
>
Verzonden: dinsdag 20 juni 2023 06:36
Aan: 'koha-devel' <koha-devel at lists.koha-community.org
<mailto:koha-devel at lists.koha-community.org> >
CC: Marcel de Rooy <M.de.Rooy at rijksmuseum.nl
<mailto:M.de.Rooy at rijksmuseum.nl> >; 'Tomas Cohen Arazi'
<tomascohen at theke.io <mailto:tomascohen at theke.io> >; 'Jonathan Druart'
<jonathan.druart at bugs.koha-community.org
<mailto:jonathan.druart at bugs.koha-community.org> >
Onderwerp: Synchronizing a Koha database with kohastructure.sql (Bug 34064) 

 

Hi all,

 

I think we've all encountered issues with a Koha database being out of sync
with kohastructure.sql, and it's not a fun experience to have. Today, I ran
into items.paidfor columns that have survived long past a 20.11.00 upgrade.
While looking to resolve that across all my instances, I was thinking how
there could be other quirks as well, so I thought it would be nice to have
an audit script:

 

"Bug 34064 - Compare kohastructure.sql against current database using
database audit script"

 

It's not 100% perfect, but it does a very good job of detecting differences
between a live Koha database and kohastructure.sql, and provides suggestions
on how to remedy the database. 

 

It could be further improved, but I'm quite happy with this first draft. I'd
like to be able to run it using koha-foreach to get a sense of how in-sync
my Koha databases are on a server.

 

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/20230621/887a27fa/attachment.htm>

From dcook at prosentient.com.au  Wed Jun 21 03:05:56 2023
From: dcook at prosentient.com.au (David Cook)
Date: Wed, 21 Jun 2023 11:05:56 +1000
Subject: [Koha-devel] Dockerized Koha
Message-ID: <01e901d9a3dc$8d964b30$a8c2e190$@prosentient.com.au>

Hi all,

 

I've noticed a few people asking about Koha in Docker in production lately.

 

Do we have any appetite for starting to create a production-ready Dockerized
Koha? 

 

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/20230621/bc1a28f7/attachment-0001.htm>

From domm at plix.at  Wed Jun 21 09:11:48 2023
From: domm at plix.at (Thomas Klausner)
Date: Wed, 21 Jun 2023 09:11:48 +0200
Subject: [Koha-devel] Dockerized Koha
In-Reply-To: <01e901d9a3dc$8d964b30$a8c2e190$@prosentient.com.au>
References: <01e901d9a3dc$8d964b30$a8c2e190$@prosentient.com.au>
Message-ID: <20230621071148.GG626766@plix.at>

Hi!

On Wed, Jun 21, 2023 at 11:05:56AM +1000, David Cook wrote:
 
> Do we have any appetite for starting to create a production-ready Dockerized
> Koha? 

++

And while I have a lot of experience with deploying Perl apps using 
containers like Docker or Podman, I did not manage to get a (usable) 
Dockerfile / docker-compose for Koha running (in a reasonable amount of 
time; and then discovered koha-testing-docker for localdev..)

But I could definitely again try to spend some time on this!

Greetings,
domm


-- 
#!/usr/bin/perl                             https://domm.plix.at
for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}

From tomascohen at gmail.com  Wed Jun 21 19:47:35 2023
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Wed, 21 Jun 2023 14:47:35 -0300
Subject: [Koha-devel] Dockerized Koha
In-Reply-To: <20230621071148.GG626766@plix.at>
References: <01e901d9a3dc$8d964b30$a8c2e190$@prosentient.com.au>
 <20230621071148.GG626766@plix.at>
Message-ID: <CABZfb=XnFhLgntK5dYmU_tjnQQ4mh2QgQi88ym7DC7CYvT8=UQ@mail.gmail.com>

Hi all. We actually *have* a Docker image building pipeline [1]. If someone
wants to join the effort of publishing an official docker image, please put
it in the Roadmap wiki. That reminds me I didn't send the email about the
roadmap last week. Doing it right now.

Best regards.

[1]  https://gitlab.com/koha-community/docker/koha-docker

El mié, 21 jun 2023 a las 4:12, Thomas Klausner (<domm at plix.at>) escribió:

> Hi!
>
> On Wed, Jun 21, 2023 at 11:05:56AM +1000, David Cook wrote:
>
> > Do we have any appetite for starting to create a production-ready
> Dockerized
> > Koha?
>
> ++
>
> And while I have a lot of experience with deploying Perl apps using
> containers like Docker or Podman, I did not manage to get a (usable)
> Dockerfile / docker-compose for Koha running (in a reasonable amount of
> time; and then discovered koha-testing-docker for localdev..)
>
> But I could definitely again try to spend some time on this!
>
> Greetings,
> domm
>
>
> --
> #!/usr/bin/perl                             https://domm.plix.at
> for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}
> _______________________________________________
> 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/
>


-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230621/3a7e41d3/attachment.htm>

From tomascohen at gmail.com  Wed Jun 21 19:49:59 2023
From: tomascohen at gmail.com (Tomas Cohen Arazi)
Date: Wed, 21 Jun 2023 14:49:59 -0300
Subject: [Koha-devel] Roadmap 23.11
Message-ID: <CABZfb=UvkSA0HO3g1f-fT-2mhiPey1Z4hYTYzumsUGLKshepdQ@mail.gmail.com>

Hi all, better late than never, here's the roadmap site for the upcoming
23.11 release:

https://wiki.koha-community.org/wiki/Roadmap_for_23.11

As mentioned a few times already, that's where you should put your goals
for the cycle, and the things you're willing to participate on. That way
the release team knows who to reach and what to track. Enhancements and new
features outside the roadmap document will have lesser priority for our
non-infinite time.

Team work is expected to take place.

Best regards

-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230621/017d0346/attachment.htm>

From dcook at prosentient.com.au  Thu Jun 22 02:09:24 2023
From: dcook at prosentient.com.au (David Cook)
Date: Thu, 22 Jun 2023 10:09:24 +1000
Subject: [Koha-devel] Dockerized Koha
In-Reply-To: <CABZfb=XnFhLgntK5dYmU_tjnQQ4mh2QgQi88ym7DC7CYvT8=UQ@mail.gmail.com>
References: <01e901d9a3dc$8d964b30$a8c2e190$@prosentient.com.au>
 <20230621071148.GG626766@plix.at>
 <CABZfb=XnFhLgntK5dYmU_tjnQQ4mh2QgQi88ym7DC7CYvT8=UQ@mail.gmail.com>
Message-ID: <029701d9a49d$d2f91420$78eb3c60$@prosentient.com.au>

Personally, I don’t need it at the moment, although I briefly thought I might for one library. 

 

Sometimes I wonder about design…

 

1.	Would it be 1 Koha instance per container, or would it be a multi-tenant Koha in 1 container? 
2.	*How would upgrades be handled?*

a.	At the moment, when you install a new package, post-install hooks upgrade the database and change some configuration files. But that wouldn’t work if you install the package when making a new Docker image. Those hooks wouldn’t be invoked on the production system when you launch a new container from the new image. 

                                                               i.      The solution there might be to make a new script for performing upgrades, and for backwards compatibility it would still be called by the DEB post-install hooks, and the Docker entrypoint.sh could call it at startup time.

1.	Although if it were called at startup time, that could make startup unnecessarily slow, since the database upgrade check is very slow even when it has no work to do. (I have been meaning to fix that…)

2.	How would configuration files be persisted?

a.	If you have 1 Koha instance per container, you could just mount individual files, but there are a lot of configuration files, so that might get burdensome.
b.	If you have multi-tenant Koha, maybe you could mount the entirety of /etc/koha/sites. That would probably work well. 

                                                               i.      I don’t think you could mount /etc/koha because a lot of those files are generated by the koha-common package at install time, so you’d want to pick them up from the Docker image.

4.	How would other files be persisted?

a.	Mount to /var/lib/koha, /var/spool/koha, /var/log/koha(?)

 

Anything else I’ve missed?

 

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 Tomas Cohen Arazi
Sent: Thursday, June 22, 2023 3:48 AM
To: koha-devel at lists.koha-community.org
Subject: Re: [Koha-devel] Dockerized Koha

 

Hi all. We actually *have* a Docker image building pipeline [1]. If someone wants to join the effort of publishing an official docker image, please put it in the Roadmap wiki. That reminds me I didn't send the email about the roadmap last week. Doing it right now.

 

Best regards.

 

[1]  https://gitlab.com/koha-community/docker/koha-docker

 

El mié, 21 jun 2023 a las 4:12, Thomas Klausner (<domm at plix.at <mailto:domm at plix.at> >) escribió:

Hi!

On Wed, Jun 21, 2023 at 11:05:56AM +1000, David Cook wrote:

> Do we have any appetite for starting to create a production-ready Dockerized
> Koha? 

++

And while I have a lot of experience with deploying Perl apps using 
containers like Docker or Podman, I did not manage to get a (usable) 
Dockerfile / docker-compose for Koha running (in a reasonable amount of 
time; and then discovered koha-testing-docker for localdev..)

But I could definitely again try to spend some time on this!

Greetings,
domm


-- 
#!/usr/bin/perl                             https://domm.plix.at
for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}
_______________________________________________
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/




 

-- 

Tomás Cohen Arazi

Theke Solutions (https://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230622/595f6ca8/attachment-0001.htm>

From dcook at prosentient.com.au  Thu Jun 22 02:59:55 2023
From: dcook at prosentient.com.au (David Cook)
Date: Thu, 22 Jun 2023 10:59:55 +1000
Subject: [Koha-devel] Dockerized Koha
In-Reply-To: <029701d9a49d$d2f91420$78eb3c60$@prosentient.com.au>
References: <01e901d9a3dc$8d964b30$a8c2e190$@prosentient.com.au>
 <20230621071148.GG626766@plix.at>
 <CABZfb=XnFhLgntK5dYmU_tjnQQ4mh2QgQi88ym7DC7CYvT8=UQ@mail.gmail.com>
 <029701d9a49d$d2f91420$78eb3c60$@prosentient.com.au>
Message-ID: <02a101d9a4a4$df83f820$9e8be860$@prosentient.com.au>

By the way, I’ve raised bug 34088 to fix the slowness of the database upgrade checks. I’ve got a workable patch there, and I’ll look at polishing it up when I have a bit more free time.

 

With the database upgrade check time fixed, I think we could do an “check_for_updates.sh” script in the Docker container entry point script. 

 

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 David Cook
Sent: Thursday, June 22, 2023 10:09 AM
To: koha-devel at lists.koha-community.org
Subject: Re: [Koha-devel] Dockerized Koha

 

Personally, I don’t need it at the moment, although I briefly thought I might for one library. 

 

Sometimes I wonder about design…

 

1.	Would it be 1 Koha instance per container, or would it be a multi-tenant Koha in 1 container? 
2.	*How would upgrades be handled?*

a.	At the moment, when you install a new package, post-install hooks upgrade the database and change some configuration files. But that wouldn’t work if you install the package when making a new Docker image. Those hooks wouldn’t be invoked on the production system when you launch a new container from the new image. 

                                                               i.      The solution there might be to make a new script for performing upgrades, and for backwards compatibility it would still be called by the DEB post-install hooks, and the Docker entrypoint.sh could call it at startup time.

1.	Although if it were called at startup time, that could make startup unnecessarily slow, since the database upgrade check is very slow even when it has no work to do. (I have been meaning to fix that…)

2.	How would configuration files be persisted?

a.	If you have 1 Koha instance per container, you could just mount individual files, but there are a lot of configuration files, so that might get burdensome.
b.	If you have multi-tenant Koha, maybe you could mount the entirety of /etc/koha/sites. That would probably work well. 

                                                               i.      I don’t think you could mount /etc/koha because a lot of those files are generated by the koha-common package at install time, so you’d want to pick them up from the Docker image.

4.	How would other files be persisted?

a.	Mount to /var/lib/koha, /var/spool/koha, /var/log/koha(?)

 

Anything else I’ve missed?

 

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 <mailto:koha-devel-bounces at lists.koha-community.org> > On Behalf Of Tomas Cohen Arazi
Sent: Thursday, June 22, 2023 3:48 AM
To: koha-devel at lists.koha-community.org <mailto:koha-devel at lists.koha-community.org> 
Subject: Re: [Koha-devel] Dockerized Koha

 

Hi all. We actually *have* a Docker image building pipeline [1]. If someone wants to join the effort of publishing an official docker image, please put it in the Roadmap wiki. That reminds me I didn't send the email about the roadmap last week. Doing it right now.

 

Best regards.

 

[1]  https://gitlab.com/koha-community/docker/koha-docker

 

El mié, 21 jun 2023 a las 4:12, Thomas Klausner (<domm at plix.at <mailto:domm at plix.at> >) escribió:

Hi!

On Wed, Jun 21, 2023 at 11:05:56AM +1000, David Cook wrote:

> Do we have any appetite for starting to create a production-ready Dockerized
> Koha? 

++

And while I have a lot of experience with deploying Perl apps using 
containers like Docker or Podman, I did not manage to get a (usable) 
Dockerfile / docker-compose for Koha running (in a reasonable amount of 
time; and then discovered koha-testing-docker for localdev..)

But I could definitely again try to spend some time on this!

Greetings,
domm


-- 
#!/usr/bin/perl                             https://domm.plix.at
for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}
_______________________________________________
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/




 

-- 

Tomás Cohen Arazi

Theke Solutions (https://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F

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

From pedro.amorim at ptfs-europe.com  Mon Jun 26 10:44:18 2023
From: pedro.amorim at ptfs-europe.com (Amorim, Pedro)
Date: Mon, 26 Jun 2023 08:44:18 +0000
Subject: [Koha-devel] Koha 22.11.07 released
Message-ID: <CAB2K=vuoq0DTgprY_y-6E_N+2LAnTvnBavB-WhTKdX=qVP175g@mail.gmail.com>

The Koha community is proud to announce the release of Koha 22.11.07.

Koha 22.11.07 is a bugfix/maintenance release.

It includes 5 enhancements, 77 bugfixes.

The full release notes are available here:
https://koha-community.org/koha-23-05-released/

Debian packages should be available soon

Best regards




Pedro Amorim

Software Engineer



E: pedro.amorim at ptfs-europe.com

www.ptfs-europe.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230626/94e70131/attachment.htm>

From pedro.amorim at ptfs-europe.com  Mon Jun 26 10:50:17 2023
From: pedro.amorim at ptfs-europe.com (Amorim, Pedro)
Date: Mon, 26 Jun 2023 08:50:17 +0000
Subject: [Koha-devel] Koha 22.11.07 released
Message-ID: <CAB2K=vtW-nM5Cfi5fyVe35RCrSc6iA7eExa4QpVddNu76BvsnA@mail.gmail.com>

The Koha community is proud to announce the release of Koha 22.11.07.

Koha 22.11.07 is a bugfix/maintenance release.

It includes 5 enhancements, 77 bugfixes.

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

Debian packages should be available soon

(Apologies for the previous announcement e-mail containing a link error!
First release as release maintainer and whatnot!)

Best regards


Pedro Amorim

Software Engineer



E: pedro.amorim at ptfs-europe.com

www.ptfs-europe.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230626/3d0ace03/attachment.htm>

From fridolin.somers at biblibre.com  Wed Jun 28 15:35:46 2023
From: fridolin.somers at biblibre.com (Fridolin SOMERS)
Date: Wed, 28 Jun 2023 15:35:46 +0200
Subject: [Koha-devel] Koha 23.05.01 released
Message-ID: <d3639747-a15d-a878-38a3-3c691ae363cf@biblibre.com>

Hello everyone 🤗

The Koha community is proud to announce the release of Koha 23.05.01.

It is a bugfix/maintenance release including 6 enhancements, 35 bugfixes.

The full release notes are available here:
https://koha-community.org/koha-23-05-01-released/

Debian packages should be available soon 🎁

With a great pleasure I will be the 23.05 cooking chef this 6 months meal.

Best regards 🤓

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

From kohanews at gmail.com  Thu Jun 29 11:00:25 2023
From: kohanews at gmail.com (Koha Newsletter)
Date: Thu, 29 Jun 2023 11:00:25 +0200
Subject: [Koha-devel] Koha Community Newsletter: June 2023
Message-ID: <CAEqgz_ny91hzXDT+r1aoTu6yb6muwh2sL8fbOf3_a5ade+PEsw@mail.gmail.com>

The Koha Community Newsletter for June 2023 is here:

https://koha-community.org/koha-community-newsletter-june-2023/

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/20230629/a11453e6/attachment.htm>

From aleisha at catalyst.net.nz  Fri Jun 30 03:03:51 2023
From: aleisha at catalyst.net.nz (Aleisha Amohia)
Date: Fri, 30 Jun 2023 13:03:51 +1200
Subject: [Koha-devel] Problems with pbuilder and gitlab runner
Message-ID: <a587ba75-9c9e-f3e0-2cdc-6c50e1e7cb21@catalyst.net.nz>

Hello everyone

We're having a problem with pbuilder and I wonder if anyone is 
experiencing the same thing, or if we're misunderstanding how this is 
supposed to work.

We have pbuilder set up on a test server, and we've run all these 
commands: 
https://wiki.koha-community.org/wiki/Building_Debian_Packages_-_The_Easy_Way#Enter_pbuilder

Then we set off a pipeline in Gitlab, which essentially just runs 
./debian/build-git-snapshot to build our Koha package.

We've noticed that we are being required to log into pbuilder and run 
those commands from the wiki page before every package build/pipeline.

Is that expected? We would've thought that the commands only have to be 
run once and the environment is then saved in base.tgz and used.

Has anyone else experienced this and know how to fix?

-- 
*Aleisha Amohia (she/her)*
Koha Technical Lead
*Catalyst.Net Limited - Expert Open Source Solutions*

*Catalyst.Net Ltd - a Catalyst IT group company*
Tel: +64 4 499 2267 | www.catalyst.net.nz <http://www.catalyst.net.nz>

Catalyst Logo

CONFIDENTIALITY NOTICE: This email is intended for the named recipients 
only. It may contain privileged, confidential or copyright information. 
If you are not the named recipient, any use, reliance upon, disclosure 
or copying of this email or its attachments is unauthorised. If you have 
received this email in error, please reply via email or call +64 4 499 2267.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20230630/0e203a30/attachment.htm>