Bug 2024814

This package built on koji:  https://koji.fedoraproject.org/koji/taskinfo?taskID=79057785

Taking this review (I need this package too, for reqwest 0.11.8).

Two minor issues:

- regenerate the spec with rust2rpm 20
- drop unused "criterion" dev-dependency (only used for benchmarks, so it's unused during RPM builds, but it is still compiled and increases build times by *a lot*)

(regenerating with "rust2rpm -sap rustls-pemfile" and removing "criterion" dev-dependency from Cargo.toml should fix both issues)

@dcavalca are you still interested in getting this package reviewed?
Otherwise I will submit a review request for it myself, as I need it for updating reqwest with all features enabled.

Yep, I'll try and get this wrapped up today or tomorrow.

Spec URL: https://dcavalca.fedorapeople.org/review/rust-rustls-pemfile/rust-rustls-pemfile.spec
SRPM URL: https://dcavalca.fedorapeople.org/review/rust-rustls-pemfile/rust-rustls-pemfile-0.3.0-1.fc37.src.rpm

Changelog
- re-run rust2rpm
- update to 0.3.0
- drop criterion dev-dependency

Package was generated with rust2rpm, simplifying the review.

- package builds and installs without errors on rawhide
- test suite is run and all unit tests pass
- latest version of the crate is packaged
- license matches upstream specification (ASL 2.0 or ISC or MIT) and is acceptable for Fedora
- license files are included with %license in %files
- package complies with Rust Packaging Guidelines

Package APPROVED.

===

Recommended post-import rust-sig tasks:

- add @rust-sig with "commit" access as package co-maintainer

- set bugzilla assignee overrides to @rust-sig (optional)

- set up package on release-monitoring.org:
  project: $crate
  homepage: https://crates.io/crates/$crate
  backend: crates.io
  version scheme: semantic
  version filter: alpha;beta;rc;pre
  distro: Fedora
  Package: rust-$crate

- track package in koschei for all built branches

===

Please build this package for f34+ as I will need it for future builds of request.

Thanks!

$ fedpkg request-repo rust-rustls-pemfile 2024814
https://pagure.io/releng/fedora-scm-requests/issue/43159

You can already submit requests for the other branches, if you want to reduce round-trip-time for the fedora-scm-requests ticket queue:

$ fedpkg request-branch --repo rust-rustls-pemfile f36
$ fedpkg request-branch --repo rust-rustls-pemfile f35
$ fedpkg request-branch --repo rust-rustls-pemfile f34

Those tickets are processed in the order in which they were submitted, so there's no need to wait until the "request-repo" ticket is processed before submitting the other ones.

Oh thanks, I didn't know that. Done:

$ fedpkg request-branch --repo rust-rustls-pemfile f36
https://pagure.io/releng/fedora-scm-requests/issue/43160
$ fedpkg request-branch --repo rust-rustls-pemfile f35
https://pagure.io/releng/fedora-scm-requests/issue/43161
$ fedpkg request-branch --repo rust-rustls-pemfile f34
https://pagure.io/releng/fedora-scm-requests/issue/43162

(fedscm-admin):  The Pagure repository was created at https://src.fedoraproject.org/rpms/rust-rustls-pemfile

FEDORA-2022-b640231e6d has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b640231e6d

FEDORA-2022-b640231e6d has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2022-bc23243a63 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-bc23243a63

FEDORA-2022-316b915c11 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-316b915c11

FEDORA-2022-1ecdd99f7d has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1ecdd99f7d

FEDORA-2022-bc23243a63 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2022-bc23243a63 \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-bc23243a63

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2022-1ecdd99f7d has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2022-1ecdd99f7d \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-1ecdd99f7d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2022-316b915c11 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2022-316b915c11 \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-316b915c11

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2022-bc23243a63 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2022-316b915c11 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2022-1ecdd99f7d has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.