-
Notifications
You must be signed in to change notification settings - Fork 149
Update to nix-0.28 #176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Update to nix-0.28 #176
Conversation
While at it, use std::os::fd::owned::OwnedFd instead of custom implementation.
eldruin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your work!
Could you look into the CI failures?
Also, could you add an entry to the changelog about this?
|
Hi. This looks like a MSRV issue. |
|
Hmm, this does not seem MSRV-related to me, though. Here is a run with 1.76.0: The MSRV is set to 1.59.0, where have you found the 1.36.0 reference? |
|
You're right. I was looking at the first issues like here: https://github.com/serialport/serialport-rs/actions/runs/8535157043/job/23396025571?pr=176#step:7:32. |
Both variants provide a direct conversion from Duration, so there is no need for us to deal with converting the timeout and signedness.
No, this looks like an issue with the signedness of Ended up with bf7050c while looking into this. So there is just raising the MSRV left.
At a first glance at least when it comes to the Rust support shipped with Yocto. Dependents using older Yocto releases could still pin their dependency on us to a minor version and we could attempt to scan all publicly visible dependencies. And on the other hand there is also meta-rust-bin which provides the brand spanking new releases of Rust. Let me think and sleep over it. |
|
Did you have time to think about this @sirhcel ? |
|
I finally managed to. Just to get my perspective on this right: Is bumping our nix dependency tied to switching to I'm fine with switching to When it comes to bumping nix, I would postpone this to the next major release as this could be a breaking change for dependents still relying on our MSRV being 1.59.0. I know this is subject to general discussion but we've got our MSRV for dev builds broken recently with our dependencies |
|
I think that changes regarding the used file descriptor objects are necessary and that the custom implementation is no longer needed. |
|
Given the adoption of |
|
Hi folks, what's the latest on this effort? I'm attempting to pull this into a project that's locked-in on Is there anything I can do to help move this forward? |
|
I'm packaging serialport for Debian which ships It would be nice to see support for more recent |
|
I've made a new attempt at the |
https://crates.io/crates/serialport/4.7.0 Request Document: go/android-rust-importing-crates For CL Reviewers: go/android3p#cl-review Notes: 1. Upstream includes the short "Source Code Form" of the MPL 2.0 license text. But ComplianceLint wants the full text. So this includes a patch to include the full license text. 2. This includes patches which update serialport to support nix 0.28. The original patches come from this GitHub PR: serialport/serialport-rs#176 The specific commits are: * serialport/serialport-rs@2d859aa * serialport/serialport-rs@bf7050c Additional changes were made to accomodate upstream changes since the base of that PR. 3. cargo_embargo.json specifies libunescaper in the dep_blocklist because it is not actually needed, given that we aren't using udev: serialport/serialport-rs#247 4. Tests cannot be enabled due to numerous missing dependencies (see dev-dependencies in Cargo.toml). Bug: 398963123 Test: m libserialport Test: cargo build --no-default-features Change-Id: Iec8b421d732431b0321e16d2e94426eb3cbbe995
While at it, use std::os::fd::owned::OwnedFd instead of custom implementation.
Fixes #175