Re: How to deal with COPR and RPMAutoSpec

On úterý 17. října 2023 22:47:23 CEST Richard Shaw wrote: > I'm trying to test build packages before actually creating a side tag and > doing real builds. > > I'm using rpkg to do the test builds but openshading language uses > RPMAutoSpec. I've tried creating empty commits to bump the release

Re: How to deal with COPR and RPMAutoSpec

On Wed, Oct 18, 2023 at 11:18 AM Miroslav Suchý wrote: > > Dne 18. 10. 23 v 16:12 Diego Herrera napsal(a): > > What I usually do when I need for COPR to handle rpmautospec is to set > > the source type to "Custom", and use the following script: > > > &

Re: How to deal with COPR and RPMAutoSpec

Dne 18. 10. 23 v 16:12 Diego Herrera napsal(a): What I usually do when I need for COPR to handle rpmautospec is to set the source type to "Custom", and use the following script: #! /bin/sh -x git clone cd spectool -g rpmautospec process-distgit Set the Buildroot dependenci

Re: How to deal with COPR and RPMAutoSpec

What I usually do when I need for COPR to handle rpmautospec is to set the source type to "Custom", and use the following script: #! /bin/sh -x git clone cd spectool -g rpmautospec process-distgit Set the Buildroot dependencies to "git rpmdevtools rpmautospec" and

Re: How to deal with COPR and RPMAutoSpec

Never mind, I hadn't realized fedpkg had grown the ability to do COPR builds. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: How to deal with COPR and RPMAutoSpec

On Tue, Oct 17, 2023 at 10:47 PM Richard Shaw wrote: > > I'm trying to test build packages before actually creating a side tag and > doing real builds. > > I'm using rpkg to do the test builds but openshading language uses > RPMAutoSpec. I've tried creating empty commits to bump the release but

How to deal with COPR and RPMAutoSpec

I'm trying to test build packages before actually creating a side tag and doing real builds. I'm using rpkg to do the test builds but openshading language uses RPMAutoSpec. I've tried creating empty commits to bump the release but it does not appear to be working. What's the work around?

Re: COPR and rpmautospec

On 18/12/2022 15:14, Michael J Gruber wrote: %autorelease needs the git history, and you are building from dist-git, so that part is fine. COPR has Git history. Example: https://copr-dist-git.fedorainfracloud.org/cgit/xvitaly/matrix/neochat.git/log/ -- Sincerely, Vitaly Zaitsev

Re: COPR and rpmautospec

* Michael J. Gruber: > I'm afraid you're not holding it right ;) > > %autorelease needs the git history, and you are building from > dist-git, so that part is fine. But you are not using `Release: > %autorelease` but, instead, there are additional tags in there. And - > depending on your view on

Re: COPR and rpmautospec

I'm afraid you're not holding it right ;) %autorelease needs the git history, and you are building from dist-git, so that part is fine. But you are not using `Release: %autorelease` but, instead, there are additional tags in there. And - depending on your view on old vs. new version names -

Re: COPR and rpmautospec

On Sat, Dec 17, 2022, 20:59 Florian Weimer wrote: > It looks like COPR always produces 1 for %autorelease. Is this a known > issue? Is there a way around it? > > Here's a build that shows this: > > < > https://copr.fedorainfracloud.org/coprs/fweimer/modernc-1/build/5152562/> > > Thanks, >

Re: COPR and rpmautospec

On 17/12/2022 20:59, Florian Weimer wrote: It looks like COPR always produces 1 for %autorelease. Is this a known issue? Yes. rpmautospec works correctly only in Fedora Koji. In rpmbuild, mock, COPR, it will always use 1. Is there a way around it? I didn't find it, so I reverted my

COPR and rpmautospec

It looks like COPR always produces 1 for %autorelease. Is this a known issue? Is there a way around it? Here's a build that shows this: Thanks, Florian ___ devel mailing