Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Legacy] Sync legacy branch with stable #248

Merged
merged 29 commits into from
Aug 18, 2023

Conversation

grische
Copy link
Contributor

@grische grische commented Jul 26, 2023

Backported PRs to legacy (4/32) branch:

partially #177
partially #201
#189
#182
#188
#190
#191
#186
#219
#217
#230
#231
#241
#244
#245
#246
#247

Reverting spacing changes of 1de0476
@grische grische added the gluon-v2021.1.x Applies on 4/32 branch label Jul 26, 2023
goligo and others added 28 commits July 27, 2023 23:02
- Remove mesh_on_wan from site.conf - default is false anyway
* Make the script idempotent (you can run it again to test patching)
* Drop the usage of git branches for patching.
  The branches were not used and add unncessary complexity
* Do not forcefully reset custom commits in gluon-build as part of the patching
* Reset the gluon-build environment before applying patches
* Do not reset gluon-build environment for debugging if patching failed
In case the gluon-build folder exists and does not contain a .git directory (or
file) the following command "git remote set-url origin" will override the git
remote of the "main" folder/directory.

Avoiding this by checking explicitely for the .git directory inside gluon-build
and restructuring the cloning/fetching process.

This also speeds up the initial cloning by only fetching the commit required to
build.

Important legacy-only change: adding git clean -ffdx packages/
When preparation the gluon-build folder was changed from git clone to git fetch, the tags got lost. This is causing the generated fIrmware version not to incluce the gluon version correctly: "v2022.10.4 / gluon-ab1fb05+" instead of "v2022.10.4 / gluon-v2022.1.1+"
Due to stability issues with GitHub runners, try to run without LVM magic, instead just remove some big software packages.
As the Github build is building targets in separate VMs, it does not use the target-list in the Makefile, but holds its own copy instead. This change moves the target list into a new file called "targets" which is then used by the Makefile as well as the Github workflow.
@grische grische force-pushed the feature/sync_legacy_with_stable branch from 91a97e2 to 398acfd Compare August 17, 2023 09:56
@grische grische marked this pull request as ready for review August 17, 2023 12:11
@grische grische requested a review from a team as a code owner August 17, 2023 12:11
@grische
Copy link
Contributor Author

grische commented Aug 17, 2023

Confirmed working on WR841ND

@grische grische merged commit 98c839f into freifunkMUC:legacy Aug 18, 2023
@grische grische deleted the feature/sync_legacy_with_stable branch August 18, 2023 16:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gluon-v2021.1.x Applies on 4/32 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants