Spec URL: https://salimma.fedorapeople.org/specs/rust-blazesym.spec SRPM URL: https://salimma.fedorapeople.org/specs/rust-blazesym-0.2.0~rc.0-1.fc41.src.rpm Description: Blazesym is a library for address symbolization and related tasks. Fedora Account System Username: salimma
> %package -n %{name}+nightly-devel Do you actually want/need the nightly feature?
Koji scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=121261957
(In reply to Davide Cavalca from comment #1) > > %package -n %{name}+nightly-devel > > Do you actually want/need the nightly feature? oh good point, I'll strip it out
Dropped. Also, rust2rpm.toml: ❯ cat rust2rpm.toml [package] cargo-toml-patch-comments = [ "bump addr2line from =0.23.0 to 0.24.0", "bump gimli from 0.30 to 0.31", "drop unpackaged dump_syms dev-dependency", "drop unneeded reqwest, xz2, zip", "clean up dependencies of generate-* features", "drop nightly feature from stats_alloc", ] [features] # generate-*-test-files depend on unpackaged dump_syms hide = [ "dont-generate-unit-test-files", "generate-unit-test-files", "generate-large-test-files", "nightly", ] [tests] run = ["none"] comments = ["tests require unpackaged dump_syms"]
Consider packaging dump_syms so we can get the test suite running. Package was generated with rust2rpm, simplifying the review. - package builds and installs without errors on rawhide - latest version of the crate is packaged - license matches upstream specification and is acceptable for Fedora - license file is included with %license in %files - package complies with Rust Packaging Guidelines Package APPROVED.
The Pagure repository was created at https://src.fedoraproject.org/rpms/rust-blazesym
FEDORA-2024-e670dce831 (rust-blazesym-0.2.0~rc.0-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-e670dce831
FEDORA-2024-e670dce831 (rust-blazesym-0.2.0~rc.0-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2024-d61fbc8e7c (rust-blazesym-0.2.0~rc.0-1.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-d61fbc8e7c
FEDORA-2024-fa027b306e (rust-blazesym-0.2.0~rc.0-1.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-fa027b306e
FEDORA-2024-98919545ca has been pushed to the Fedora 40 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-98919545ca \*` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-98919545ca See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-fa027b306e has been pushed to the Fedora 39 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-fa027b306e \*` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-fa027b306e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-d61fbc8e7c has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-d61fbc8e7c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-d61fbc8e7c (rust-blazesym-0.2.0~rc.0-1.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-fa027b306e (rust-blazesym-0.2.0~rc.0-1.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-98919545ca (rust-blazesym-0.2.0~rc.0-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.