On Tue, Jan 10, 2023 at 4:39 AM Miroslav Suchý <msuchy(a)redhat.com> wrote:
Dne 10. 01. 23 v 9:29 Vitaly Zaitsev via devel napsal(a):
> On 10/01/2023 08:16, Zbigniew Jędrzejewski-Szmek wrote:
>> If rpmautospec is used in COPR, and the build is started in a
>> compatible way, the release field should be the same as in koji.
>
> Steps to reproduce:
>
> 1. Create a new COPR project.
> 2. Add a new COPR package with building from SCM:
> - Type - Git
> - Clone URL:
https://src.fedoraproject.org/rpms/protobuf-c.git (you can choose any
other package with rpmautospec)
> - Commithash: rawhide
> - Spec File: protobuf-c.spec
> - How to build SRPM - rpkg (default choice)
> 3. Press Save and Rebuild.
> 4. Wait for the results. Check the final RPM. It will have Release: 1 and an empty
%changelog.
>
rpmautospec should work with plain git - I will leave the defending for others.
But in your case you should rather use DistGit instead of SCM method (the first row of
tabs):
https://docs.pagure.org/copr.copr/user_documentation.html#distgit
And it should start working.
Admittedly, I have a weird case here, but I'm forking a Fedora package
and putting it outside of DistGit. It uses RPMAutoSpec and I'm trying
to build this in COPR, but because I can't use it through the DistGit
method, the NVR is broken.
Example:
* Git:
https://pagure.io/fedora-asahi/asahi-fedora-remix-release
* Package:
https://copr.fedorainfracloud.org/coprs/g/asahi/fedora-remix-branding/bui...
--
真実はいつも一つ!/ Always, there's only one truth!