Bug#944323: RFS: piper/0.3-1 [ITP] -- graphical frontend for libratbag

[Stephan Lachnit <stephanlachnit@protonmail.com>]

> Right, python3 is the interpreter only, python3-dev adds a number of files
> which are necessary to build Python modules. I suspect that Piper doesn’t
> need python3-dev, and its meson.build could be changed to avoid that
> build dependency...

Will try it out and send a patch to upstream.

> With the latter approach, non-breaking versions of ratbagd can be uploaded
> without requiring a new upload of Piper. If ratbagd breaks Piper, upstream
> will release a new version of Piper anyway, which would require an upload.

Sounds good to me.

> If you don’t have anything left to do on the package, I can upload it for
> you, and create the repository on Salsa in the debian namespace.

I'm finished with it. Latest version on mentors from today is the same as the last one, the one in between was just a test for me.
Just one more technical question about maintaining the package: how exactly is this going to work? I guess it's not done by just updating/tagging the git repo.

Regards,
Stephan