I'm just using Redis on a small scale to enable caching for Nextcloud instances.
Instances are on Debian 11 servers, Nextcloud 26 or 27. My redis.list contains:
deb [signed-by=/usr/share/keyrings/redis-archive-keyring.gpg] https://packages.redis.io/deb bullseye main
Which does contain the fact that server is Debian 11 (Bullseye).
Yesterday I did a server update/upgrade and Redis was upgraded up to 7.2 which is not Debian 11 compatible, this broke Nextcloud ... I discovered that it was previously updated to 7.0, package exists in the Debian backport repo which I don't use, but this allowed Redis and Nextcloud to keep on functionning even though it is not an official Debian package.
I uninstalled Redis 7.2, et reinstalled using the Debian repo which gave me a Redis 6.0 and allowed me to restart my Nextcloud.
My question is about redis.list: is it normal that redis.list did allow for a 7.0 and then a 7.2 upgrade even though redis.list knows that the OS is Bullseye which is not compatible ? that seems quite dangerous so I'm wondering if I did something wrong or if this is a bug ?
Pierre.
