$ rust2rpm crc-any --patch Subcommand failed with code 101: cargo metadata --quiet --format-version 1 --offline --no-deps --manifest-path /tmp/tmp76b90d62/crc-any-2.5.0/Cargo.toml I save and exit the editor, but then the /tmp file is gone and the cargo-metadata command fails rust2rpm-26.1.1-3.fc41.noarch Reproducible: Always
I cannot reproduce this issue ... do you have any special setup for /tmp on your system?
Okay, the problem is that I am editing the Cargo.toml in such a way that it cannot be parsed. But the error message that cargo metadata produces is not output so it is very hard to tell what is going on. If I run the command on the file manually I get: error: failed to parse manifest at `/home/orion/rust-crc-any/rust-crc-any-2.5.0-build/crc-any-2.5.0/Cargo.toml` Caused by: feature `alloc` includes `debug-helper` which is neither a dependency nor another feature Can we get rust2rpm to output that message?
Hum, looks like there's a bug in cargo2rpm that makes it eat command output in case the return code from "cargo metadata" is non-zero. I'm testing a fix now - if it resolves this issue, I'll tag a new release and update the package in Fedora.
FEDORA-EPEL-2024-b73358ead7 (cargo2rpm-0.1.17-1.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-b73358ead7
FEDORA-2024-4eb27d6b90 (cargo2rpm-0.1.17-1.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-4eb27d6b90
FEDORA-2024-5109f41e83 (cargo2rpm-0.1.17-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-5109f41e83
FEDORA-2024-f72de18097 (cargo2rpm-0.1.17-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-f72de18097
FEDORA-EPEL-2024-b73358ead7 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-b73358ead7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-f72de18097 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-f72de18097` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-f72de18097 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-4eb27d6b90 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-4eb27d6b90` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-4eb27d6b90 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-5109f41e83 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-5109f41e83` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-5109f41e83 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-f72de18097 (cargo2rpm-0.1.17-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-b73358ead7 (cargo2rpm-0.1.17-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-4eb27d6b90 (cargo2rpm-0.1.17-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-5109f41e83 (cargo2rpm-0.1.17-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.