Add packit config to build rpms in Copr

[r0x0d]

No description provided.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {0: {'trigger': ['Missing data for required field.']}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {0: {'trigger': ['Missing data for required field.']}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {0: {'trigger': ['Missing data for required field.']}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {0: {'trigger': ['Missing data for required field.']}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {0: {'trigger': ['Missing data for required field.']}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {0: {'trigger': ['Missing data for required field.']}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[r0x0d]

/packit build

[packit-as-a-service]

We have requested the builder permissions for the @rhel-lightspeed/shellai Copr project.

Please confirm the request on the @rhel-lightspeed/shellai Copr project permissions page and retrigger the build by clicking on a Re-run button or with a /packit build pull-request comment (for builds in pull-requests).

[r0x0d]

/packit build

[r0x0d]

/packit build

[r0x0d]

/packit build

[packit-as-a-service]

Based on your Packit configuration the settings of the @rhel-lightspeed/shellai Copr project would need to be updated as follows:

field	old value	new value
chroots	['rhel-9-x86_64', 'rhel-8-x86_64']	['epel-8-x86_64', 'epel-9-x86_64', 'rhel-8-x86_64', 'rhel-9-x86_64']

Diff of chroots:

+epel-9-x86_64
+epel-8-x86_64

Packit was unable to update the settings above as it is missing admin permissions on the @rhel-lightspeed/shellai Copr project.

To fix this you can do one of the following:

• Grant Packit admin permissions on the @rhel-lightspeed/shellai Copr project on the permissions page.
• Change the above Copr project settings manually on the settings page to match the Packit configuration.
• Update the Packit configuration to match the Copr project settings.

Please retrigger the build, once the issue above is fixed.

[r0x0d]

/packit build

[r0x0d]

/packit build

[r0x0d]

If #8 gets accepted, this will be reworked to be a meta package where it will install only a reference bash script to execute the underlying container with podman.

[r0x0d]

/packit build

[r0x0d]

/packit build