Package: musescore
Version: 3.0.3+dfsg1-1
Severity: wishlist

Hello,

shortly after the release of buster as stable, I upgraded my box from
buster to bullseye. I was kind of shocked to discover that musescore was
marked as "obsolete or locally created", i.e. not present in bullseye.
It took me some time to notice the package renaming from "musescore" to
"musescore3" and to find the right piece of changelog documenting it:

  * Rename binary packages to musescore3{,-common} for coïnstallability
    (musescore{,-common} 2.x will stay around for buster’s lifetime, and
    upstream says users should have both in parallel, for existing
    scores)

(from 3.0.3+dfsg1-1, thus the Version: command above)

Now, I understand the reason for the change and have no problem myself
with the renaming and with installing a new package. I suspect, though,
that I wasn't the only user left in the cold and I wonder how many of
them know where to look to solve this. Could something be done, at least
to better document the change and suggest a solution?

Hopefully, at least, people will happen to read this bug and thus find
their way out :-)

Thanks for the great work!

Regards,
Gabriele Stilli

Reply via email to