Bug#923203: pulseaudio: fails to start without manual configuration

[Adam Borowski]

On Sun, Jun 23, 2019 at 11:13:15AM -0400, Felipe Sateler wrote:
> Control: severity -1 normal
> 
> On Fri, Jun 21, 2019 at 4:57 PM Adam Borowski <kilobyte at angband.pl> wrote:
> > Control: severity -1 grave
> 
> I don't think this issue is RC. However, I'm not interested in playing
> severity ping pong. Please involve the release team if you think the
> severity should be grave, and an update for this issue would be allowed.

I bumped the severity based on Tobias' suggestion -- I don't know what is
appropriate.  The package is currently useless for non-systemd users unless
every of them applies a fix by hand.

> > https://salsa.debian.org/pulseaudio-team/pulseaudio/merge_requests/5
> >
> > On Fri, Jun 21, 2019 at 11:37:48AM +0200, Tobias Hansen wrote:
> > > Can this still be fixed for buster? Can we make it an RC bug?
> >
> > It should have been tagged a long time ago, but I believe that's a good
> > idea.  The bug is severe -- makes the package effectively useless for a
> > part of users (those on any inits other than systemd), has a pending fix,
> > and the fix has went through maintainer's review with no comments since 3
> > weeks ago.

> Sorry about that, I interpreted "haven't tested beyond a simple install
> yet" as implying you would ping back once the testing had been done.

Oif, my fault.  Apologies.

There's not that much testing involved:
* non-systemd
* systemd
* upgrade: deleted conffile
* upgrade: intact conffile
* upgrade: modified conffile

> Reviewed again, it has a few issues (but mostly ok). I'd like long term to
> revert the order: disable autospawn by default, and have non-systemd run
> something to enable it.

Seems more complicated than the other way, but it's your shed so it's you
who gets to pick the color.  Fair enough.
 
> Honestly, I'm a bit annoyed about all this rushing. This behaviour has been
> present since 2017, and  all of a sudden this is unacceptable and needs to
> be fixed less than a month before release.

Most people don't start testing until shortly before the release.  I on the
other hand use Buster since June 2017 (and will switch to Bullseye soon)
thus upon seeing the initial regression grumbled and assumed it will be fixed
shortly, noticing it's still there only upon installing a non-server box.

You'll see the main influx of bug reports only after the release :/


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Packager's rule #1: upstream _always_ screws something up.  This
⢿⡄⠘⠷⠚⠋⠀ is true especially if you're packaging your own project.
⠈⠳⣄⠀⠀⠀⠀