On Mar/22, Helmut Grohne wrote: > Uhm. Maybe you could talk with upstream about this???
Upstream won't be available till mid-April at least. > Your workaround will not fix the problem, so you cannot close the bug. I don't intend to; did I say somewhere that I would ? > There is no requirement to fix bugs like this as soon as possible. There is: fairly large playlists, combined with the default mpdcron.conf that ships with the package, yield that bug, thus making mpdcron unusable. The workaround I described will limit the scope of this bug's, and we do want that. Well, *I* do. > It would be much better to go the slow path and come up with a proper > solution. It will come in its own time, but as it'll require introducing a totally new way for the mpdcron daemon to communicate data to its hooks, I am not about to do that just now without talking to the upstream author. --Seb -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
