The thing is we don't have a spec for each endpoint as we do for the API.
So people could be tricked to send a GET with a similar form, to an
endpoint (the .pl script) and bypass the generic CSRF check we do.
Also, this ways programmers and the QA team have a simpler way to detect
state-changing
Hi everyone, we just identified an error on last week's releases and are
publishing a quick update.
Packages are generally available with the patched versions and should be
applied. Source tarballs are a bit delayed but will be published as well.
Thanks to all involved
--
Tomás Cohen Arazi
te.
> > So maybe better create a dedicated route with only PUT.
> > Like the one for privacy :
> > /public/patrons/{patron_id}/guarantors/can_see_charges
> >
> > We should add some text to wiki :
> > https://wiki.koha-community.org/wiki/Koha_REST_API_Users_Guide
> >
&g
When we decided to implement the RESTful API, we agreed PUT is for
'replacing' resources, and PATCH for updating selected pieces of them.
I personally never managed to wrap my mind around PATCH and how to validate
what tiny bit is allowed to be patched or not. As OpenAPIv2 is not that
flexible.
Congrats team!
El vie, 1 mar 2024 a las 10:26, Nick Clemens via Koha-devel (<
koha-devel@lists.koha-community.org>) escribió:
> Hello all!
>
> We have pushed the CSRF work from 34478 and related bugs today. We know
> there are more follow-ups needed, and have filed a series of bugs under an
>
That's interesting! I've seen such situation on stuck STOMP messages, so I
guess we are breaking userenv somewhere!
El lun, 12 feb 2024 a las 21:36, David Cook via Koha-devel (<
koha-devel@lists.koha-community.org>) escribió:
> Hi all,
>
>
>
> The last two days I’ve noticed that my session is
I think it's related to having Cypress bundled. And maybe some mistake on
package cache cleanup.
El dom, 4 feb 2024 a las 19:30, David Cook via Koha-devel (<
koha-devel@lists.koha-community.org>) escribió:
> Hi all,
>
>
>
> I’ve noticed recently that koha/koha-testing:master has been steadily
>
Great, Frederic!
El mar, 2 ene 2024 a las 9:59, Frédéric Demians via Koha-devel (<
koha-devel@lists.koha-community.org>) escribió:
> Hello everyone,
> and best wishes for the New Year,
>
> The Koha community is proud to announce the release
> of Koha 22.11.13:
>
Yay!
El mar, 2 ene 2024 a las 7:37, Fridolin SOMERS via Koha-devel (<
koha-devel@lists.koha-community.org>) escribió:
> Hello everyone 珞
>
> The Koha community is proud to announce the release of Koha 23.11.01.
>
> It is a bugfix/maintenance release including 25 bugfixes.
>
> The full release
That'd be 13 UTC.
El mar, 12 dic 2023 a las 9:10, Marcel de Rooy via Koha-devel (<
koha-devel@lists.koha-community.org>) escribió:
> How late btw?
> --
> *Van:* Koha-devel namens
> Fischer, Katrin via Koha-devel
> *Verzonden:* dinsdag 12 december 2023 10:10
> *Aan:*
Yes, I know what you want to say
>
> Marcel
>
> --
> *Van:* Marcel de Rooy
> *Verzonden:* dinsdag 5 december 2023 16:55
> *Aan:* Marcel de Rooy
> *Onderwerp:* Fwd: [Koha] Koha 23.11 released
>
>
>
> ------ Forwarded message -
dru...@bugs.koha-community.org>) escribió:
> But it won't embed po files.
> Please see my reply to Victor.
>
> Le vendredi 10 novembre 2023, Tomas Cohen Arazi a
> écrit :
> > Gitlab allows you to download a tar.gz, and commits are GPG signed
> already.
> > Maybe we can chan
Gitlab allows you to download a tar.gz, and commits are GPG signed already.
Maybe we can change the workflow. We should take some time to think about
it next cycle.
El mar, 7 nov 2023 a las 17:22, Jonathan Druart via Koha-devel (<
koha-devel@lists.koha-community.org>) escribió:
> Hi,
>
> I am
plan.
>> Communication is good.
>>
>>
>>
>> Timezones, especially mine, make it tough, but being able to point at
>> documentation for policies and procedures is helpful.
>>
>>
>>
>> David Cook
>>
>> Senior Software Engineer
Hi all, this is master's latest failures:
https://jenkins.koha-community.org/job/Koha_Master/lastCompletedBuild/testReport/
The selenium failure has been there for a while, and the other ones are
recent.
El jue, 2 nov 2023 a las 10:30, Tomas Cohen Arazi ()
escribió:
> Hi all.
>
> We a
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 *On
> Behalf
Hi all.
We are almost done with the release, a couple medium/big things to push
today/tomorrow and then bug fixing.
I wanted to ask y'all to please view the Jenkins tasks status anytime after
your stuff has been pushed. I know I said this many times, but some devs
clearly break some tests that
Hi all,
This are the release dates:
* Oct 30th - "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 5 - "Hard" feature freeze, nothing considered as an improvement will
be pushed if not marked as Passed QA
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
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
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
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, 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
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, 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
The Koha community is proud to announce the latest releases of the current
stable, oldstable, oldoldstable and lts versions of the software.
This is a security and maintenance release on all branches, so please update
at the earliest opportunity.
As always, you can update using the already
Hi all. I've been trying to push as much as I can from the PQA queue, and
I'm finding that most of the patches haven't been tidied up yet or have
trivially caught issues (maybe not most, but a lot).
For example, this is what I find when I run an up to date KTD and the code
is not tidy:
```
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
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]
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
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 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
mber 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.blo...@inlibro.com
> inLibro | pour esprit libre | www.inLi
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
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/
David, that's correct, you should use the query parameter in that case. We
really added the possibility of passing the query in the request body
because we were looking for examples and that's what ES does. But it is not
used in Koha, internally.
El vie, 12 may 2023 a las 3:58, David Cook ()
Hi all, we are a bit past the release dates. Time flied :-D
This are the release dates
* May 10th - "Hard" feature freeze, nothing considered as an improvement
will be pushed if not marked as Passed QA
* May 17th - String freeze, draft of release notes published
* May 24th - Only bug fixes
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
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
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
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
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
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. 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
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 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
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, there's been chatter and work about this subject in the last weeks.
This is something we postponed until after the 22.11 release, which
includes Vue files and forced us to rethink our build pipeline.
Today we've done two important things you need to be aware of:
* Compiled CSS and JS
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
>
aining a 16G 8cores server resources (I just put
> random numbers here)
>
> Le mer. 1 févr. 2023 à 14:51, Tomas Cohen Arazi a
> écrit :
>
>> Can't we just use Gitlab for now?
>>
>> El mié, 1 feb 2023 a las 6:08, Jonathan Druart (<
>> jonathan.dru..
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
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'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
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
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
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,
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:
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
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,
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.
--
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
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
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
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,
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,
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.
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:
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
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 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
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, 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.
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
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":
>
> #
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
:-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:
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.
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'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
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
>
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
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
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
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
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
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
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
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
> ___
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
>
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
+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
>
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
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
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
>> ("
1 - 100 of 731 matches
Mail list logo
