Bug#970635: moosic: not Python-3-compatible, so due for removal

2020-12-23 Thread The Wanderer
Thinking about this again, I feel I should note for your awareness when it comes to packaging that the primary things I'm concerned about on upgrades are already-running daemons and existing playlist files. I don't remember to what extent I tested this when I did the original porting work back in

Bug#970635: moosic: not Python-3-compatible, so due for removal

2020-12-22 Thread Arto Jantunen
The Wanderer writes: > retitle -1 moosic: new upstream version works with Python 3 > thanks > > > I've decided it's worth the effort to become the new upstream for this, > and confirmed with the original author that he has no objections, as he > is no longer spending any time maintaining it. > > V

Bug#970635: moosic: not Python-3-compatible, so due for removal

2020-12-22 Thread The Wanderer
retitle -1 moosic: new upstream version works with Python 3 thanks I've decided it's worth the effort to become the new upstream for this, and confirmed with the original author that he has no objections, as he is no longer spending any time maintaining it. Version 1.5.7, based on Python 3 rathe

Bug#970635: moosic: not Python-3-compatible, so due for removal

2020-09-20 Thread The Wanderer
I've done some more digging, and it looks like the delay isn't related to the new version, or to moosic at all. It happens only with WAV files played by sox; my best guess is that it's a matter of how sox handles things internally, such that when it gets SIGSTOP or suchlike it (I imagine) lets a bu

Bug#970635: moosic: not Python-3-compatible, so due for removal

2020-09-20 Thread Andrew J. Buehler
Package: moosic Version: 1.5.6-1 Severity: normal Tags: patch upstream Dear Maintainer, moosic was written in Python 2, which is due for removal from Debian. A recent dist-upgrade against testing on my system wanted to remove it in order to upgrade other packages. The original moosic upstream se