• Bug#1106760: redis-timeseries module is not available in debian

    From purification@ukr.net@21:1/5 to All on Thu May 29 14:50:01 2025
    Package: redis-server
    Version: 5:8.0.0-2

    According to the module description [0]:

    "Starting with Redis 8, the Time Series data structure is integral to
    Redis. You don't need to install this module separately."

    I have checked the redis official source code release [1] and it does
    contain said module.

    However when installing Redis 8 from the Debian repository, the
    timeseries functionality (various TS.* commands) is neither available
    out of the box, nor there is a .so module that could be configured by
    user to be loaded.

    [0] https://github.com/RedisTimeSeries/RedisTimeSeries
    [1] https://download.redis.io/redis-stable.tar.gz

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Lamb@21:1/5 to purification@ukr.net on Fri May 30 01:10:01 2025
    tags 1106760 + confirmed
    thanks

    purification@ukr.net wrote:

    "Starting with Redis 8, the Time Series data structure is integral to
    Redis. You don't need to install this module separately."

    I have checked the redis official source code release [1] and it does contain said module.

    I'm afraid that's not quite right. If you look a little more closely,
    you see that the Makefile under redis-stable/modules/redistimeseries
    is actually a placeholder that calls "git clone" or equivalent when
    you build with modules enabled.

    As you likely are aware, downloading source code from third-party
    sources is not permitted in Debian package builds.

    However when installing Redis 8 from the Debian repository, the
    timeseries functionality (various TS.* commands) is neither available
    out of the box, nor there is a .so module that could be configured by
    user to be loaded.

    Indeed. :( There are a number of solutions:

    1. Redis starts to bundle the actual source code for the "included"
    modules in its release tarballs. (I can understand them wanting to
    develop them in separate Git repositories.)

    2. We package these modules into separate Debian source packages and
    get them into Debian. e.g., redis-module-timeseries or something.

    Either way, due to the timing of Redis' relicensing and Debian's freeze,
    these modules will not ship with the version in trixie. (In addition,
    some of these modules require Rust and so forth, and other things that
    require a bit more work and time to get them shipped.) The functionality
    would likely be available via backports, however.


    Regards,

    --
    ,''`.
    : :' : Chris Lamb
    `. `'` lamby@debian.org 🍥 chris-lamb.co.uk
    `-

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adrian Bunk@21:1/5 to Chris Lamb on Sat May 31 16:00:01 2025
    On Thu, May 29, 2025 at 03:52:45PM -0700, Chris Lamb wrote:
    tags 1106760 + confirmed
    thanks

    purification@ukr.net wrote:

    "Starting with Redis 8, the Time Series data structure is integral to Redis. You don't need to install this module separately."

    I have checked the redis official source code release [1] and it does contain said module.

    I'm afraid that's not quite right. If you look a little more closely,
    you see that the Makefile under redis-stable/modules/redistimeseries
    is actually a placeholder that calls "git clone" or equivalent when
    you build with modules enabled.

    As you likely are aware, downloading source code from third-party
    sources is not permitted in Debian package builds.

    However when installing Redis 8 from the Debian repository, the
    timeseries functionality (various TS.* commands) is neither available
    out of the box, nor there is a .so module that could be configured by
    user to be loaded.

    Indeed. :( There are a number of solutions:

    1. Redis starts to bundle the actual source code for the "included"
    modules in its release tarballs. (I can understand them wanting to
    develop them in separate Git repositories.)

    2. We package these modules into separate Debian source packages and
    get them into Debian. e.g., redis-module-timeseries or something.
    ...

    3. A Debian package can have multiple source tarballs, this would be the
    normal solution.

    Regards,

    cu
    Adrian

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)