| |
@@ -162,13 +162,13 @@
|
| |
Using the `comps-sync.py` script, provide the updated input XML file to examine
|
| |
the changes as a dry-run:
|
| |
|
| |
- `$ ./comps-sync.py /path/to/fedora-comps/comps-f41.xml.in`
|
| |
+ `$ ./comps-sync.py /path/to/fedora-comps/comps-f42.xml.in`
|
| |
|
| |
Examine the changes and cross-reference them with PRs made to the `fedora-comps`
|
| |
repo. When you are satisfied that the changes are accurate and appear safe,
|
| |
re-run the script with the `--save` option:
|
| |
|
| |
- `$ ./comps-sync.py --save /path/to/fedora-comps/comps-f41.xml.in`
|
| |
+ `$ ./comps-sync.py --save /path/to/fedora-comps/comps-f42.xml.in`
|
| |
|
| |
Create a pull request with the changes and note any PRs from `fedora-comps`
|
| |
in the commit message that are relevant to the changes you have generated.
|
| |
@@ -186,22 +186,22 @@
|
| |
### On Rawhide / main branch
|
| |
|
| |
```
|
| |
- sed -i "s/41/42/g" *.repo comps-sync.py
|
| |
- sed -i "s/releasever: 41/releasever: 42/" common.yaml
|
| |
- sed -i "s/# - fedora-41/# - fedora-42/" *.yaml
|
| |
- mv fedora-41.repo fedora-42.repo
|
| |
- mv fedora-41-updates.repo fedora-42-updates.repo
|
| |
- sed -i "s/42/42/g" README.md
|
| |
- sed -i "s/41/42/g" README.md
|
| |
+ sed -i "s/42/43/g" *.repo comps-sync.py
|
| |
+ sed -i "s/releasever: 42/releasever: 43/" common.yaml
|
| |
+ sed -i "s/# - fedora-42/# - fedora-43/" *.yaml
|
| |
+ mv fedora-42.repo fedora-43.repo
|
| |
+ mv fedora-42-updates.repo fedora-43-updates.repo
|
| |
+ sed -i "s/43/44/g" README.md
|
| |
+ sed -i "s/42/43/g" README.md
|
| |
```
|
| |
|
| |
- ### On the new branch (f41)
|
| |
+ ### On the new branch (f42)
|
| |
|
| |
```
|
| |
rm fedora-rawhide.repo
|
| |
sed -i "/- fedora-rawhide/d" fedora-*.yaml
|
| |
- sed -i "s/# - fedora-41/- fedora-41/" *.yaml
|
| |
- sed -i "s/ref: fedora\/rawhide/ref: fedora\/41/" *.yaml
|
| |
+ sed -i "s/# - fedora-42/- fedora-42/" *.yaml
|
| |
+ sed -i "s/ref: fedora\/rawhide/ref: fedora\/42/" *.yaml
|
| |
```
|
| |
|
| |
## Historical references
|
| |
Signed-off-by: Samyak Jain samyak.jn11@gmail.com