Administration/pmbootstrap-meow
2
0
Fork 0
forked from Mirror/pmbootstrap
Code Pull requests Activity Actions

Replace pmaports channels stable, stable-next (MR 2032)

Browse source 
Translate the pmaports channels "stable" to "v20.05" and "stable-next"
to "v21.03", so these have the same channel name as the pmaports.git
branch name.

The original plan was to switch the "stable" channel from the "v20.05"
branch to the "v21.03" branch when the release is done. However, now
that we are close to that, I'm realizing that this would not be useful.
It would lead to conflicts in the dir with locally built packages
(default: ~/.local/var/pmbootstrap/packages/$CHANNEL). And it would make
it awkward to go back to a previous branch (we may name it old-stable
for the time being, but what after that, old-old-stable?).
This commit is contained in:
Oliver Smith 2021-03-02 19:47:58 +01:00
parent 5c1c126647
commit 278dfced61
No known key found for this signature in database
GPG key ID: 5AE7F5513E0885CB
13 changed files with 90 additions and 25 deletions
Download patch file Download diff file Expand all files Collapse all files

8
test/test_helpers_git.py
View file

@ -116,10 +116,14 @@ def test_parse_channels_cfg(args):
"branch_pmaports": "master",
"branch_aports": "master",
"mirrordir_alpine": "edge"},
"stable": {"description": "For workgroups",
"v20.05": {"description": "For workgroups",
"branch_pmaports": "v20.05",
"branch_aports": "3.11-stable",
"mirrordir_alpine": "v3.11"}}}
"mirrordir_alpine": "v3.11"},
"v21.03": {"description": "Second beta release",
"branch_pmaports": "v21.03",
"branch_aports": "3.13-stable",
"mirrordir_alpine": "v3.13"}}}
assert pmb.helpers.git.parse_channels_cfg(args) == exp