Help people with migrating to gitlab.postmarketos.org

I propose helping users that currently have their pmbootstrap git remote to gitlab.com to migrate over.

Finish and merge MRs !2445 (merged) and !2447 (merged)

Done

Tag a new stable pmbootstrap release v2.3.2

Done: https://gitlab.postmarketos.org/postmarketOS/pmbootstrap/-/tags/2.3.2

Push these patches to gitlab.com/postmarketOS/pmbootstrap to master and 2.3.x branch respectively: gitlab.com-master.patch & gitlab.com-2.3.x.patch (probably need to unarchive the repo, push, archive again)

EDIT: sorry didn't read your message properly, I thought you proposed to fast-forward to current 2.3.x and master branches. your approach is more user-friendly than mine, I'll do that now.

EDIT: done, applied your patch to gitlab.com master and 2.3.x!

If we only pushed the patches to do the pmaports migration to pmbootstrap.git, then users would "git pull", have pmaports migrated but would still run an old pmbootstrap version that won't be updated anymore moving forward.

So I've deleted pmbootstrap.git contents for the master and 2.3.x branches instead, and updated the README.md (like done here):

https://gitlab.com/postmarketOS/pmbootstrap/

With this, users who have been using pmbootstrap git, and do a "git pull", will immediately notice that they can't use this repository anymore and need to switch to the new source. We will also notice if any of our scripts have still been using the old repository URL and can fix them.

Remove contents from gitlab.com/postmarketOS/pmaports and replace with a single README.md file advising users to upgrade to the latest pmbootstrap release / git checkout, similar to the message in the linked pmbootstrap patches. This will hopefully make it (more) obvious for users who are running pmbootstrap pull on pmbootstrap v2.3.1

With this proposal we create a git tree that cannot be fast-forwarded after migrating the git remote URLs. Another idea:

wait 1 week to give distros time to package pmbootstrap 2.3.2 (e.g. it isn't merged in alpine yet right now)
set pmbootstrap_min_version=2.3.2 in pmaports.cfg in pmaports.git master and v24.06
unarchive the gitlab.com repository and fast-forward the full tree of changes for master and v24.06 there
archive it again

Then users running 2.3.1 who do "pmbootstrap pull" will get a notice that they need to upgrade to pmbootstrap 2.3.2 or higher. Once they do, the pmaports.git URL gets migrated, and they can use "pmbootstrap pull" to fast-forward without errors. I've made a note to do this next week.

Thanks so much for starting this issue to have a proper migration path for users, who may otherwise not be aware that we switched source repo locations if they only used "git pull" and "pmbootstrap pull"!

changed the description

marked the checklist item 4. Remove contents from gitlab.com/postmarketOS/pmaports and replace with a single README.md file advising users to upgrade to the latest pmbootstrap release / git checkout, similar to the message in the linked pmbootstrap patches. This will hopefully make it (more) obvious for users who are running pmbootstrap pull on pmbootstrap v2.3.1 Wait until 2024-11-03, set pmbootstrap_min_version=2.3.2 in pmaports.cfg on gitlab.postmarketos.org, unarchive, fast-forward until this change at gitlab.com, archive as completed

all done!

closed

Help people with migrating to gitlab.postmarketos.org

Child items ...

Activity