New COPR user - successfully built pkg not going to project repo

Ask Fedora
1

I’m very new to copr, so I’m likely missing something – but, I forked a project that was building three pkgs successfully. When I try to build them, the first one succeeds, but I’m having issues with the others (which depend on the first). After a few retries, I managed to get the 2nd package to build – but it seems like the result did not end up in the project repo. When I tried the third build, it failed because it didn’t have that 2nd dependency. I re-submitted with ssh-access and tried poking around on the builder some. However, I only see fedora repos in /etc/yum.repos.d – I expected to see my ‘project’ repo in there – as I think it is needed.
I thought builds for the same project were supposed to be added to that project repo.

What am I missing?

2

Looking more carefully at the backend.log, it looks like the VM expired before result could be published. It did show as ‘success’ in the main Project Summary, which threw me off. Also, looking at the builder-live.log it appears the package build was successful. But the backend.log seems to have timed out, and therefore published no pkgs. Not sure why things are running so slowly.

3

Hello, sorry to hear that Copr made not so good first impression.

Can you please point me to your project? I’ll try to see what went wrong.

4

I think after several tries, it finally worked. And I may have deleted some of the ‘failed’ attempts – but you are welcome to take a look. It’s at: https://copr.fedorainfracloud.org/coprs/grayeul/rakudo-el-sandbox/

I am still curious – when I ssh’ed in to the build machine, it didn’t look like my repo for this project was enabled. Does that happen in some other way? Shouldn’t I be able to see that as a valid repo when I ssh in to that machine?

thanks,

bob

5

I think this is the project?

and the builds 10264961 and 10264962. From the builder-live.log I can see that it failed because of

No matching package to install: 'moarvm-devel >= 2026.02'
Not all dependencies satisfied
Error: Some packages could not be found.

The moarvm-devel should have been available from the forked project. Is it possible you submitted those while the project was still saying

Forked project is still being prepared for you. It may take a few minutes to duplicate backend data.

From the logs, I can see the forking action eventually finished successfully.

6

I am still curious – when I ssh’ed in to the build machine, it didn’t look like my repo for this project was enabled. Does that happen in some other way? Shouldn’t I be able to see that as a valid repo when I ssh in to that machine?

The build is not done directly on the virtual machine but in a Mock environment.

If you open any builder-live.log for any of your builds, there is this at the very top:

You can reproduce this build on your computer by running:

  sudo dnf install copr-rpmbuild
  /usr/bin/copr-rpmbuild --verbose --drop-resultdir --task-url https://copr.fedorainfracloud.org/backend/get-build-task/10264961-epel-10-x86_64 --chroot epel-10-x86_64

If you run that command on the machine, or even on your own laptop, you will reproduce that build exactly in a way that Copr does. In your case, you could for example add the --dump-configs parameter which will just generate a Mock config for you. And you can see that repositories there.

7

Ok, thanks. Yes, eventually the pkgs made it to the repo. The first couple of times, it wasn’t quite setup. But even later, at least once the pkg built ok, but the VM did before pkg could be published to repo.

Bib