I have the automated builds setup for my snap, but it seems like the build is not respecting the Cargo.lock file for my project because it is updating dependencies that I have not told it to.
I am using a release of a crate that is one version older than the latest available release and my project will not compile with the latest one. When I compile locally or on my other automated builds Cargo will use the versions of the packages that are specified in the Cargo.lock file until I explicitly run cargo update to update the lock file.
Here is the build log from the Snapcraft CI server:
Here is the build log from my CI build:
Here is the commit from my project:
The snapcraft build updating the termimad crate from 0.8.4 to 0.8.5.
This is still happening for me and is breaking my snap builds whenever somebody updates a certain library I depend on because snapcraft isn’t respecting my Cargo.lock.
Is there somewhere I should create a bug for this?
You can file bugs for snapcraft at http://bugs.launchpad.net/snapcraft. I noticed this post is not in the snapcraft category and was originally made during holidays where folks may have missed it. Perhaps they will see it now, but regardless I recommend filing a snapcraft bug for this.
Once it’s done building, it should be available to install with:
snap refresh snapcraft --channel edge/pr-2915
It would be awesome if you could give it a test run on your project!
FWIW I’m not really experienced with Rust, so if you have any thoughts on further improving the rust plugin, or this PR specifically, please let us know!
