Closed andrewn closed 1 year ago
This looks good to me. I had considered whether we should bump the final container up to alpine:3.16-run
as well, but if it's not broken don't fix it, as the motto goes. I think it makes sense to leave it like this where we know the package versions work.
You can add Fixes: https://github.com/balena-labs-projects/balena-sound/issues/589#issuecomment-1310072186
in your post body for this PR and it will link the two together, and close the issue when we merge it.
I haven't got the capacity to test this out, but we trust you. Are you happy for this to be merged, and to take the heat from the BalenaSound community if they come knocking? ;).
You can add
Fixes: https://github.com/balena-labs-projects/balena-sound/issues/589#issuecomment-1310072186
in your post body for this PR and it will link the two together, and close the issue when we merge it.
I think that also works by including the issue number in the PR title (or a commit).
I haven't got the capacity to test this out, but we trust you. Are you happy for this to be merged, and to take the heat from the BalenaSound community if they come knocking? ;).
Well, it works for me, and it's currently totally broken in the latest release so I guess we can give it a go 😄
Spotify playback is broken in librespot 0.3.1 and depending on tmigone/librespot:0.3.1-pulseaudio means we can't easily upgrade to the latest version.
Building within the project allows us to choose which version is tracked by balena-sound, as suggested here.
I pushed this to a balena device and it builds correctly and plays Spotify.
Fixes #589