Your message dated Fri, 29 Sep 2023 11:49:10 +0100
with message-id <a06eff35-3393-5492-d753-b71b68d95...@debian.org>
and subject line re: rust-laurel, upcoming rust-bindgen update.
has caused the Debian Bug report #1051146,
regarding rust-laurel, upcoming rust-bindgen update.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1051146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rust-laurel
Version: 0.5.3-1
In the rust team we are working on upgrading rust-bindgen from 0.60 to
0.66, there are a few reasons for this. Firstly it's part of the
dependency stack
for the new version of rust-cargo. Secondly the version currently in sid
has a
compatibility issue with new versions of llvm. Thirdly Jonas has filed a
bug report
requesting the new upstream version.
bindgen bumps semver on most releases, however the changes tend to be
relatively minor. You can read the changelog at
https://github.com/rust-lang/rust-bindgen/blob/main/CHANGELOG.md#0610
but I don't see anything too scary in there.
The new version of rust-bindgen has been uploaded to experimental so people
can test against it. After bumping the dependencies your package built
successfully. Unfortunately your package doesn't seem to have any
autopkgtests.
The attatched debdiff, removes the upper limit from the bindgen dependency,
(similar to how you have already removed the upper limit from the nix
dependency)
given the history of the bindgen package I think this is a sensible way
forward
OTOH if you would preffer to simply bump the dependency when the new
bindgen is uploaded that would be fine too.
--- End Message ---
--- Begin Message ---
Version: 0.5.3-1.1
Fixed in 0.5.3-1.1
--- End Message ---
