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

install alsa-utils (needed for buster lite) #1471

Closed
wants to merge 3 commits into from

Conversation

t0b3
Copy link
Contributor

@t0b3 t0b3 commented Aug 9, 2021

#1255 misses the alsa-utils package that is needed make it work on buster-lite
see #1467

t0b3 added 3 commits August 9, 2021 13:48
MiczFlor#1255 misses the alsa-utils package that is needed make it work on buster-lite
see MiczFlor#1467
needed for ci tests
@s-martin s-martin requested a review from pabera August 10, 2021 19:55
@s-martin s-martin added bug future3 Relates to future3 development labels Aug 10, 2021
@pabera
Copy link
Collaborator

pabera commented Aug 21, 2021

Thanks @t0b3 for this .. What is this specifically for? I am testing this script just like this on Buster lite and I don't have any issues.

@pabera pabera requested review from arne123 and a user August 21, 2021 22:15
@t0b3 t0b3 closed this Aug 22, 2021
@t0b3 t0b3 deleted the patch-3 branch August 22, 2021 09:58
@t0b3 t0b3 restored the patch-3 branch August 22, 2021 10:57
@t0b3
Copy link
Contributor Author

t0b3 commented Aug 22, 2021

This PR ports the fix #1467 to future3. ALSA is usually preinstalled except for buster-lite docker images (as mentioned in #1255).
alsa-tools was introduced by mistyping instead alsa-utils was the package being needed.

@t0b3
Copy link
Contributor Author

t0b3 commented Aug 22, 2021

obviously the wrong ci test where executed, therefore I recreated the PR #1471 with this new branch name future3/... so follow #1485 instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug future3 Relates to future3 development
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants