# wontfix works-as-intended close 933599 thanks Hello Gabriele,
>It took me some time to notice the package renaming from "musescore" to >"musescore3" and to find the right piece of changelog documenting it: I’m sorry this took you some time; if you have any idea of how to do that better, other than an entry in the bullseye release notes which will be published in two years, please share. >them know where to look to solve this. Could something be done, at least >to better document the change and suggest a solution? I can’t think of any (otherwise I’d have implemented it). That the existing musescore binary package continues to provide a working MuseScore 2.x is deliberate, and I was even considering keeping it around for bullseye as well but then I’d have to support it within Debian until 2023 or longer, which at that time I felt not ready to without help from upstream (who have told me they can only sup‐ port the latest release, so no). I’m providing private musescore2 builds for those who need it and will update them should that be necessary due to Qt changes, that is, if the buster binaries no longer work. I feel it is still im‐ portant that users can have both versions available (though the 3.2.3 release feels stable enough again, a first for the 3.x se‐ ries). >Hopefully, at least, people will happen to read this bug and thus find >their way out :-) I’d rather they read the release notes… well, in two years. An “apt-cache search musescore” will easily show the binary package name to install though, and the installation instructions for Debian on the upstream website in the Handbook are also up-to-date. As I said, if you have concrete suggestions of what else could be done, do share them, otherwise… *shrug*. Sorry about that, //mirabilos -- [16:04:33] bkix: "veni vidi violini" [16:04:45] bkix: "ich kam, sah und vergeigte"...
