Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: =?utf-8?Q?=C3=89tienne?= Mollier Newsgroups: linux.debian.maint.python Subject: Re: newer dask release Date: Sun, 16 Jun 2024 23:00:01 +0200 Message-ID: References: X-Original-To: Julian Gilbey X-Mailbox-Line: From debian-python-request@lists.debian.org Sun Jun 16 20:54:36 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-114.52 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="kB3COxwUVMvTTBf3" Content-Disposition: inline X-Debian-User: emollier X-Mailing-List: archive/latest/21976 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/Zm9Q_J3fN1qUoxBQ@fusion.emlwks999.eu Approved: robomod@news.nic.it Lines: 71 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Sun, 16 Jun 2024 22:54:20 +0200 X-Original-Message-ID: X-Original-References: <4074f18a7e9cefde7200a90ebdc8315608062491.camel@ghic.org> Xref: csiph.com linux.debian.maint.python:15941 --kB3COxwUVMvTTBf3 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Julian, Julian Gilbey, on 2024-06-16: > On Sat, Jun 15, 2024 at 10:50:17AM +0200, =C3=89tienne 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. > >=20 > > It makes sense. The construction pretty much looks like the > > latter is supposed to be a Python submodule of the former. >=20 > You could do something like this in the dask.distributed source > package: >=20 > Source: dask.distributed > Build-Depends: python3-dask (>> 2024.5.2), python3-dask (<< 2024.5.3~) >=20 > and in the binary python3-dask.distributed package similarly: >=20 > Depends: python3-dask (>> 2024.5.2), python3-dask (<< 2024.5.3~) >=20 > 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). Thanks for the hint! I was not initially happy with the manual setting of the version, at least for the build dependency, but thinking a second time about this, it would prompt upload attempts for newer upstream versions to lookup dask as well as dask.distributed. So all in all, this is a fair plan. Have a nice day, :) --=20 .''`. =C3=89tienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/2, please excuse my verbosity `- on air: Refugee - Grand Canyon: The Source/Theme for t=E2=80=A6 --kB3COxwUVMvTTBf3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmZvUPwACgkQeTz2fo8N EdqUaRAAvGNsGYPgA9DbwLjaEMSy2g0EaDOgoGSjdqGrTrqqCjTCErc1yH8+AnnM TT/XPBYgRuebmF2NoU8u2Bdhf0u9KHQ+VF4dJiQelMeOjWFN5dOI4qq86iOpySiW ym4AxwhqR6O/RZDfy+dO92EVF2ci/DfrE7Ro/koYR3Cmtfuo46yK9S7uMg3WNVSr ILc3/bogZBUXDZE0xuBGCk7hEmJMJ++Dq77GrgUdZbehug2yDOS/x32/kEyevk4k H8jKgUO4omcn4FADA3CKtDOqbLs4hhyJWgv/VK5c8PV/6ykj82bsFDV/yE7nEJGS ASmgAsFOp1+S/rUJCdnqtkSOxBgKpEAJ1qF1Ywkiz117FcaS5qFPtylKg59nfKvR KYhQHVoXrRPTcP463LZS79qfPQkogxQ5BPI9G22tPt8+K10aP8utxPHhTpZQdKvK ZyMbRXHMkHivg5VWAXTURPR4wFqO4GZ65eu9DRdpbPxJeieLyy+Gvm1LdGyPHEVr eijEFTH8XaRpOHCLNPt4aApQFI9bEFR0aRozikmPKERKy5sO2dCk1y5nNHA7ssoX OV7bd3REZ3EIh3ADP4oN4qody0ZoVtn47InsUxZ1bQpK3fS95g7Cvuvh5cUGnxmo ldkTzjbl/df4FtfXDDK1BfryiB+cgRux0jEClZjk1A2OjPV3qSY= =IjiW -----END PGP SIGNATURE----- --kB3COxwUVMvTTBf3--