Hi Thorsten, Thorsten Glaser <t...@mirbsd.de> writes:
> John Scott dixit: > >>It's been a little while. Do you still plan on working on this? > > Yes, as time permits. I’m even keeping my ear on a possible > inofficial (as the new Muse Group management is disinterested) > 3.7 which is accumulating over a hundred fixes still. I’m > still wary of the regressions relative to 3.2 though which > I fear will require a nōntrivial amount of original work on > my side. > Furthering our discussion on IRC, if necessary, I'm interested in helping out with updating Musescore3 later this summer. There is also notable interest on IRC in #debian-quebec for seeing this package updated :) and also sadness at being forced to use upstream's AppImage, in cases where 3.2.3+dfsg2-11 proves insufficient. In an earlier update you mentioned that there were numerous regressions and problems with these new releases. Are these limited to non-dfsg components (such as instrument samples) that need to be replaced, and are there too many problems that it would make sense listing them? Would it be useful to start a Musescore team to divide the workload, assuming that it's divisible? I'm guessing it's something painful like tracking down many non-dfsg things before being able to important the new upstream orig.tar. Regards, Nicholas
signature.asc
Description: PGP signature
