Bug 2315609
| Summary: | A request for building rust-atomic0.5 on Fedora 41 and 42 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | wojnilowicz <lukasz.wojnilowicz> | ||||
| Component: | rust-atomic0.5 | Assignee: | Rust SIG <rust-sig> | ||||
| Status: | CLOSED ERRATA | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | decathorpe, rust-sig | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | rust-atomic0.5-0.5.3-2.fc41 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2024-10-09 00:16:39 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 2315472 | ||||||
| Attachments: |
|
||||||
|
Description
wojnilowicz
2024-09-30 06:56:32 UTC
I would really like not to have to add *back* compat packages that were already retired. Would it be possible to port this package to atomic v0.6? (In reply to Fabio Valentini from comment #1) > I would really like not to have to add *back* compat packages that were > already retired. > > Would it be possible to port this package to atomic v0.6? It's already done for rocket 0.6 as seen at https://github.com/rwf2/Rocket/blob/master/core/lib/Cargo.toml Actually nothing is seen because this crate would not be a dependency anymore. Rocket 0.6 is still unreleased though. I need rocket 0.5 for building ActivityWatch. Without it whole my work on the missing dependencies would be go for nothing. I could retire it myself if you wish. You can patch the dependency from 0.5 to 0.6 without needing to package a pre-release or waiting for a new release. It looks like the APIs between atomic 0.5 and 0.6 didn't change (much), so it should be as simple as patching rocket for bumping the atomic dependency 0.5 -> 0.6 when packaging it. Ok. I'll try to do that and come back with the results. Thanks for investigating. Created attachment 2049555 [details]
cannot_build_rocket_0.5_with_atomic_0.6.txt
I tried but failed (details in the attachment). I don't know rust, so I'm not sure how should I handle those errors.
Is it easily fixable? If not, then wouldn't it be easier just to unretire rust-atomic0.5?
Hm, that error does look strange. atomic v0.6 *does* implement the NoUninit trait from bytemuck ... I'll need to take a closer look later. It does look like using atomic 0.6 here won't be easy. I filed a request to unretire the atomic v0.5 compat package in f41 and f42: https://pagure.io/releng/issue/12375 FEDORA-2024-ec95e0a8df (rust-atomic0.5-0.5.3-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-ec95e0a8df FEDORA-2024-ec95e0a8df has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf install --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-ec95e0a8df \*` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-ec95e0a8df See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-ec95e0a8df (rust-atomic0.5-0.5.3-2.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. |