Daniil Anfimov

We have the module preview feature that gets a list of modified packages by parsing yaml file (e.g. `https://git.almalinux.org/almalinux/modified_packages/raw/branch/main/a8.yml`). This approach is going to be deprecated soon, and we need...

To manage our platform repositories in the better way, we should do some adjustments in the `bootstrap_repositories` script to remove repositories from the `platform_repository` table that aren't listed in platform

We're planning to adjust `BuildTaskArtifact` model with `metadata` field where there would be NEVRA for sure and maybe later other data (such as checksums, etc.). After adjusting that model, we...

Right now, when we create a product repository we set an incorrect repo type (instead of `rpm` we set repo arch) and don't set `platform_id`.

Incorrect `modules.yaml` content when one of the modular build items gets rebuilt, modules get duplicated but with different versions (probably introduced by adding a workaround for bypassing Pulp limitations to...

Due to our mapping and incorrect determination of product entities, we can accidentally remove Pulp repositories/distributions that start with the same name

We should add a check in our GH Actions in the web-server repository to reduce cases when new repositories aren't available over HTTP. For now, it would be great to...

When we try to build something with enabled SELinux we get the following error: ``` DEBUG util.py:459: groupadd: /var/lib/mock/b3ea6a75030850a0899dec09154bac44f0e3ab2222e80262060d080b9a7ec1b0.0/root//etc/group.16137: Permission denied DEBUG util.py:459: groupadd: cannot lock /var/lib/mock/b3ea6a75030850a0899dec09154bac44f0e3ab2222e80262060d080b9a7ec1b0.0/root//etc/group; try again later....

We have a problematic query in our build feed endpoint (see https://github.com/AlmaLinux/albs-web-server/blob/master/alws/crud/build.py#L133-L142). This query loads too many entries because of join statements, but without them, filters don't work. Also, we...

Sometimes we can fall into parsing spec files silently to users, and detailed info about parsing spec files can be found in the service logs. For example: mock_build_srpm.log ``` RPM...