[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-devel-list
Subject:    Re: F38 proposal: Rpmautospec by Default (System-Wide Change proposal)
From:       Miroslav_Suchý <msuchy () redhat ! com>
Date:       2023-01-10 9:38:49
Message-ID: f679b1bd-2ca8-ba11-152b-3f846a9d11a3 () redhat ! com
[Download RAW message or body]

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.

Miroslav
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


[prev in list] [next in list] [prev in thread] [next in thread]