SRPM builds successfully, but RPM does not - is that SRPM saved?

Ask Fedora
1

I’m trying to track down a build problem that seems to have popped up with a particular version of a package (or maybe it’s dependencies…) – Ideally I would try copr-rpmbuild (I never have, and I’m curious what all it will do…) – but that package is not available in epel-10, only copr-cli. I do see copr-rpmbuild in the epel-9 repos…

So – I submit a sequence of builds of dependent packages – then I hit my failure. But, the SRPM built successfully, the rpmbuild failed. I’d like to download that built SRPM, but it seems like since the build-id failed it does not save even the SRPM in the repo (which might be a useful thing). So – it seems like I will need to locally build up that SRPM on my own, so I can try to run mock locally and try to track down the problem.

I’m assuming the SRPM is not accessible – so, this is either a comment, or a suggestion – or possibly a question if I’m right. I think it would be handy to get at the SRPM. (Also would be nice if epel-10 had the copr-rpmbuild – not sure why it doesn’t.

2

What commands are you running to create the srpm?
Usually the srpm is created outside of copr.
There are special cases like packaging python code from PyPI yhat do not need a srpm.

3

I guess there are several ways to build… I’m using a Custom Script. The requirements for that are to end up with the .spec and the source tar.gz in the top directory. So, my script is pulling from git repos, and switching to the ‘latest’ tagged version, then building the tarball from that.

When I run a build, I see that it has two stages – the first ‘run’ builds the SRPM – then once that is done, it attempts to build from that. There are separate logs for each stage – and I can see in the SRPM build log, that it successfully wrote the SRPM.

4
5

OK – you are right – I can get at the desired SRPM that way… I was looking in the actual repo. So, at least there is a place to get at it. Thanks!