Bug 1964664
| Summary: | F35FailsToInstall: rust-unsafe-io+async-std-devel | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Miro Hrončok <mhroncok> |
| Component: | rust-unsafe-io | Assignee: | Olivier Lemasle <o.lemasle> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | decathorpe, o.lemasle, rust-sig |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rust-unsafe-io-0.6.9-1.fc35 rust-unsafe-io-0.6.9-1.fc34 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-05-26 20:06:48 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: | 1927313 | ||
|
Description
Miro Hrončok
2021-05-25 19:30:10 UTC
Do you plan to drop the async-std feature, or do you want to keep it? I've been working on packaging async-std for a different project (deno) and I only still need to submit all the necessary package reviews ... @Fabio I'll drop the async-std feature, at least in a first time. But I'll be happy to review your package reviews to have async-std in repositories. Great! You can use this in the .rust2rpm.conf file for rust-unsafe-io: ``` [DEFAULT] unwanted-features = async-std ``` This will prevent the async-std subpackage from being generated when you run rust2rpm. These are the currently pending package reviews for packaging async-std: https://bugzilla.redhat.com/show_bug.cgi?id=1964685 https://bugzilla.redhat.com/show_bug.cgi?id=1964690 https://bugzilla.redhat.com/show_bug.cgi?id=1964694 I suspect there will be more, as those are only the default dependencies, and don't include optional dependencies. I have all packages prepared locally, but am only submitting the package reviews once all dependencies are ready in Fedora. Thanks for the .rust2rpm.conf tip! BTW, removing the "async-std" feature from the spec prevents building "rust-unsafe-io+async-std-devel", but does not remove the subpackage from repos. So does it really fix this issue? I've started reviewing your packages. FEDORA-2021-7f7701d24c has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-7f7701d24c FEDORA-2021-7f7701d24c has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. (In reply to Olivier Lemasle from comment #4) > Thanks for the .rust2rpm.conf tip! No problem! I added that feature to it a while back because it was a recurring problem in other packages too. This way there's usually no need to patch the feature out from Cargo.toml manually. > BTW, removing the "async-std" feature from the spec prevents building > "rust-unsafe-io+async-std-devel", but does not remove the subpackage from > repos. So does it really fix this issue? It should, because only the latest version of a package is kept in the repos, so as soon as the latest update is pushed, the old package that contains the subpackage is removed. > I've started reviewing your packages. Thank you! FEDORA-2021-4a8a019b1b has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4a8a019b1b FEDORA-2021-4a8a019b1b has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-4a8a019b1b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4a8a019b1b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-4a8a019b1b has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. |