Debian Packages?

[proffalken]

Hi,

I see on the downloads page that RPM's are available, are there plans to make .deb packages available too?

[zuiderkwast]

Yes, there is an RFP (Request For Packaging) filed here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068342

@guillemj FYI

[guillemj]

BTW this then turned into an ITP (Intent To Package), and is now sitting in the NEW upload queue pending archive admin approval (https://ftp-master.debian.org/new/valkey_7.2.5+dfsg1-1.html and https://ftp-master.debian.org/new/valkey_7.2.5+dfsg1-2.html). Once it's approved it will get into unstable, a new source-only upload will be needed so that it can migrate to testing (binary uploads are not permitted to migrate to force all artifacts to be built from a known environment in the Debian build daemons), and then if no severe bugs are found, and the various QA tests pass, it will migrate to testing in a range from a couple of days to 5 days or so.

[zuiderkwast]

@guillemj the list of binaries looks like it's taken from an extremely old redis version. That's not the binaries we provide.

We have valkey-server, valkey-cli and valkey-benchmark, plus some symlinks to valkey-server with other names (valkey-sentinel, valkey-check-aof, etc.)

We have scripts to build man pages too now, in the repo valkey-doc. You can take any version since the docs are not versioned. (They describe all versions and mention when each thing was added.)

[guillemj]

I have not really reviewed the packaging, but I'd assume that's what it looked like in relase 7.2.5, and the packaging probably was adapted from the redis one.

Once this gets accepted into the archive, then I'd expect updates to start flowing more often, and for the maintainer to then update to the latest upstream release.

[proffalken]

Perfect, thanks.

[zuiderkwast]

We can leave it open for others to see, ok? I marked my answer as "accepted".

[proffalken]

Sure, sounds good!

[gesundes]

Can we have it in packages along with tar.gz?

[zuiderkwast]

We could, but IMO it's better that it's packaged by the Debian project, just like the RPMs are prvided by Fedora. The distros provide source and several binary packages for various hardware.

[zuiderkwast]

Otoh, if we build our own deb files, we could do it immediately on each new release. @roshkhatri wdyt?

[guillemj]

This could be problematic if people then end up switching between packages from Debian and upstream generates ones and vice-versa.

[maherbeg]

Is it possible to get this into debian bookworm-backports? That would make transitioning systems into debian-trixie a bit easier too!

[guillemj]

Perhaps the maintainers would be interested in preparing a backport, someone might need to ask them. :)

Otherwise some other Debian Developer could prep it, and take responsibility.

[maherbeg]

I'm happy to ask! I wasn't sure what the process here is between folks on Valkey and the packaging teams of the various distros. I didn't want to step on any toes or create additional maintenance burdens.