#684 'Specfile is not available' on push and new-sources for container repositories
Closed: Fixed a year ago by onosek. Opened a year ago by rhhemartin.

Hi! A new change was introduced recently (1.66.5 most probably) that makes rhpkg to search for a Specfile even in container repositories.

My versions that lead to the error:
rhpkg version: 1.44-3.fc37eng
python3-rpkg: 1.66-5.fc37eng

The exact error line:

  • Could not execute push: Spec file is not available
  • Could not execute new_sources: Spec file is not available

The workaround was to install from URLs older packages, because they were not available on the RPM repositories.

The expected behavior is that does not fail requiring a Specfile.


The expected behavior is that does not fail requiring a Specfile.

One might require Dockerfile inspead fo spec file for container repositories :-)
Not sure how simple is to find out in rpkg whether repo is for rpm, container or module

Could I rely on it? I mean that the container repo always contains a Dockerfile.
I am not usually working with containers and modules, so I am not aware of the rules there. How strict they are.

regular container repos require Dockerfile, but there can be also flatpak build which doesn't have initial Dockerfile and one is created on the fly in osbs

@onosek shouldn't it be based on the namespace? rpms/ should have spec files, containers/ should have Dockerfiles/Containerfiles, etc.

I'm facing the same issue when using CEkit to build containers in OSBS.

Login to comment on this ticket.

Metadata
Related Pull Requests
  • #691 Merged a year ago