On Sat, Jun 15, 2024 at 10:50:17AM +0200, Étienne Mollier wrote: > > Historically it was pretty important to dask and dask.distributed to be > > released together, upstream intends them to be matching versions, but I > > didn't know how to set the the dependnecy version strings to require > > that. > > It makes sense. The construction pretty much looks like the > latter is supposed to be a Python submodule of the former.
You could do something like this in the dask.distributed source package: Source: dask.distributed Build-Depends: python3-dask (>> 2024.5.2), python3-dask (<< 2024.5.3~) and in the binary python3-dask.distributed package similarly: Depends: python3-dask (>> 2024.5.2), python3-dask (<< 2024.5.3~) This forces the dask version to match the dask.distributed version. I don't know how tight the version numbers need to be, but this works to keep the packages in step with each other, and will prevent an updated dask package from migrating if the dask.distributed package has not been updated in parallel. Probably more effective than adding something to README.source (though that will certainly help a bit). Best wishes, Julian
