- Koha-devel - lists.koha-community.org

Bootstrap 4 upgrade for the OPAC
by Owen Leonard 05 Jun '20

05 Jun '20

Hi all, I've been working on a Bootstrap 4 upgrade to the OPAC (Bug 20168, https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20168) My work in progress is here: https://gitlab.com/koha-dev/koha-dev/-/tree/wip-2020-05-14-opac-bootstrap-4 One of the differences between this version and master is that Bootstrap assets will be added by npm and the OPAC's SCSS files built using those. This seems to make more sense than adding the entire Bootstrap library to our repo and building from there. I think the same should probably be done for jQuery and jQueryUI. I'm curious if anyone has comments on that. Thanks, Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org

3 4

Replace some koha-* scripts that use "daemon" with systemd unit files
by dcook＠prosentient.com.au 05 Jun '20

05 Jun '20

Hi all, What do people think about replacing some of the koha-* script files with systemd unit files? I'm creating a service for a RabbitMQ-based task scheduler and my unit file is 17 declarative configuration lines. Creating a koha-mq-scheduler file looks like it'll be hundreds of lines of shell script code. My unit file is actually a "template" file, which means I have 1 file in /etc/systemd/system/koha-mq-scheduler@.service and I can just invoke "systemctl start koha-mq-scheduler(a)INSTANCE.service" to start the service. You can use the %i placeholder in the unit file and it will be replaced with INSTANCE, so you can set paths, environmental variables, et cetera very easily. It's so easy and convenient. I think all modern Linux OSes use systemd for their init system, so I think it would be pretty safe to use. I'm happy to work on this one, but I guess I'd like to see if other people have interest in this. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

3 4

Fwd: Repack git repo
by Liz Rea 04 Jun '20

04 Jun '20

Hi all, As the release is now done, yesterday ~3pm Central Standard Time I ran a repack on the Koha repo. The repo is now 1.03G in size, down from 4.6G. There is more work to be done on that server - namely it's got a old and busted (and cantankerous!) OS, and thusly an old and busted (and cantankerous!) git version. It will need an upgrade at least, and it may end up being a server move. I don't have a timeline for any of that, but will aim to make it as unimpactful as I can when it happens, and will let everybody know closer to the time. Cheers, Liz On Tue, Apr 28, 2020 at 4:57 PM Jonathan Druart < jonathan.druart(a)bugs.koha-community.org> wrote: > The wiki page is outdated, I will try and update it soon. I managed to > get rid of po files and l kept the history and tags (using BFG instead > of git filter-branch). > > Le mar. 28 avr. 2020 à 20:02, Mark Tompsett <mtompset(a)hotmail.com> a > écrit : > > > > Greetings, > > > > I checked out the wiki page. Thank you for typing that up, Jonathan. > > > > I vote for keeping tags (hey GB to MB -- we can keep tags), and I really > like: > > > https://wiki.koha-community.org/wiki/Git_Splitting_and_Shrinking#Howto_use_… > > > > It's still pretty clean in terms of getting all of Koha. > > > > GPML, > > Mark Tompsett > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel(a)lists.koha-community.org > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ >

3 2

Koha Community Newsletter: May 2020
by Koha Newsletter 30 May '20

30 May '20

The Koha Community Newsletter for May 2020 is here: https://koha-community.org/koha-community-newsletter-may-2020/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Alerting users to breaking changes / backwards incompatibility
by dcook＠prosentient.com.au 29 May '20

29 May '20

Hi all, I was just thinking how a lot of SQL reports will return unexpected results when we merge the deleted* tables with their live/active counterparts. What do people think about a modal popup in the reports (on a per user basis) alerting them to how they may need to update their reports following an upgrade which changes reporting behaviour? I'm not 100% sure how we'd do it, but it's something we could re-use through much of the Koha staff client. Or maybe we could raise a flag in the borrower row during an upgrade, and when they log into the staff client, they're presented with a "You need to know." kind of page. After all, users aren't going to be reading release notes, and sysadmins doing upgrades aren't necessarily going to do the best job communicating to every single staff user about what they need to know in an upgrade. But that's easier said than done too, especially when you're upgrading past multiple versions. Anyway, just putting it out there. As you can see, I haven't thought about it too deeply yet. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

3 5

Bad koha-common.postinst in 19.11.05
by dcook＠prosentient.com.au 28 May '20

28 May '20

Hi all, Anyone else getting this in their 19.11.05 upgrade output: /var/lib/dpkg/info/koha-common.postinst: 155: [: !log4perl_component: unexpected operator Looks like a little typo David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

4 3

20.05.00 Alpha release
by Renvoize, Martin 22 May '20

22 May '20

Hi all, As we've got a number of improvements in the translations and packaging processes in this release I have built an alpha to test prior to a full release in the coming days. If you have time to work through any test upgrades/installs using the nightly Debian repository it would be greatly appreciated to get your feedback. The repository is available at http://apt.kohaaloha.com/koha-nightly/. Things to look out for: * Debian 10 Support! * Installer process and translations of default data * Circulation rules being added correctly during onboarding * Logging and log file permissions Any feedback given over the next few days will be taken into consideration before I build the release notes and officially release to the wider world. Many thanks, *Martin Renvoize* <https://www.ptfs-europe.com> Development Team Manager Community Release Manager (19.11, 20.05) *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize(a)ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

2 2

Plugin Security, Plugin Repositories, etc
by dcook＠prosentient.com.au 22 May '20

22 May '20

Hi all, I was doing my morning reading, and noticed that Microsoft have a Windows Package Manager in the works (https://www.theverge.com/2020/5/20/21264739/microsoft-windows-package-manag er-preview-download). While that might not be newsworthy for many people interested in FOSS, you might reconsider when you look at what they're doing for a community metadata repository: https://github.com/microsoft/winget-pkgs Here's an example of a metadata file for 7-zip in that repository: https://github.com/microsoft/winget-pkgs/blob/master/manifests/7Zip/7Zip/19. 0.0.yaml. It includes a URL to the installer and a SHA256 hash for integrity checking. Now according to https://github.com/microsoft/winget-cli, it doesn't look like they're using that Github repository as *the* metadata source repository. Indeed after a bit of digging it appears that the actual default metadata source is https://winget.azureedge.net/cache/source.msix, which contains a SQLite database of metadata (index.db). I think that's an interesting model. We could use http://gitlab.com/koha-community/plugins like https://github.com/microsoft/winget-pkgs where people could submit pull requests to get plugin metadata added to the repository. That would enable there to be a basic level of curation. We could then use something like https://plugins.koha-community.org/ to serve actual metadata (in whatever standardish format we want) to either the Koha web UI (and a Debian package Koha CLI tool like "koha-plugin-get" which make plugin deployment and maintenance potentially easier for sysadmins). There could be an automated process for updating plugins.koha-community.org from http://gitlab.com/koha-community/plugins too. People would be free to point to other plugin metadata repositories (e.g. vendor-specific repos), but by default it would be set up for the Koha Community plugin metadata repository. In terms of security, we could mimic Debian's Apt model of signing the plugin metadata manifest. That way, when setting up a plugin metadata repository in Koha, all you need to do is import a public key/cert to get trusted access to the repo. With the Koha Community repository, we could bake that public key/cert into Koha releases, so it would be seamless for end users. The hardest part of this process would be settling on what metadata manifest format to use for https://plugins.koha-community.org/. Actually, the hardest part would be trying to maintain some kind of backward compatibility. Maybe that's best done by rebranding the current plugin model as "Legacy Plugins" or "Manual Plugins" and then just building a separate web UI for the Repository model. We could re-use the same internals. We could also have separate controls for enabling/disabling "Manual Plugins" vs "Repository Plugins", so that vendors could provide access to plugins via a repository but prevent people from uploading random plugins from the Internet. Anyway, food for thought. I'm happy to do a lot of this work (probably in my personal time rather than work time), but I'd want to make sure there is some buy-in from other vendors and Koha plugin creators first. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Koha release 19.11.06
by Joy Nelson 22 May '20

22 May '20

Greetings! The Koha community is proud to announce the release of Koha 19.11.06. It includes 23 enhancements and 122 bug fixes. The full release notes are available at https://koha-community.org/koha-19-11-06-release/ Debian packages will be updated within a few days. -- Joy Nelson President, Koha Division ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>

1 0

Debian packaging problems for master and 19.11
by dcook＠prosentient.com.au 18 May '20

18 May '20

Hi all, You may or may not have noticed, but there are a few outstanding bugs for the Debian packaging for master and 19.11. I've contributed patches to all of them, so I can't really move them forward, but it would be great if other folk could take a look at these ASAP. I know packaging bugs are tough to test. I've spent almost a whole day writing code and testing. But here are some options: https://wiki.koha-community.org/wiki/Building_Debian_Packages_-_The_Easy_Way https://hub.docker.com/r/koha/koha-dpkg https://gitlab.com/minusdavid/koha-deb-builder-docker Bugs: master: Bug 25068 - koha-common build error caused by missing /etc/searchengine https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25068 19.11 (and possibly older versions although I haven't checked): Bug 25485 - TinyMCE broken in Debian package installs https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25485 Bug 25510 - Typo in koha-common.postinst causing shell errors https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25510 Bug 25524 - Debian packages always append to /etc/koha/sites/$site/log4perl.conf https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25524 Cheers, David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0