[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:       Richard Shaw <hobbes1069 () gmail ! com>
Date:       2023-01-10 22:20:35
Message-ID: CAN3TeO1OTkKJq6VWOFu6qSmEUBbdCEOYnHe0Jh4hCuunKp6EPw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Tue, Jan 10, 2023 at 11:48 AM Miro Hron=C4=8Dok <mhroncok@redhat.com> wr=
ote:

> On 10. 01. 23 13:52, Richard Shaw wrote:
> >     Second, how exactly are you building the package?
> >     Looking at [1], you used "Source Type: SRPM or .spec file upload".
> >     How was it generated?
> >
> >     [1]
> https://copr.fedorainfracloud.org/coprs/hobbes1069/OIIO/build/5210045/
> >     <
> https://copr.fedorainfracloud.org/coprs/hobbes1069/OIIO/build/5210045/>
> >
> >     Both 'fedpkg srpm' and uploading that to copr, and letting copr
> build from
> >     dist-git should result in the expected release. (Though without
> other steps
> >     it'll still be the same as the version in Fedora release, so you'll
> need
> >     to tell dnf to install that specific build.)
> >
> >
> > Looks like the problem is using `rpkg` but that's the easiest method an=
d
> has
> > worked great until now...
>
> For the record I've reported several issues with the rpkg method over the
> years. The distgit method was partially a response for those. tl;dr rpkg
> "works
> great" until it doesn't because it does not work like fedpkg, but instead
> it is
> a pre-processor for templated spec files that happens to work in most of
> the
> cases with bare spec files as well.
>

I didn't realize the fedpkg had grown the ability to do COPR builds. I will
use that from now on.

Thanks,
Richard

[Attachment #5 (text/html)]

<div dir="ltr"><div dir="ltr">On Tue, Jan 10, 2023 at 11:48 AM Miro Hrončok &lt;<a \
href="mailto:mhroncok@redhat.com">mhroncok@redhat.com</a>&gt; wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 10. 01. 23 13:52, \
Richard Shaw wrote:<br> &gt;        Second, how exactly are you building the \
package?<br> &gt;        Looking at [1], you used &quot;Source Type: SRPM or .spec \
file upload&quot;.<br> &gt;        How was it generated?<br>
&gt; <br>
&gt;        [1] <a href="https://copr.fedorainfracloud.org/coprs/hobbes1069/OIIO/build/5210045/" \
rel="noreferrer" target="_blank">https://copr.fedorainfracloud.org/coprs/hobbes1069/OIIO/build/5210045/</a><br>
 &gt;        &lt;<a href="https://copr.fedorainfracloud.org/coprs/hobbes1069/OIIO/build/5210045/" \
rel="noreferrer" target="_blank">https://copr.fedorainfracloud.org/coprs/hobbes1069/OIIO/build/5210045/</a>&gt;<br>
 &gt; <br>
&gt;        Both &#39;fedpkg srpm&#39; and uploading that to copr, and letting copr \
build from<br> &gt;        dist-git should result in the expected release. (Though \
without other steps<br> &gt;        it&#39;ll still be the same as the version in \
Fedora release, so you&#39;ll need<br> &gt;        to tell dnf to install that \
specific build.)<br> &gt; <br>
&gt; <br>
&gt; Looks like the problem is using `rpkg` but that&#39;s the easiest method and has \
<br> &gt; worked great until now...<br>
<br>
For the record I&#39;ve reported several issues with the rpkg method over the <br>
years. The distgit method was partially a response for those. tl;dr rpkg &quot;works \
<br> great&quot; until it doesn&#39;t because it does not work like fedpkg, but \
instead it is <br> a pre-processor for templated spec files that happens to work in \
most of the <br> cases with bare spec files as \
well.<br></blockquote><div><br></div><div>I didn&#39;t realize the fedpkg had grown \
the ability to do COPR builds. I will use that from now on.  \
</div><div><br></div><div>Thanks,</div><div>Richard</div></div></div>


[Attachment #6 (text/plain)]

_______________________________________________
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]