On 2022-02-28 18:12:27, Ian Jackson wrote: > This bug came to my attention as a user of mplayer, due to the testing > autoremoval which is the consequence of an RC bug. > > I tried Sebastian Ramacher's suggested alternative of `mpv` and, > speaking entirely personally, it would do OK for me as a replacement > for mplayer. It seems to have many of the same advantages over other > programs (eg vlc), for me. > > But: > > I have to say that I found the original report in this bug rather > unfriendly in tone. Removing things is usually regrettable - at the > very least, there will usually be people who are going to be upset. > And an RC bug like this has very high visibility and will draw the > attention of people without much of the context.
As I am effectively its last maintainer, the original bug report describes mplayers state in Debian: it is not maintained. And it hasn't been since 2018 (or even 2016 which saw the last maintainer upload). > A message which was kinder about mplayer, and which more positively > spoke of the advantages of mpv, would have avoided darkening my day > today. > > > I had a look at the bug list in Debian and it doesn't seem to have > insuperable problems. I'm not able to commit substantial amounts of > time but I wouldn't want this package to fall out of Debian just > because no-one with the appropriate permissions is available to > support people who want to do the actual maintenance. So I hereby > volunteer to sponsor uploads. > > It seems to me that at #1004579 (ffmpeg 5.0) and #939032 (giflib) > would need to be addressed, and #958865 (crash on theora) really ought > to be fixed too. If we had a maintainer who is able to deal with > those, and also deal with some of the outstanding bug gardening, then > we could conclude that mplayer ought to stay. Please feel free to take over. Cheers -- Sebastian Ramacher