Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1964664 - F35FailsToInstall: rust-unsafe-io+async-std-devel
Summary: F35FailsToInstall: rust-unsafe-io+async-std-devel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rust-unsafe-io
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Olivier Lemasle
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F35FailsToInstall, RAWHIDEFailsToInstall
TreeView+ depends on / blocked
 
Reported: 2021-05-25 19:30 UTC by Miro Hrončok
Modified: 2021-06-04 01:12 UTC (History)
3 users (show)

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:
Clone Of:
Environment:
Last Closed: 2021-05-26 20:06:48 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Miro Hrončok 2021-05-25 19:30:10 UTC 
Hello,

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok).

Your package (rust-unsafe-io) Fails To Install in Fedora 35:

can't install rust-unsafe-io+async-std-devel:
  - nothing provides (crate(async-std/default) >= 1.9.0 with crate(async-std/default) < 2.0.0~) needed by rust-unsafe-io+async-std-devel-0.6.8-1.fc35.noarch
  - nothing provides (crate(async-std/unstable) >= 1.9.0 with crate(async-std/unstable) < 2.0.0~) needed by rust-unsafe-io+async-std-devel-0.6.8-1.fc35.noarch
  
If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.


If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks.

P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors.

P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages

Thanks!
Comment 1 Fabio Valentini 2021-05-25 20:19:49 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 ...
Comment 2 Olivier Lemasle 2021-05-26 13:28:59 UTC 
@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.
Comment 3 Fabio Valentini 2021-05-26 13:36:36 UTC 
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.
Comment 4 Olivier Lemasle 2021-05-26 20:05:12 UTC 
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.
Comment 5 Fedora Update System 2021-05-26 20:06:32 UTC 
FEDORA-2021-7f7701d24c has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-7f7701d24c
Comment 6 Fedora Update System 2021-05-26 20:06:48 UTC 
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.
Comment 7 Fabio Valentini 2021-05-26 20:26:54 UTC 
(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!
Comment 8 Fedora Update System 2021-05-26 21:16:03 UTC 
FEDORA-2021-4a8a019b1b has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4a8a019b1b
Comment 9 Fedora Update System 2021-05-27 01:32:45 UTC 
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.
Comment 10 Fedora Update System 2021-06-04 01:12:48 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.