v21.12 service pack 1
Discussion issue for the next service pack, suggestions welcome.
- use gnss-share on librem 5: !2736 (closed)
- workaround for fixing modem regression on samsung-serranove (may not be ready yet, but don't want ot forget about it): #1274 (comment 778738594)
-
chatty 0.5 (includes MMS support). see comment thread below (-> probably not this service pack though, chatty 0.5 stable is still not out and needs testing on edge first)
- mmsd-tng 1.7, fork from alpine aports (only if backporting Chatty 0.5...)
- upgrade sxmo to 1.7.0
- backports of !2795, !2799 (should ofc be merged to edge first and see a bit of testing there)
-
librem 5 u-boot 0.11- removed because: if fixes some charging 'issues', but it wouldn't get flashed on existing devices unless the user ran the update script manually. so that's unlikely to happen. and the issues it fixes aren't that critical
-
install PA on pmos-ui-mate: https://gitlab.postmarketos.org/postmarketos/pmaports/-/merge_requests/2820see https://gitlab.postmarketos.org/postmarketos/pmaports/-/merge_requests/2820#note_804229191
Activity
added service-pack-discussion label
mentioned in issue #1274 (closed)
By clayton craft on 2021-12-16T00:55:42
I would highly reccomend we backport Chatty v0.5 as soon as it is released. v0.5 adds full support for MMS.
Chatty v0.5beta4 was just released so the final release shouldn't be far away.
By Tim M. on 2021-12-19T15:42:18
Edited by Ghost User-
great idea, I added it to the list above.
everything else needed for MMS is already in alpine 3.15, so it should really just be a matter of forking the 0.5 chatty package from alpine aports for the SP1 release
By clayton craft on 2021-12-20T12:54:23
Edited by Ghost User -
Right now it looks like it will probably not make the first service pack though (but a later one), the stable chatty 0.5 is still not out and we plan to make the first service pack in two weeks. we can't integrate it in the last minute, it would need some proper testing on edge first.
By Oliver Smith on 2022-01-04T02:38:17
-
We should release sxmo 1.7.0 before this service pack and have it in the service pack. Cc: @proycon
By Anjandev Momi on 2021-12-20T09:09:36
Edited by Ghost User
-
The backport to 3.15 for the cups fix has been merged in alpine. Would it be possible to include !2795 and !2799 (enable printer panel in GNOME Settings) in the service pack after they have been tested a bit in edge?
By Pablo Correa Gomez on 2021-12-29T12:29:59
Edited by Administrator
-
As discussed, assigning Martijn. We plan to have it done in calendar week 02.
CC: @anjandev, @proycon
By Oliver Smith on 2022-01-07T11:46:02
Edited by Ghost User -
sxmo 1.7.0 MR for edge is now open: https://gitlab.postmarketos.org/postmarketos/pmaports/-/merge_requests/2827
By Maarten van Gompel on 2022-01-07T11:46:02
-
Before the weekend is over, I will be making a PR for N900 re-inclusion, per https://gitlab.postmarketos.org/postmarketos/pmaports/-/merge_requests/2814#note_799431559
By Sicelo on 2022-01-07T19:26:04
Edited by Ghost User -
I think before we add it to the SP1, it needs to undergo the same level of testing that other devices in the stable release went through: #1331 (closed)
You can find the template that was used for testing here: https://wiki.postmarketos.org/wiki/Kernel_upgrade_testing#Stable_release_testing
By clayton craft on 2022-01-07T08:18:36
-
Okay.
Regarding the order of steps I need to follow for the N900, do I start by making a 'reinstatement' PR to the SP1 branch, then test images it generates (from reading #1331 (closed), sounds like they get generated automagically?)?
I'd appreciate if someone can spell out all/most of the steps in order, so hopefully everything gets done properly and in time for the SP1. Hope I'm not asking for too much :)
By Sicelo on 2022-01-07T15:57:18
Edited by Administrator -
we always merge to edge/master first, then cherry pick patches to stable branches. so I recommend doing this (in order):
-
make a MR to move N900 back to community, target the
masterbranch -
ping @MartijnBraam when that is merged, since I don't see a v21.12.1 branch yet. if one is created soon, then you can make a MR adding the N900 + dependencies (kernel, etc) to the that branch (not v21.12).
-
after it gets backported to the v21.12.1 (SP1) branch, build/flash an image and start testing
I'm not sure if images will be made automatically for testing the SP1 release before it is out. We do that for the major release because a lot has changed... (@MartijnBraam?)
In the interim, you can also start doing some of the testing on edge to make sure thing work. not a whole lot has changed on edge since v21.12 was released, so if things work on edge they should work on the SP1 (in theory, it's always good to go back and test with what will actually be in SP1 when the N900 is added back in)
By clayton craft on 2022-01-07T19:25:59
-
-
Thank you so much for the explanation. Luckily for me, at least in edge, the N900 had not been moved out of community just yet.
So I guess I will do edge testing in the meantime, and wait for the SP1 branch to appear.
By Sicelo on 2022-01-07T19:41:13
Edited by Administrator -
I've created the v21.12.1 branch, so you can make a merge request with all the great n900 related changes against it :)
Regarding images, they will not be built before the service pack is released usually. I guess in case of the N900 we should try to make one available before we announce the service pack, but that's something the core team needs to handle and you don't need to worry about it (merge big service pack MR, configure bpo to build it, wait until it is built, release blog post).
So in summary, please make a merge request with all n900 related changes against v21.12.1, and then build a test image from that branch with pmbootstrap, and verify that everything works as expected. Then note in the MR that everything has been tested.
It's really awesome to have it back in SP1, thanks for all the work you did on this @sicelo!
By Oliver Smith on 2022-01-09T12:02:15