Tomáš Hozza

> A solution to this could be to use software emulation. We have not done this internally in osbuild, as we don't have a supported software emulation solution to rely...

When I made a deliberate typo in the config, I got also an error printed multiple times: ``` $ packit validate-config .packit.yaml 2023-10-30 10:37:22.309 utils.py ERROR .packit.yaml does not pass...

Note that everything needed to build the image must be pinned down in the osbuild manifest. While we can download RPMs from a repo when these are pinned using their...

> > warning This PR introduces changes in at least one manifest (when comparing PR HEAD [dff5103](https://github.com/osbuild/osbuild-composer/commit/dff51039fdebbd76b393f88b2ace1de5193e86f2) with the main merge-base [13fdf04](https://github.com/osbuild/osbuild-composer/commit/13fdf04839ff25f4cd61c80a0d046824df0519c5)). Please review the changes. The changes can be...

I also noticed that some CI jobs are failing on 9.2 images due to `image-info` not being able to inspect images. @lavocatt is working on it for the `manifest-db` repo,...

> Maybe we could catch stderr from dnf and look for errors to fail the depsolve job in such cases. We've talked to the dnf team a couple of times...

This was done as part of https://github.com/osbuild/osbuild-composer/pull/2914

@dependabot rebase

Closing and letting depenabot to create a new PR, since it can't handle someone else rebasing it.

Hi @husky-parul. Sorry for the late response. I just tested this scenario on F35, but the osbuild-composer available in the repositories is already of version 47. Could you please confirm...