https://bugzilla.redhat.com/show_bug.cgi?id=2283850



--- Comment #5 from Cristian Le <[email protected]> ---
Spec URL:
https://github.com/LecrisUT/rusty_parserk-paseto-rpmspec/raw/a68b2628e1f4eadbb43696f948bd33d691f8d86f/rust-rusty_paseto/rust-rusty_paseto.spec
SRPM URL:
https://download.copr.fedorainfracloud.org/results/packit/LecrisUT-rusty_parserk-paseto-rpmspec-main/fedora-rawhide-x86_64/07523788-rust-rusty_paseto/rust-rusty_paseto-0.7.1-1.fc41.src.rpm

rust2rpm.toml
```toml
[[package.extra-patches]]
comments = [
    "Patch Cargo.toml:",
    "- Remove examples",
    "- Relax erased-serde to 0.4.4",
    "- Relax iso8601 to >=0.4.2",
]
file = "rust-rusty_paseto-0.7.1-Patch_dependencies.diff"
number = 10

[scripts.prep]
post = [
    "# Remove examples",
    "rm -r examples",
]
```

---

> why don't you use rust2rpm -p for this?

I do, but I just copy the contents to extra-patches so that it is more easily
reproducible, and it doesn't affect the spec file itself, so it can be placed
in either patch.

> Check line encodings and send a patch upstream

Thanks, PR sent: https://github.com/rrrodzilla/rusty_paseto/pull/41
Should we fix them in the spec file for 0.7.1, or keep it like this since it
only affects the -devel package?


-- 
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2283850

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202283850%23c5
--
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to