Source: opusfile Version: 0.9+20170913-1.1 Severity: important Dear Maintainer,
I intend to salvage the package "opusfile", for the following reasons: - "opusfile" currently FTBFS (due to using a very outdated debhelper compat) [#965762] - multiple new upstream releases of "opusfile" have been missed - 0.11 (in 2018) - 0.12 (in 2020) - [#935591, #923031] - lacking multiarch support [#935590, #899138, #923031] - no visible packaging activity for 1660 days - the last upload by the current maintainer was 2017-10-03 - there has been a non-NMU, no-source-change upload on 2020-12-17 by the Reproducible Build teams in the meantime) - there are 7 open bug reports, ranging from wishlist to *serious* since 2017-11-15 not a single bug report has seen *any* reaction from the current maintainer. I'm aware that the maintainer of "opusfile" does not usually want to make packaging changes without specific reasons, but I don't think that this allows for completely ignoring open bug-reports of severity SERIOUS for more than 1½ year. I tried contacting the current maintainer multiple times about a year ago, but the *only* answer I ever got was "I've been afk for a bit, but I'm catching up on things again now". I'm happy with co-maintaining the package (although my stance at maintenance is definitely more aggressive with regard to updating to the latest and greatest source format, dh-compat and the like). I would more than welcome maintenance of the package under the multimedia-team umbrella. it would be great to hear something from the current maintainer of "opusfile". cheers