Hello there Otto, Le vendredi, 26 décembre 2025, 04.18:27 h Otto Kekäläinen a écrit : > What is the status with Typesense packaging? > > I see there are no commits at > https://salsa.debian.org/typesense-team/typesense/-/commits/debian/latest > since 2023, and last message in this bug report mentions upstream has > forked dependencies that are tricky to package.
I have basically given up and now rely on the Kubernetes Operator to deploy it when needed: https://github.com/akyriako/typesense-operator Back when I tried to package, I quickly realised that: - a) it was going to need a lot of build- and run-dependencies, many of which in technologies or languages that I'm not very familiar with - b) it's a fast-moving target: there were new dependencies needed when I looked again after some time. > Was there some feature requests for upstream to upstream their own > dependencies so no unnecessary forks are maintained long-term? I am > sure the Typesense team don't want to have too many dependencies to > fork/maintain permanently either. See https://github.com/typesense/typesense/issues/1050 : typesense uses the headers of an unreleased lru-cache repository, which doesn't build correctly (at least when I tried in 2023). Also, typesense moved from CMake to bazel as build-system, which is gone from Debian: https://lists.debian.org/debian-bazel/2023/02/msg00002.html So, I've given up, hence my rename from ITP to RFP and my disowning of the bugreport. Best, and a merry end of year, OdyX
signature.asc
Description: This is a digitally signed message part.
