This shouldn't be blocked by the freeze as compose-eln01 isn't frozen
and it shouldn't affect anything else.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We moved them to f40 via upgrade, sync up ansible to match so that when
we reinstall them they will get 40 instead of 39
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
I changed the logic a little to prevent the issue with container projects that
happened before, but this needs new change in configuration.
The distgit_bugzilla_sync will now map project to product first based on
namespace and if there are more Bugzilla products mapped to same namespace it
will use the branch_regex. This should be more clear and prevent the container
issue in future.
Signed-off-by: Michal Konecny <mkonecny@redhat.com>
Users don't need to use this and so restrict it to admins by ip for now.
Down the road we should be able to do this much better once we can set a
policy for access here.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
The API didn't work and failed with 500, because the REST framework didn't know
how to render the response. This fixes the issue.
https://pagure.io/fedora-infrastructure/issue/12134
Signed-off-by: Michal Konecny <mkonecny@redhat.com>
EPEL-10.0 needs an override to use 10 in the repomd URL instead of 10.0.
We'll need to move this forward over time to stay on the leading minor
version, allowing trailing minor versions to use the default repomd URL.
Signed-off-by: Carl George <carlwgeorge@gmail.com>
We don't have a stable repo, so skip the epel-release 'latest' link for
epel10 for now. Since we don't have any modular stuff left, we can just
reuse that conditional. ;)
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
While EPEL 10 will have minor versions, the repo for the leading minor
version will be published as just the major version. This is because it
is intended for use on CentOS Stream 10, which does not indicate a minor
version within the operating system.
Signed-off-by: Carl George <carlwgeorge@gmail.com>
In c7fbc26afe9f770414a49d150d9072c1e58b21ec I switched an integer 41 to
a string, but didn't notice that it was inside another string as part of
the double templating this file does. This results in a template error:
jinja2.exceptions.TemplateSyntaxError: expected token 'end of statement block', got 'integer'
Other strings inside this bigger string use double instead of single
quotes to handle this, so let's take the same approach on this line.
Signed-off-by: Carl George <carlwgeorge@gmail.com>
