#1150138 rust-if-watch: Update for netlink-packet-core 0.9

#1150138#5
Date:
2026-10-05 21:07:17 UTC
From:
To:
Dear Maintainer,

as part of transition of netlink-packet-core to v0.9.0

rust-if-watch would also need to be updated at the

same time. Work on netlink-packet-core is tracked at:

https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/1352

I've created a patch in advance here:

https://salsa.debian.org/cen/rust-if-watch/-/commit/a4521b65558e3dd80df91b2105c7acb20d18d4e1

If you would consider enabling MRs on salsa I can also

open a pull request there.


Best regards, Klemen

#1150138#10
Date:
2026-10-22 07:35:26 UTC
From:
To:
Hi Klemen,

Quoting cen (2026-10-05 23:07:17)

Thanks for reporting this, and for investigating closer and preparing a
patch.

I don't use pull requests. What would be helpful to my workflow is if
you could share the patch here (or, if the patch only involves
relaxing version numbers in Cargo.toml files then simply say so).

It would also be helpful that you provided the newer crate in
experimental to allow test-compiling against it, and that you mention
whether your proposed patch have been tested against that experimental
package. Or if you have investigated upstream code changes and judge it
unnecessary to create and test against an experimental package, then
say so.

None of that is mandatory, but helps for a smoother collaboration :-)

Kind regards,

 - Jonas

#1150138#15
Date:
2026-10-22 07:35:26 UTC
From:
To:
Hi Klemen,

Quoting cen (2026-10-05 23:07:17)

Thanks for reporting this, and for investigating closer and preparing a
patch.

I don't use pull requests. What would be helpful to my workflow is if
you could share the patch here (or, if the patch only involves
relaxing version numbers in Cargo.toml files then simply say so).

It would also be helpful that you provided the newer crate in
experimental to allow test-compiling against it, and that you mention
whether your proposed patch have been tested against that experimental
package. Or if you have investigated upstream code changes and judge it
unnecessary to create and test against an experimental package, then
say so.

None of that is mandatory, but helps for a smoother collaboration :-)

Kind regards,

 - Jonas