#8925 epel8-playground build blocking epel8 build
Closed: Fixed 2 months ago by kevin. Opened 7 months ago by dwd.

  • Describe the issue
    I'm trying to build singularity-3.4.2-1.1 for epel8 and it won't let me. I built it for epel8-playground, but now if I try fedpkg build in the epel8 branch it says
Could not execute build: Package singularity-3.4.2-1.1.el8 has already been built
Note: You can skip this check with --skip-nvr-check. See help for more info.

I successfully did this command a couple of weeks ago on the previous version. I tried --skip-nvr-check but it fails then too with

38490479 build (epel8-candidate, /rpms/singularity.git:790d2aa0062dc95d5e475e4ad4b41fa17d0b0188): open (buildhw-10.phx2.fedoraproject.org) -> FAILED: GenericError: Build already exists (id=1403378, state=COMPLETE): {'name': 'singularity', 'task_id': 38490479, 'extra': '{"source": {"original_url": "git+https://src.fedoraproject.org/rpms/singularity.git#790d2aa0062dc95d5e475e4ad4b41fa17d0b0188"}}', 'pkg_id': 22529, 'epoch': None, 'source': 'git+https://src.fedoraproject.org/rpms/singularity.git#790d2aa0062dc95d5e475e4ad4b41fa17d0b0188', 'state': 0, 'version': '3.4.2', 'completion_time': None, 'volume_id': 0, 'owner': 4159, 'release': '1.1.el8', 'start_time': 'NOW'}
  0 free  0 open  0 done  1 failed

It turns out the epel8-playground build was going to be the same as the epel8 build, so I thought I would try to just do fedpkg update on it as it was, but that fails with

Could not execute update: Could not generate update request: Cannot find release associated with build: singularity-3.4.2-1.1.el8, tags: ['epel8-playground']
A copy of the filled in template is saved as bodhi.template.last

I don't know why that say epel8-playground, since I'm in the epel8 branch. I thought I would try untagging it, but I don't have the permission

$ koji untag-pkg epel8-playground singularity-3.4.2-1.1.el8
2019-10-22 14:38:20,145 [ERROR] koji: ActionNotAllowed: tag requires autosign permission

Can you help? If you'd untag the package I'd skip the epel8-playground build and that would likely fix it. Better would be if you could explain how to have both epel8-playground and epel8 builds.

When I did the epel8-playground build yesterday I used fedpkg-1.37-4.el7. Today I updated to fedpkg-1.37-7.el7 hoping it might make a difference for this problem but it doesn't.

  • When do you need this? (YYYY/MM/DD)

  • When is this no longer needed or useful? (YYYY/MM/DD)
    I guess in a few weeks when the next version is expected.

  • If we cannot complete your request, what is the impact?
    I won't be able to release this version for epel8.

I got the same problem with epel-rpm-macros. The entire playground thing confuses me a lot.

This problem should be fixed as we had competing tags going on. The larger conversation on the confusion of playground is outside the scope of this ticket and should be dealt with on the mailing list. I apologize for this confusion as I was hoping we could come up with an easy way to allow fast/slow and breaking/non-breaking changes.

@smooge By "fixed" do you mean for new cases, or is it supposed to be fixed for previous cases as well? I still get the same errors if I try to build singularity-3.4.2-1.1 in the epel8 branch.

@$@$#@%#@$%$##$% @$@@$@#@$%$ @@$%##@%#@@@#$@@$#@$%

other expletives deleted. OK for me to try and do the builds as a proven packager to diagnose why this is still happening?

Sure, please go ahead.

This has long since been fixed. The problem was someone build epel-rpm-macros in epel8 and just merged it to epel8-playground, which wiped out the dist override in it.

If you are still seeing this at all, please re-open or file a new ticket.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 months ago

Login to comment on this ticket.