package: rust-abnf-core x-debbugs-cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Recently Matthias and dkg updated the rust-nom package to version 8, and introduced a rust-nom-7 package. Unfortunately, the version of rust-abnf-core in testing is not compatible with this because it's cargo dependencies are on nom 7 but it's Debian dependencies are on librust-nom-dev rather than librust-nom-7-dev. Soon afterwards, Jonas uploaded a rust-abnf-core package which included a patch to build with nom 8. However there were two problems with this upload. 1. It does not have a dependency on the new rust-nom, so it's tests fail in testing migration tests. 2. Even in a sid environment, it breaks builds of rust-abnf, and rust-imap-codec because abnf-core and abnf build against different versions of nom. I see two possible ways forward. The first option is to disable 1001_nom.patch in rust-abnf-core and have rust-abnf-core (build-)depend on librust-nom-7-dev. This would solve the immediate problem and allow rust-nom and rust-nom-7 to migrate to testing, as well as allowing us to fix python-pycddl for the ongoing pyo3 transition, but it would leave rust-abnf-core depending on an old version of nom. The second option would be to prepare patches for rust-abnf and rust-imap-codec to use the new version of nom and then add sufficient versioned dependencies and breaks so that britney knows it should migrate rust-abnf-core, rust-abnf and rust-imap-codec to testing together. I have determined that updating rust-abnf for the new version of nom is not a simple matter of bumping the dependency, but I have not dug deeper than that.
