bluealsa: fix signature after .rc change in March (Tim Biermann)

bluealsa/.signature

@@ -1,7 +1,7 @@
 untrusted comment: verify with /etc/ports/contrib.pub
-RWSagIOpLGJF37OPJrNTjQsSiTbIQXTyyLHke7Rda+jyA/wzhsLf4A03UKQ0nquGOfuXF3wESfXuJh6esN+xxMsGUA2Q/v8HpAI=
-SHA256 (Pkgfile) = d0ebdf5fc14ecf90bd861eb17967161d280f9f1c2e68d7fa0daae1319f4625c2
+RWSagIOpLGJF38YxRpx+tzjUN6UTC53aaLlaM4M8rwkJEzELnDHWBjwM/ZjPwiHHOBHpdA3lIq7Swg8tIyGfZBjfKgajafoFWA0=
+SHA256 (Pkgfile) = b3190896049eb1c6418477aad021e5fd92dd0e7164c94f81aa5fec8e71501ee0
 SHA256 (.footprint) = a1ec2cab3b6db9ed7c973fec4a346d4cc1f1a489618664a156bfa4f19d1d49bd
 SHA256 (bluez-alsa-3.0.0.tar.gz) = 8b9bc36be922c10c6628ddf84b13dfadfeb3ab0bcf72bad842c66f3120abc6b2
-SHA256 (bluealsa.rc) = 4dc58ddb3cd97103ab17fbe82269a7a313e4a552eece97a8aafe147d65ab36cf
+SHA256 (bluealsa.rc) = 2d16433ea5be38ca5d14d628c8ef12022d8c18dd509d49e7fc8460550fbb3efa
 SHA256 (bluealsa.conf) = 85751bb2dbda79b22ce4572e2165dcb0843e292676a781db2c2a5bcc60f840b0

bluealsa/Pkgfile

@@ -8,7 +8,7 @@
 name=bluealsa
 rname=bluez-alsa
 version=3.0.0
-release=2
+release=3
 source=(
    https://github.com/Arkq/${rname}/archive/\
 v${version}/${rname}-${version}.tar.gz

bluealsa/bluealsa.rc

@@ -19,7 +19,8 @@ stop)
 		--exec "${PROG}"
 	;;
 restart)
-	"${SSD}" --status --pidfile "${PID}" --exec "${PROG}" && "${0}" stop
+	"${SSD}" --status --pidfile "${PID}" --exec "${PROG}" &&
+		"${0}" stop
 	exec "${0}" start
 	;;
 status)