Maybe you need some other hook. Ones that allows you to make changes to the
object right before it is stored instead of this one, that gets the 'just
updated' object.
When I added 'after' hooks for biblios and items actions, the idea was that
they should act as triggers for other actions: in my
I had issues with reset_all as well. It is some latest changes on the db
El jue., 11 feb. 2021 15:32, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> escribió:
> Which errors do you get?
>
> Le jeu. 11 févr. 2021 à 18:03, Andrew Fuerste-Henry <
> and...@bywatersolutions.com> a écrit :
Those are just defaults in the OS distribution, that can be changed at will.
Koha, internally, sets the character set correctly on connection time [1].
You should always check when they drop support for our used encodings.
Which is not the case (for now?). We have the test suite run against the
You need to run it inside koha-shell
El lun., 18 oct. 2021 12:30, Stephen Graham
escribió:
> Actually I just testing this now and cannot get it to work. I'm getting an
> error about not being able to write to the plack-opac-error.log file. I'm
> logged in as the usual koha user, and it's for a
Effectively ignored. Oh, wait.
El lun, 6 dic 2021 a las 8:14, Marcel de Rooy ()
escribió:
> Just testing if these signatures did not come along now anymore
>
> Have a great day, Koha.
>
> Marcel
> ___
> Koha-devel mailing list
>
Hi all, I wanted to mention that I've submitted patches for bug 28020 [1].
The change introduces a new attribute to the generic error response object
that is reused everywhere in the spec. The new attribute is called
'error_code' and is intended to be adopted so API consumers have better
means to
+1
El mié., 29 dic. 2021 5:40, Fridolin SOMERS
escribió:
> Hi,
>
> We are getting close to end date for KohaCon22 proposals, January 8.
>
> Unfortunately there is actually no proposal :
> https://wiki.koha-community.org/wiki/KohaCon22_Proposals
>
> This as been discussed in last dev meeting.
>
This is great! Community involvement will be key to reach the release!
El lun., 13 dic. 2021 12:11, Paul Poulain
escribió:
> Hello all,
>
> The staff interface design is something like 8 years old. It's worth
> being refreshed.
>
> We'd like to sponsor that work, with the idea to have a 22.05
I can try installing it in the community Portainer server.
El mar., 16 nov. 2021 3:20, Fridolin SOMERS
escribió:
> Thanks a lot David for your sharing.
>
> What plugin do you have in mind ?
> If we like the features of this software, it is worth doing the install
> work I bet.
>
> Best regards,
I'm more inclined to make ktd use an external rabbitmq container. But yeah,
we could do it
El mar., 16 nov. 2021 12:17, Marcel de Rooy escribió:
> Looks like we should add this "fix". Before starting the rabbitmq service,
> rm -rf /var/run/rabbitmq.
> Tested this in a Docker container, works
If you are not using the output of grep (it returns all matching elements)
you should be using 'any', which short-circuits on the first match. And
List::Util is a core library nowadays.
That's why I use it in those scenarios and suggest it on QA as well.
Best regards
El vie., 19 nov. 2021
El mié, 1 dic 2021 a las 12:24, Jonathan Druart (<
jonathan.dru...@bugs.koha-community.org>) escribió:
> Hello everybody,
>
> I have been listing some tasks I would like to work on during the next
> development cycle.
> I suggest a give and take approach. Help me on one or more of those
> topics
That's fantastic!
El mar., 15 feb. 2022 13:01, Owen Leonard escribió:
> On Thu, Feb 10, 2022 at 3:27 PM Fridolin SOMERS
> wrote:
> > Hi devels.
> > I've changed next dev IRC meeting hour from 15 UTC to 10 UTC.
> >
>
We have lots of indexes. KEY and INDEX are basically synonyms in MySQL.
We in fact might have too many indexes defined. This is a valid hypothesis
when the index size (on disk) is too close to the DB size for a table.
El lun, 21 mar 2022 a las 14:40, Victor Grousset/tuxayo ()
escribió:
> Hi :)
Hi, let me tell you a short and (technical but) interesting story. Most of
you might know about this, but I found it could be useful to know and/or to
refresh.
DBIC has a nice property that our Koha::Objects inherited (obviously): you
can chain calls like this:
Koha::Patrons->search(
Hi all, happy 2022 :-D
I wanted to mention that a bug that introduces Koha::Result::Boolean has
been pushed [1]. This class provides a way to return an object, that
evaluates to a boolean in (Perl's) bool context but also carries reasons
for the result.
It has been used in a couple places, like
You should use koha-testing-docker, there's an alias specifically for that.
Once you use it, the instructions Michael have you are similar!
El mié., 19 ene. 2022 16:31, Samu Heiskanen
escribió:
> Hi,
>
> I am a new Koha developer from windy and cold Finland. As new to the
> Koha-community, I'd
What I do is running the qa script within the kshell. We should add an
alias there.
El mar., 25 ene. 2022 7:49, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> escribió:
> Hi devs,
>
> If you are using koha-testing-docker and you write patches, you certainly
> also use the koha-qa.pl
Hi all. Today we pushed to master a needed upgrade for Cypress. The new
Cypress configuration file that is included in the master branch IS NOT
COMPATIBLE with older Cypress versions, and thus you need to pull the
latest KTD image in order for things to work.
I didn't expect a `ktd up` to fail
Hi all, we've recently run into issues on the stable branches with DB
upgrades failing.
Jonathan put together a proposal that will help us catch those beforehand,
as mentioned on [bug 34683](
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34683).
Please take a look ASAP and help us
I see this email.
El lun, 11 sept 2023 a las 12:21, Philippe Blouin (<
philippe.blo...@inlibro.com>) escribió:
> Hi!
>
> Someone here (Shi Yao) has been trying to write to koha-devel starting two
> weeks ago. The emails never got through, nor he got any followup from
> koha-devel-owner.
>
>
Hi all, I've been working on making things easier on ARM64 processors (M1,
M2, and so on) on top of the great work from Mason.
Now we need help testing a branch [1].
I specially need non-ARM testers, so we are sure nothing gets broken with
the change.
To test:
1. On your KTD clone do:
$ git
What plugin is that?
El jue, 31 ago 2023 a las 17:16, Philippe Blouin (<
philippe.blo...@inlibro.com>) escribió:
> Hi!
>
> Any suggestion onto why our plugin doesn't seem to work on (bywater's)
> Devboxes while being perfectly fine in 22,23 or master local installs ?
>
> The UI of the config is
Hi all. I'm wrapping a KitchenSink patch to highlight how it would be used.
The background jobs themselves work, but the template side I never looked
at. I thought there was some default display showing all the report
metadata, but it seems all descriptions are hardcoded and a dev is required
to
El vie, 6 oct 2023 a las 11:03, Olli-Antti Hypernova (<
olli-antti.kivila...@hypernova.fi>) escribió:
> Good idea. Anything to disband the "SmartUI"-antipattern is good for me.
>
>
> We should add a new endpoint following established nomenclature.
>
> eg. PUT /biblios/123/merge/456 (PUT as it
Look at this commit:
https://github.com/bywatersolutions/dev-koha-plugin-kitchen-sink/commit/30d1446387fa864fe49f25cb53a2915b33ef73ce
Best regards
El vie, 13 oct 2023 a las 10:09, Tomas Cohen Arazi ()
escribió:
> Hi all. I'm wrapping a KitchenSink patch to highlight how it would be u
id 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:* Kyle Hall
> *Sent:* Satur
I'd say it is a neat core feature as well! Nice finding!!
El lun, 18 abr 2022 23:04, escribió:
> Hi all,
>
>
>
> I was looking up a book the other day on Google when I noticed a section
> called “Borrow” and it showed two local library services where I could
> borrow the book.
>
>
>
> I did a
Congrats!!!
El vie, 27 may 2022 20:42, Fridolin SOMERS
escribió:
> Hello everyone 珞
>
> The Koha community is proud to announce the release of Koha 22.05.00.
>
> It is a major release, that comes with 6 new features, 239 enhancements,
> 360 bugfixes 者
>
> The full release notes are available
neer
> Prosentient Systems
> Suite 7.03
> 6a Glen St
> Milsons Point NSW 2061
> Australia
>
> Office: 02 9212 0899
> Online: 02 8005 0595
>
> From: Koha-devel On Behalf
> Of Jonathan Druart
> Sent: Thursday, 26 May 2022 8:33 AM
> To: Tomas Cohen Arazi
> Cc: koha-d
Hi, we need to take a look at the upcoming changes and make a decision on
enrolling as an Open Source project:
https://about.gitlab.com/blog/2022/02/04/ultimate-perks-for-open-source-projects/
Please read carefully so we can make a decision eventually.
--
Tomás Cohen Arazi
Theke Solutions
Just so you know and because these things frequently go unadvertised: we
now have a --force switch in KTD for the `dbic` command.
Enjoy.
--
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha-devel mailing
I like te idea, but where would you put those headings?
El sáb., 19 jun. 2021 3:09 p. m., Julien Sicot
escribió:
> Hi all,
>
> An enhancement idea :
>
> It could be interesting to enrich the bibliographic records exposed in OAI
> with see-from headings, this would allow users who use koha with
I think you can improve it by doing a LEFT JOIN between the two tables
instead of the IN comparison.
That way you will find those without matching authorities when they
auth_header counterpart is NULL.
If you want to go precise, you should also add 100$9 vs authid to the game.
Good luck!
El
Hi all, I have submitted the form, and also contacted the sales department
so we can explain how the project management works and to clarify any
doubts. I will add others to the conversation once I get the call with the
sales people.
Thanks everyone.
El mié, 29 jun 2022 a las 0:37, Victor
Hi all, I've been trying to track down a problem with TestBuilder tests.
The are failing (almost) randomly but I narrow it down to:
- Koha::Checkouts::Renewals
- Koha::Biblio::ItemGroup::Items
I ran out of fuel today, but it would be great if some more eyes were put
on this, so I can move on
9.99~really6.81?
El lun, 27 jun 2022 a las 15:41, Mason James () escribió:
> hiya
> i've pushed a pkg to the dev and 22.05 suites, on koha-staging - for
> testing
>
> we do seem to have a potential problem for deb11(>=) and ES6 - as deb11
> has libsearch-elasticsearch-perl-7.30-1, which seems to
ss an AI value, TestBuilder
> explodes with "Value not allowed for auto_incr issue_id in Issue".
> I guess the fix would be to use the constraint's name instead of the
> column's name.
>
> Le sam. 9 juil. 2022 à 02:18, Tomas Cohen Arazi a
> écrit :
> >
> >
Thanks everyone!
El mar, 12 jul 2022 a las 0:15, Tomas Cohen Arazi ()
escribió:
> Thanks, Jonathan. Your pointer was very helpful.
>
> El lun, 11 jul 2022 6:27, Jonathan Druart
> escribió:
>
>> I think the problem is that Koha::Checkouts::Renewals has 2
>> ("
Hi all, I have started outlining a Roadmap document [1] for us to
put together for the 22.11 release. Feel free to comment there or add the
things you plan to work on during this cycle. If there are already bugs
filed, please add links to them as well.
Thanks!
[1]
I think we will contact Gitlab to explain how the project works and see how
things fit (or not). We ain't no lawyers.
We haven't reached any quotas yet, and we can of course host our own
workers. So it feels we're gonna be good in any case.
Best regards
El vie, 10 jun 2022 17:42, Victor
Hi Owen!
If the tool is deprecated, let's find another one. I'll follow your lead on
this matter.
El mié, 20 jul 2022 7:34, Renvoize, Martin
escribió:
> I'm in a similar camp to David, though I have touched it a few times here
> and there.. I wasn't aware of a linter, but would take your lead
+1
Is it possible to apply branches to a sandbox also? Or it just interacts
with BZ?
El mar, 26 jul 2022 a las 12:43, Katrin Fischer ()
escribió:
> I still think a dedicated sandbox would be really helpful. What Victor
> says is certainly true for smaller patch sets, but this is a big patch
>
I'm pretty sure we don't support Debian 9 anymore. And Ubuntu 18.04 is in
the same situation.
Using those old MariaDB and MySQL versions is problematic and thus
discouraged.
El mié, 27 jul 2022 2:15, escribió:
> Hi all,
>
>
>
> While commenting on Bug 28267, I decided to review what versions
s Point NSW 2061
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Online: 02 8005 0595
>
>
>
> *From:* Tomas Cohen Arazi
> *Sent:* Wednesday, 27 July 2022 11:36 PM
> *To:* David Cook
> *Cc:* Koha Devel
> *Subject:* Re: [Koha-devel] Debian 9 LTS EOL
>
Hi, David. I meant to answer your first email. I'm submitting (immediately)
an alternative implementation I've been working on but failed to wrap up
sooner.
I've read the one you pointed and if fairly similar to the google oaidc
implementation for OPAC, so it is correct.
My plan is to do it for
You've got the wrong library version.
Ubuntu 20.04 is old in terms of the Debian version of is based on. I'm
pretty sure you can append 'focal' to the repository configuration line and
it will pull the right dependencies.
El vie, 26 ago 2022 14:08, Philippe Blouin
escribió:
> Hi folks!
>
> Got
ibro | pour esprit libre | www.inLibro.com
> On 2022-08-26 13:32, Tomas Cohen Arazi wrote:
>
> You've got the wrong library version.
>
> Ubuntu 20.04 is old in terms of the Debian version of is based on. I'm
> pretty sure you can append 'focal' to the repository configuration line a
eletedborrowers, borrower_modifications. We might also
> want to think about how the data will move when email verification is used
> in addition to moderation.
>
> Hope this helps,
>
> Katrin
> On 31.08.22 04:35, Tomas Cohen Arazi wrote:
>
> Please, use a separate table. An
Please, use a separate table. And think of the request workflow handling in
the db, the statuses (as enum), how it will be handled at library or
library group level. Even if not implemented at this stage. Also, maybe you
need more than one table, don't fear adding tables if they make sense and
Hi all, this cycle has been very busy and all of a sudden, it is ending!
This are the preliminary dates so you are aware of:
* Oct 28th - "Soft" feature freeze, nothing big or with high risk of
side-effects will be included into the final release if not marked
as Passed QA
* Nov 3-5 - "Hard"
I think with background jobs we have most of the framework that is needed
to deal with this within Koha.
Best regards
El mar, 25 oct 2022 7:08, BOUIS Sonia escribió:
> Hi,
> KohaLA would like to finance an OAI-PMH client in Koha but, we have
> questions that we want to raise to the community.
Excellent work Thomas!
Congratulations for getting it done so well.
Thanks!!!
El jue, 27 oct 2022 a las 9:29, Thomas Dukleth ()
escribió:
> [For those not subscribed or giving attention to the Koha mailing list, I
> repeat the announcement here without in message cross-posting.]
>
> The Koha
Are you by chance running the command in the root shell? You should always
run it inside koha-shell
El vie, 28 oct 2022 8:03, Michael Kuhn escribió:
> Hi
>
> I am running a fresh installation of Koha 22.05.04 on Debian 11.
>
> I am trying to load some data using "bulkmarcimport.pl":
>
> #
Yeah, the docs are really generic, and there are several ways to install
Koha. Packages (i.e. having koha-shell) is one of them. Please file an
issue on the manual's project so we document it better.
Regarding the fact it worked before, have you changed the server? It is not
working because of
:-D
El mar, 25 oct 2022 a las 15:33, Lucas Gass ()
escribió:
> Hello, Hola, Bonjour, Guten tag, Olá!
>
> The Koha community is proud to announce the release of Koha 22.05.06!
>
> Koha 22.05.06 includes 8 enhancements, 42 bugfixes, and 1 security fix.
>
> The full release notes can be found here:
onality on
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20916
>
> Were you planning on working on that or is it available for others to work
> on it?
>
>
> On 7/09/22 03:04, Tomas Cohen Arazi wrote:
>
> I think we need to resurrect the idea of a patron i
Thank you!!
El jue, 15 sept 2022 6:48, Mason James escribió:
> hi folks
>
> i've made a guide here...
>
> https://wiki.koha-community.org/wiki/REST_API_Debug
>
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
>
Is koha-worker running?
El vie, 9 sept 2022 12:42, Philippe Blouin
escribió:
> Hello kohaers!
>
> Simply put: our production servers installation work very fine, each
> change into a record is immediately reindexed into ES.
>
> BUT on laptop (ubuntu 20 or 22), the reindexing never occurs. We
I'd say we could add a hook for plugins to inject variables for notices.
El dom, 2 oct 2022 4:01, Indranil Das Gupta escribió:
> Hi all,
>
> I've written a new SMS::Send driver module for NIC SMS service (a
> federal IT service provider to Govt agencies in India). It's working
> fine on its
entient Systems
> Suite 7.03
> 6a Glen St
> Milsons Point NSW 2061
> Australia
>
> Office: 02 9212 0899
> Online: 02 8005 0595
>
> -Original Message-
> From: Jonathan Druart
> Sent: Thursday, 4 August 2022 10:17 PM
> To: Tomas Cohen Arazi
> Cc: David Coo
d then sends an API request
>> using an offset and that count to handle the paging. Their internal API
>> breaks it into 2 steps, so I have to hit the database twice anyway.
>>
>>
>>
>> David Cook
>>
>> Senior Software Engineer
>>
>> Prosent
Only with x-koha-embed
El jue, 4 ago 2022 3:54, escribió:
> Hi all,
>
>
>
> Is there a method for getting a “count” using the REST API without
> fetching every record?
>
>
>
> When building a paging lookup outside of Koha, it would be useful to get a
> total record count and then just fetch
Hi, koha-jenkins is now sending to #koha-ci only. Will move it to #koha-bots
El mar, 2 ago 2022 21:06, Victor Grousset/tuxayo
escribió:
> Hi :)
>
> It's about the move of automated output to #koha-bots
>
> Cheers,
>
> --
> Victor Grousset/tuxayo
> ___
Hi all, I made some pushes to the stable branches (22.11, 22.05 and 21.11)
so the images are (internally) aligned with (master's) `ktd` command.
Please let me know if you encounter any issues.
Merry xmas everyone!
--
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG:
Hi all, last cycle we worked through a roadmap which was not 100% finished,
but we made good progress in many of the main milestones:
- Task queue streamlining (several improvements, progress bars, etc)
- ERM (done)
- Introduction of Vue (done)
- Dates handling (partially done)
- Circ, holds,
Thanks for letting us know! Good luck!
El lun, 2 ene 2023 19:54, Chris Cormack escribió:
> Hi All
>
> The linode that bugs, dashboard, splitter, download, plus the bots run
> on needs an OS upgrade.
>
> I am about to snapshot it and attempt that now. The server may or may
> not go down for
ntu 18.04 to 20.04. (18.04 goes out
> of support in April).
> It should be slightly faster with more ram available.
>
> Happy new OS for new year :)
>
> Chris
>
> On Tue, 3 Jan 2023 at 12:55, Tomas Cohen Arazi
> wrote:
> >
> > Thanks for letting us know! G
I've seen some errors on saved reports. But it looks like DB structure
changes won't be easy to fix manually.
El mar, 3 ene 2023 a las 14:43, David Nind () escribió:
> Hi Chris.
>
> Thanks for all your work in supporting and maintaining these!
>
> I get this message when trying to access the IRC
Hi all, after several comments from people struggling with permissions,
yarn build, etc; I've went ahead and tweaked the new `ktd` command so the
default behavior is to jump into the container, on the instance user. i.e.
# this command will put you in what we traditionally call 'kshell'
ktd
I normally point vscode's perltidy extension to the shipped perltidyrc:
https://git.koha-community.org/Koha-community/Koha/src/branch/master/xt/perltidyrc
and do Ctrl+k-f on the region I'm editing.
El vie, 9 dic 2022 0:27, David Cook escribió:
> Hi all,
>
>
>
> I’ve heard a few people saying
El vie, 2 dic 2022 a las 11:43, Jonathan Druart (<
jonathan.dru...@bugs.koha-community.org>) escribió:
> 10. CI should drive the pushes. No more push if CI is not green. The
> more we wait the harder it is to track down the origin of the problem.
> Last cycle some jobs have been red for months,
What is your dev environment like? a dev install? on the host OS or a VM?
We tried hard to make the misc4dev tools agnostic of KTD. Feedback is
welcome.
El mar, 6 dic 2022 a las 9:17, Marcel de Rooy ()
escribió:
> > As said in the email I am planning to integrate them into our dev
> env (via
Hi all, I've (finally) restored jenkins notifications, and I plan to send
failure notifications to:
- Release maintainers
- QA team
Developers whose commits are suspected to have broken the tests will still
be notified.
I created two forwarding addresses to simplify notifications as well.
--
Hi all, just wanted to let you know that we solved a long standing issue in
KTD [1] that made it awkward to switch from using ES or not with KTD
(required tweaking the .env file and would break if things didn't match).
The `ktd` command now takes advantage of this enhancement so, as a
reminder,
You need to understand that you have dangling messages on your .
Old messages that have invalid JSON, and ids that were picked by the hybrid
fallback mechanism so fail (which I agree it's not cool)
Stop Koha, stop the worker, stop rabbit, clean rabbit, start the worker,
let it exhaust already
I recall we used the header at some point, to keep the base query clean
when adding new filters.
The only alternative is forcing the use of some form of ascii encoding
(base64?) But I agree we should better deprecate it.
It's use in the codebase on DT is tied to an option switch and probably not
El lun, 5 dic 2022 a las 14:24, Julian Maurice ()
escribió:
> Yes it is expensive. But manual testing is much more expensive. I'd
> rather pay for some CPU time than do manually what a bot can do better
> and faster than me. Free services exist too (CircleCI, github actions, ...)
>
When you
Yeah! This release will be dedicated to Rosalie.
Great call!
El vie, 18 nov 2022 12:19, Paul Poulain
escribió:
> Hi Chris,
>
> Sad news, let us know when the funerals are.
>
> @community : May I suggest that we name the next release "Koha 22.11
> Rosalie" ?
>
> Le 17/11/2022 à 08:09, Chris
unctionality into the main script though. ;)
>
> Once I've got myself back up to speed on the release process from an
> rmaint view I'll be more than happy to help refine it
>
> On Mon, 28 Nov 2022, 1:36 pm Tomas Cohen Arazi,
> wrote:
>
>> Hi all this is for rmaints mostly,
The Koha community is proud to announce the release of Koha 22.11.00.
Koha 22.11.00 is a major release, that comes with many new features.
It includes 13 new features, 351 enhancements, 3 security fixes, 551
bugfixes.
The full release notes are available here:
Hi all this is for rmaints mostly, I've just added a new 'tarball' option
to koha-release. Please review and comment if you'd prefer some other way
to do this.
Also, I think we should work on the release tools a bit so all parameters
are named and have option switches to simplify the code.
Hi all, time to git pull on your koha-testing-docker clone: we have just
added a docker-compose.sso.yml file that can be used for launching an IdP,
based on keycloak.
As usual, the `ktd` script options got a new `--sso` option switch for
enabling it. The keycloak server is running on port 8082.
Hi all, both ERM and the OIDC/OAuth2 integration have been pushed. As some
of you noted, they have new dependencies. New KTD images have been built
before pushing to avoid issues, so please do the usual so things keep
working:
$ ktd pull
Best regards
PS: If you use other ktd flags, you can also
Hi all, we pushed ERM but didn't communicate some decisions made:
- For running the ERM component (and in the future any other Vue-driven
thing) a build step needs to happen. Either:
$ yarn build_js
or (the dev-oriented version):
$ yarn watch_js
- We could've gone 'the SCSS' way, in which the
Thank you David for all your valuable input. Looking forward to those
follow-ups.
El mar, 8 nov 2022 a las 23:36, David Cook ()
escribió:
> I was pumped to see this morning that the OIDC client was pushed to master!
>
>
>
> I have 2 very easy follow-ups that I think are necessary before the
>
Hi, we've just pushed a change to Koha, moving away from node-sass to
dart-sass, and older docker images will fail as all assets are
automatically built on startup and it will fail otherwise.
Best regards
--
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F
Hi. The message you posted contains a command you're suggested to run to
get Apache properly configured.
But beware 22.11 on Ubuntu 18.04 is not officially supported.
El mié, 1 mar 2023 21:59, Christian Calle Jahuira
escribió:
> Hi all,
>
> I found the following detail when installing koha
gt; Suite 7.03
>
> 6a Glen St
>
> Milsons Point NSW 2061
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Online: 02 8005 0595
>
>
>
> *From:* Koha-devel *On
> Behalf Of *Tomas Cohen Arazi
> *Sent:* Wednesday, 26 April 2023 11:25 PM
> *T
Koha has been using the Swagger/OpenAPI plugin since... 2015.
The validation step is important, especially when there are API plugins.
Plugins can break the API, and we need to check that. I'd like to hear
opinions about that, though. And I am open to changing my mind.
Best regards
El mié, 26
There's a conversation going on on the bug, about how that change made the
build process a bit more complicated (i.e. more steps).
Kyle and I have been working on this:
https://gitlab.com/koha-community/koha-dpkg-docker#usage
which is a simple way to build packages, and considers that required
A new cycle is about to start. It is time for you all to put your names for
the next release.
Here: https://wiki.koha-community.org/wiki/Roles_for_23.11
Best regards
--
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F
Hi all :-D
I wanted to ask everyone contributing patches to Koha, that when you get
notified your patches have been pushed, at least two things need to happen:
- You get happy
- You keep an eye on the test suite [1]
You get happy because it means a lot of people reviewed your stuff, spent
time
Hi, the hackfest is over, we had great time!
I wanted to thank everyone supporting our open source work, and Biblibre
for making this opportunity to meet in person real.
Thanks!
--
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F
Hi all, we will be performing a maintenance task on the Git server during
the next hours.
--
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
The Koha::Objects query syntax is passed through. I guess you need to make
a regular join but call ->get_columns or smth.
El mar, 4 abr 2023 a las 9:07, Marcel de Rooy ()
escribió:
> Hi,
>
> Just a dumb question. But what is the best way to get a column from a
> joined table in the results of a
Excellent, thanks Jonathan.
El mar, 7 feb 2023 a las 10:31, Jonathan Druart (<
jonathan.dru...@bugs.koha-community.org>) escribió:
> Hi,
>
> We have a pre-commit hook in the wiki but people forget to install it. And
> it was not easy to update and propagate the changes. We decided to embed it
>
Hi all, community members have reported permissions issues breaking ktd
initialization when launching it fresh.
It's been narrowed down to be an issue with the Docker Desktop for Linux
product.
Please use the Docker Engine/server install instructions as pointed by the
readme.
Hi all, we've been talking for a while by different means (IRC, pm,
hackfests, etc) about the need to build a solid pipeline for our testing
infrastructure, package building and testing and also the docker images.
Several individuals have implemented different things over time, for
building the
Can't we just use Gitlab for now?
El mié, 1 feb 2023 a las 6:08, Jonathan Druart (<
jonathan.dru...@bugs.koha-community.org>) escribió:
> See https://codeberg.org/forgejo/forgejo and
> https://forgejo.org/2022-12-15-hello-forgejo/
> "To this end we are very proud that Codeberg e.V. has decided
601 - 700 of 732 matches
Mail list logo
