Bug#1053955: rust-toml: please update to v0.7.8
On 16/11/2023 18:41, Jonas Smedegaard wrote: Quoting Peter Green (2023-11-16 10:55:33) Please update to (at least) newer upstream release v0.7.8. toml itself is not semver-breaking, but it's closely coupled dependency toml_edit is. [...] My overall conclusion is that btm is the main blocker. Jonas, btm is one of your packages, can you work with upstream to prepare and test an update? Updated versions of toml_edit and toml are availble in experimental for you to test with. Please go ahead without waiting for btm: Upstream has swiftly responded with an uncomplicated change. Sorry I screwed up with my earlier analysis. I mixed up toml 0.7.8 with toml 0.8.8. Only the latter requires the new toml_edit. So it seems I won't be semver bumping toml_edit at this time after all.
Bug#1053955: rust-toml: please update to v0.7.8
Quoting Peter Green (2023-11-16 10:55:33) > > Please update to (at least) newer upstream release v0.7.8. > > toml itself is not semver-breaking, but it's closely coupled dependency > toml_edit is. [...] > My overall conclusion is that btm is the main blocker. Jonas, btm is one > of your packages, can you work with upstream to prepare and test an update? > > Updated versions of toml_edit and toml are availble in experimental for > you to test with. Please go ahead without waiting for btm: Upstream has swiftly responded with an uncomplicated change. Thanks for looking into this, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1053955: rust-toml: please update to v0.7.8
Please update to (at least) newer upstream release v0.7.8. toml itself is not semver-breaking, but it's closely coupled dependency toml_edit is. Relavent parts of the upstream changelog. 0.21.0 - 2023-11-06 Breaking Change Split default-features=false APIs into parse and display features 0.20.0 - 2023-09-13 Compatibility Serialization and deserialization of tuple variants has changed from being an array to being a table with the key being the variant name and the value being the array 0.20->0.21 looks low risk to me, but 0.19->0.20 looks potentially riskier. With that in mind lets look at the reverse dependencies. btm - still on 0.19 upstream. python-maturin - uses 0.21 upstream, did not make any code changes when bumping from 0.19 to 0.21, already broken and not in testing. rust-cargo - uses 0.20 upstream, did not make any code changes when bumping from 0.19 to 0.20 rust-rstest-test - uses 0.19 upstream, not in testing, no rdeps rust-trycmd - uses 0.20 upstream My overall conclusion is that btm is the main blocker. Jonas, btm is one of your packages, can you work with upstream to prepare and test an update? Updated versions of toml_edit and toml are availble in experimental for you to test with.
Bug#1053955: rust-toml: please update to v0.7.8
Source: rust-toml Version: 0.7.6-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please update to (at least) newer upstream release v0.7.8. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmUq7pAACgkQLHwxRsGg ASHnJA//cx9HiQ4IlI+FTTSwflG5yA+rME94OLZps1zrsep/s6VCZwlVB++jeYXv QwmkLkO96aVG4OjT2EnGu4ecfpMygvQX1XGlIPxb0XahqfbihmHLHblEA0Mkzl/z CtmknWGXzMUAP5DxcV2sP6vuEZZ3Dv6XmCd9lz5Ol4T+pmNvToxD1zLShckJIAxq arN6drzGIzPeX0+4LPiKoWZSZKANAK5+hdjbNc9zvwn37d0BAux2Fur5jvMNrGYk u1dGVcnyXndWz6NQp7Msvmgy8HiQp9TdXpu1UxN16wXGnVV2fKV/Lpw2FDtDjLPJ z/dRCxk7TyDCexAPuWaxaXGE0Rlsu1bLzrmVKPo/v9bqoHpRkUQJjsgWwLawOwVO D/OrJL3WrgLw5560IXVtWhvxE2iiAYs9v9q/5MqLnTsw4LG8mIJAJ1QiUb+l8p1e xs+6CCVUS5YJ1dMBwUptpddQJHDMc3OBbpcLB0fp2hzUBCEnehGiXo0Rfw9ITa8+ 9N40Lk7oXY0Xszt2B1Fer2+qYyaPqbnl50ItJq0FYZHcmWLvjEUUG0ZHBkKZRa43 0uABFMODPQ3Dduj7GJY6A5msd8mQ9N8EHSgugz8Y6cslRnaQ/t1jycmton3SoDJN BIQe0jCPqo6iFb30DlHW3ETcLWJSJJkegfFPeY/9L8/daRHACeg= =HRrJ -END PGP SIGNATURE-
