857192c
@@ -1,4 +1,4 @@
from .metadata import *
from . import licensing
- __version__ = '15'
+ __version__ = '16'
rust2rpm changes:
User-Agent
unwanted-features
.rust2rpm.conf
spdx2fedora changes:
rust-packaging changes:
riscv64
%rust_arches
Pull-Request has been merged by zbyszek
I now also pushed a tag using your text as description.
@zbyszek Don't forget the tarball upload for the release.
Aint't it automatic, e.g. https://pagure.io/fedora-rust/rust2rpm/archive/v16/rust2rpm-v16.tar.gz ?
I don't think we've ever used those, there have been releases made as tar.xz tarballs and uploaded to https://releases.pagure.org/fedora-rust/rust2rpm/
That was exactly my intention, since I don't know how to create the tags / release tarballs :thumbsup:
OK, so I think it's time to stop doing the manual tarballs. The automatically-generated tarball works just as well. I already built the fedora package from it.
You'll need to update rust-srpm-macros as well, apparently rust-packaging and it needs matching versions.
Problem: cannot install the best candidate for the job - nothing provides rust-srpm-macros = 16 needed by rust-packaging-16-1.fc34.x86_64
Thanks. I'll do that.
But it seems that the whole setup is unnecessarily complicated: two packages are built from the same source tarball. I guess that rust-packaging is built as arched to support only some architectures, and rust-srpm-macros is built separated to be noarch. Instead we should build both from the same package.
rust-packaging
rust-srpm-macros
https://src.fedoraproject.org/rpms/rust-packaging/pull-request/1
rust2rpm changes:
User-Agent
header to "rust2rpm" to work around new crates.io API limits, which prevent rust2pm from accessing crates.iounwanted-features
setting in.rust2rpm.conf
files to prevent subpackages for specific "unwanted" features from being generatedspdx2fedora changes:
rust-packaging changes:
riscv64
to%rust_arches