backport !pipewire-pulse dependency added to phosh (!2890; assuming it lands in edge fast enough and has some testing there, otherwise do it in the next service pack. this prevents a bug of switching to pipewire by accident and having half-broken audio by accident when installing other packages/upgrading them)
backport phosh 0.15.0 from edge? (has some nice visual improvements, non-numeric password support, and bug fixes, runs well for me)
maybe pure-maps 2.9.0 to fix failing connection to osmscout-server (not sure if this actually fixes it, make sure to test this; if this is too much for SP 2, let's move to SP 3)
@mikebdp2 note that you can just force-push your branch (git push --force), that's better than closing and opening new MRs. Thanks for submitting these patches though!
After my mistake in the last service pack, I thought it might be best to make a utility that checks all the packages in alpine and gives pmOS a list of packages that might need to be backported.
You guys might find it useful to track other packages that you might want to track. I thought of building this into pmbootstrap but I think that would be feature creep. Additionally, we might want to add functionality to this script to make backporting easier (ie. copy files over automatically, remove maintainer/contributor, add comment, etc.). Does pmbootstrap have this feature already?
Regardless, if Im not available, you guys have a script replacement of me =D. Please let me know if I should document this script somewhere so people preparing the service pack know about it.
$ ./apkbackport-helperMake sure your master and 3.15-stable branches are up to date on /home/user/code/aportsMake sure your v21.12 branch is up to date on /home/user/code/pmaportscommunity/sxmo-utils have diff pkgver in 3.15-stable and edge consider backporting to pmaports v21.12
Nice, thanks for writing this!
Does pmbootstrap have this feature already?
pmbootstrap aportgen --fork-alpine $pkgname
It removes maintainer and contributors, but adding a custom comment is not possible yet (could be useful though).
I don't think we need to tie this into the script though, just having the information of what packages need to be copied is very useful already.
So I'd suggest somebody from Sxmo still tells us in these service pack discussion issues, what you would like to have backported, and we add it to the list in the top post. The idea is that packages in edge get tested for some time, before they land in a service pack - so if an Sxmo related package gets changed just before we prepare the service pack, we would include it even though it did not get much testing if we just ran the script every time and backported everything it outputs. Or maybe you have a bigger change that you want to test / iterate upon (e.g. a big rewrite) for more than a month and we should not backport for a little longer.
Not sure if it's clear btw, so let me repeat this here:
important bugs that have clear fixes without much risk can be backported pretty much immediately, or after short testing, after they went through edge
service packs are for features or for bug fixes that come along with more severe changes
So it's your call to make, we can either put this in a service pack, or if you say it's a really annoying bug that you'd rather have fixed now, and you are confident that the patch doesn't need more testing (has been in edge a bit), it could also be backported now (i.e. open a MR towards v21.12 now, and we can merge it once it builds and looks good).
The latest version of sxmo (1.8.0) should be in this service pack, it is a major change requiring manual intervention. The issue description says 1.7.0. Sxmo 1.8.0 has been in edge since (2022-01-29 15:11:02). The blog post with the service pack with this Sxmo should mention the following:
Sxmo 1.8.0 requires manual intervention! With 1.8.0, the configs for dwm and sway have been changed significantly. Users should backup their old configs with mv ~/.config/sxmo ~/.config/sxmo.old and reboot. The default configs are available in /usr/share/sxmo/ and users must manually merge their old configs (sway/dwm configs) located in ~/.config/sxmo.old with the default configs. The main change required should only be the new location of "sxmo.swaysock" in your sway config if you're using sway.
WAITING FOR PROYCON'S RELEASE NOTES
Feel free to cc me and I will check the blog post over alongside the service pack MR.
Here is a list of packages that need to be backported from aports for Sxmo 1.8.0:
Thanks! I'll make sure we include this in the blog post. Since it turned out that this was not a trivial backport, we can't merge it right away as you figured and this will be part of the service pack then. Would you mind adding the other Sxmo packages that need to be upgraded as well to the merge request?
yep. to be clear, for who ever ends up doing the SP2 release, you just need to backport Chatty 0.6.0. Other required components (mmsd-tng) are already in the stable release.
Not sure if this kind of stuff is to be put into service packs, but I would suggest backporting OSM-scout-server from edge. The current version on v21.12 doesn't actually work #1099 (closed)
I have confirmed it working in currenct edge.
osm-scoutserver is the same version in alpine edge and alpine 3.15 (on which v21.12 is based).
However, pure-maps is newer in edge; 2.9.0 (edge), 2.8.0 (v21.12). That might fix it.
We already have a lot for the service pack and it's scheduled for next week already, not sure if we can squeeze in that as well, but I'll add it to the list above as maybe. Thanks for the suggestion @JulianGro!
Hm. If it's the same version then the problem must be something different. Because I am definitely running into the same problem as #1099 (closed) or rather I run into the same symptoms.
Whatever the issue is, it seems to be fixed in Edge though.
@craftyguy the issue isn't solved, but Pure-Maps runs.
Also I am not getting thumbnails for Pure-Maps or OSM-scoutserver-gui which I always got before, but I assume that must be unrelated.
Administratormarked the checklist item chatty 0.6.0 upgrade (already in edge) as completed·
Imported
marked the checklist item chatty 0.6.0 upgrade (already in edge) as completed
By clayton craft on 2022-02-02T20:24:57
Administratormarked the checklist item backport phosh 0.15.0 from edge? (has some nice visual improvements, non-numeric password support, and bug fixes, runs well for me) as completed·
Imported
marked the checklist item backport phosh 0.15.0 from edge? (has some nice visual improvements, non-numeric password support, and bug fixes, runs well for me) as completed
By clayton craft on 2022-02-02T20:25:00
Administratormarked the checklist item also phoc latest release as completed·
Imported
marked the checklist item also phoc latest release as completed
Administratormarked the checklist item backport !pipewire-pulse dependency added to phosh (!2890; assuming it lands in edge fast enough and has some testing there, otherwise do it in the next service pack. this prevents a bug of switching to pipewire by accident and having half-broken audio by accident when installing other packages/upgrading them) as completed·
Imported
marked the checklist item backport !pipewire-pulse dependency added to phosh (!2890; assuming it lands in edge fast enough and has some testing there, otherwise do it in the next service pack. this prevents a bug of switching to pipewire by accident and having half-broken audio by accident when installing other packages/upgrading them) as completed
Administratormarked the checklist item maybe pure-maps 2.9.0 to fix failing connection to osmscout-server (not sure if this actually fixes it, make sure to test this; if this is too much for SP 2, let's move to SP 3) as completed·
Imported
marked the checklist item maybe pure-maps 2.9.0 to fix failing connection to osmscout-server (not sure if this actually fixes it, make sure to test this; if this is too much for SP 2, let's move to SP 3) as completed
Administratormarked the checklist item possibly backport samsung-serranove modem fixes? (after went through edge, see #1274 (comment 797524967)) as completed·
Imported
marked the checklist item possibly backport samsung-serranove modem fixes? (after went through edge, see #1274 (comment 797524967)) as completed