vcswatch reports that
this package seems to have a new changelog entry (version
1.1.8-3, distribution
unstable) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit 0dee89e615d5bdba8c5f573aad0162b8354ad710
Author: Elimar Riesebieter <riesebie@lxtec.de>
Date: Sun Apr 14 05:27:55 2019 +0200
Release 1.1.8-3 to unstable.
commit d8e09154eb19c59ac5ea4935e8062fd33f9db621
Author: Elimar Riesebieter <riesebie@lxtec.de>
Date: Sun Apr 14 05:23:12 2019 +0200
Don't run both systemd services in paralell.
Last release started both alsa-restore and alsa-state services concurrently.
Therefore removed Fix-alsactl-to-restore-config.patch and introduced
Don-t-run-both-systemd-services-in-paralell.patch. Thanks to Michael Biebl
for the hint.
commit 83561546fa3158c0f25f8b337b581596affdbb9f
Author: Elimar Riesebieter <riesebie@lxtec.de>
Date: Sun Apr 14 04:25:23 2019 +0200
Revert "Release 1.1.8-3 to unstable."
This reverts commit 5b5b498b3f4ad46dad1d210a5e64e62eb3c4df29.
commit 5b5b498b3f4ad46dad1d210a5e64e62eb3c4df29
Author: Elimar Riesebieter <riesebie@lxtec.de>
Date: Wed Apr 10 14:06:18 2019 +0200
Release 1.1.8-3 to unstable.
commit da4803a0c88e83a0e580c98f1474872d1f6288bf
Author: Elimar Riesebieter <riesebie@lxtec.de>
Date: Wed Apr 10 13:53:14 2019 +0200
Don't run both systemd services in paralell.
Last release started both alsa-restore and alsa-state services concurrently.
Therefore removed Fix-alsactl-to-restore-config.patch and introduced
Don-t-run-both-systemd-services-in-paralell.patch. Thanks to Michael Biebl
for the hint.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/a/alsa-utils.png){kind=link}