Description of problem: I'm trying to correctly package the rust package called biquad and rpmbuild complains about this part of the spec file when successfully building: %files devel %license %{crate_instdir}/LICENSE-APACHE %license %{crate_instdir}/LICENSE-MIT %doc %{crate_instdir}/CHANGELOG.md %doc %{crate_instdir}/README.md %{crate_instdir}/ I've compaired to the rust packages that we have in the official repos and none of them differ from this when the devel package is regarded so I don't understand why rpmbuild says: RPM build warnings: File listed twice: /usr/share/cargo/registry/biquad-0.4.2/CHANGELOG.md File listed twice: /usr/share/cargo/registry/biquad-0.4.2/LICENSE-APACHE File listed twice: /usr/share/cargo/registry/biquad-0.4.2/LICENSE-MIT File listed twice: /usr/share/cargo/registry/biquad-0.4.2/README.md Version-Release number of selected component (if applicable): 4.18.2 How reproducible: All the time. Steps to Reproduce: 1. Download the proposal spec file. 2. Open a terminal window. 3. Download the crate file for biquad to ~/rpmbuild/SOURCES/. 3. cd to the location of the spec file. 4. Do urpmi rust-biquad.spec as root. 5. Now do rpmbuild -ba rust-biquad.spec and watch it reach the end when it says exit 0 where it says: RPM build warnings: File listed twice: /usr/share/cargo/registry/biquad-0.4.2/CHANGELOG.md File listed twice: /usr/share/cargo/registry/biquad-0.4.2/LICENSE-APACHE File listed twice: /usr/share/cargo/registry/biquad-0.4.2/LICENSE-MIT File listed twice: /usr/share/cargo/registry/biquad-0.4.2/README.md even though many of our spec files tells you to use %{crate_instdir}/ for the mentioned files. This is NOT normal if you ask me.
Created attachment 14389 [details] Proposal spec file
CC: (none) => lovaren
Created attachment 14390 [details] Crate file for biquad
Created attachment 14391 [details] biquad-fix-metadata patch diff
Created attachment 14392 [details] biquad-libm0.2 patch
rust-biquad is no part of Mageia. Mageia bugzilla is not a support forum for packaging questions. Please ask for packaging help in the support forums or mailing lists.
Status: NEW => RESOLVEDResolution: (none) => INVALID