Laura Barcziová

This occured again for `umockev`, see https://github.com/martinpitt/umockdev/issues/241.

it looks like both staging and prod contained outdated ssh-config before https://github.com/packit/deployment/commit/780ab9729074af82278395764541120203d4452c, I have just updated it. Will close this once it is verified to work.

The problem still persists even with the mentioned change being deployed, see https://dashboard.packit.dev/results/propose-downstream/8787.

On a related note, in #2503 it was mentioned, that something similar would be useful also for downstream Koji builds - be notified for a failure. The preferred way there...

Outcome from our architecture discussion: we will also set up a meeting with someone from CPE to brainstorm how to improve the situation.

> We are cloning the repo there only to get the config, right? That's actually not true, we are getting the config via API earlier. The cloning happens anytime `LocalProject`...

This should be resolved by #2449, we now do not clone the repo for `copr-build` tasks. Closing.

PR for debconf package: https://src.fedoraproject.org/rpms/debconf/pull-request/3. I will continue with other packages once we agree on the config specifics there.

@sergiomb2 I wasn't able to find any upstream git repository which currently is not supported, unfortunately (should be unblocked by https://github.com/packit/packit-service/issues/2202 ). Or have I missed the git repo and...

Yes you are right, the ImageMagick is currently blocked on this issue: https://github.com/packit/packit/issues/2280. So besides that, the missing packages are `opencv`, `clamav` and `git-extras`. If I check correctly, opencv and...