Infrastructure/infra-docs-fpo
3
0
Fork 0
Code Issues 100 Pull requests 6 Projects Releases Packages Wiki Activity Actions

Drop more stuff that isn't required for EPEL

Browse source 
Signed-off-by: Diego Herrera <dherrera@redhat.com>
This commit is contained in:
Diego Herrera 2025-03-10 14:21:08 -03:00
parent 31bc81d135
commit 27e1b6f27e
1 changed files with 0 additions and 38 deletions
Download patch file Download diff file Expand all files Collapse all files

38
modules/release_guide/pages/sop_epel_minor_mass_branching.adoc
View file

@ -54,7 +54,6 @@ $ koji cancel <build>
Now we need to update dist-git in two steps: Now we need to update dist-git in two steps:
* Create the new branch in git * Create the new branch in git
* Update the gitolite.conf to allow user to push to this new branch
For both of these actions you will need the file generated by pdc above. For both of these actions you will need the file generated by pdc above.
@ -105,15 +104,6 @@ Please check these files from the https://pagure.io/fedora-infra/ansible/c/549e5
Make sure that the SLAs are added, check https://pagure.io/fedora-infra/ansible/pull-request/2190#request_diff[this PR] for reference. Make sure that the SLAs are added, check https://pagure.io/fedora-infra/ansible/pull-request/2190#request_diff[this PR] for reference.
=== Fedora Branched
WARNING: TODO: Confirm if we should skip this part for EPEL
. Set https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/FedoraBranched.yaml[FedoraBranched] to True.
. Set https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/FedoraBranchedBodhi.yaml[FedoraBranchedBodhi] to preenable.
Please check the file `FedoraBranched.yaml` and `FedoraBranchedBodhi.yaml` from the https://pagure.io/fedora-infra/ansible/c/549e5d3ace41c04fdbef9d81f359f16c2fe0c2fa?branch=main[commit] for your reference.
=== Koji hub === Koji hub
Update the koji hub config to allow side tags for new koji rawhide (currently f{rawhide}) tag. Update the koji hub config to allow side tags for new koji rawhide (currently f{rawhide}) tag.
@ -177,19 +167,6 @@ from https://pagure.io/releng[pagure releng] repo. This should be run on
$ sudo -u ftpsync sh scripts/branching-epel/create_empty_repos.sh 10.1 $ sudo -u ftpsync sh scripts/branching-epel/create_empty_repos.sh 10.1
---- ----
[NOTE]
====
Update the link in /mnt/koji/repos/epel10/latest use https://pagure.io/releng/issue/12255 as reference.
====
[NOTE]
====
Please verify the repo permissions that are created under
/pub/epel/<fedora_release_number>. They should
be owned by _ftpsync:ftpsync_
Check directory permissions (should be "0755") to ensure new composes synchronize correctly.
====
=== Creating EPEL10.1 release === Creating EPEL10.1 release
To create a new minor release in bodhi, you need to run: To create a new minor release in bodhi, you need to run:
@ -228,21 +205,6 @@ $ sudo rbac-playbook openshift-apps/bodhi.yml
$ sudo systemctl restart fm-consumer@config.service bodhi-celery.service $ sudo systemctl restart fm-consumer@config.service bodhi-celery.service
``` ```
=== Update rawhide koji repo
We need to point the _epel10_ buildroot repo to the newly created
epel buildroot. This way kojira doesn't make a newrepo for _epel10_
target as often as epel10.xx-build (new epel10 buildroot).
Run the following commands from any of the compose boxes:
[source,bash,subs="attributes"]
----
$ cd /mnt/koji/repos/epel10
$ rm -f latest
$ ln -s ../epel10.1-build/latest ./latest
----
=== Update block_retired.py script === Update block_retired.py script
https://pagure.io/releng/blob/main/f/scripts/block_retired.py[block_retired.py] https://pagure.io/releng/blob/main/f/scripts/block_retired.py[block_retired.py]