> According to the documentation, only Ubuntu developers may do that directly.
Then perhaps contact an Ubuntu developer such as myself that is also on the Debian Multimedia Team? >> What *should* happen here is that musescore should become a transitional >> dummy package to >> musescore3 and not completely removed. > this >No, this is about the *source* package, not the binary package. > >The binary packages musescore and musescore-common are now built from >src:musescore2 and the binary >packages musescore3 and musescore3-common are >built from src:musescore3 so this is really about >removing src:musescore >only, as it’s a source package with no binary packages. A source package is required to make a binary dummy transition package in Ubuntu (I did this with the transition from ubuntustudio-controls to studio-controls). I can do this as it's part of the Ubuntu Studio packageset, but I cannot remove the source package once that is done, nor should we. In Ubuntu, we don't simply remove source packages unless they're FTBFS. You might do that in Debian, but that's not the way we do things here necessarily. -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to musescore in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1904060 Title: Please remove the musescore source package (renamed to musescore3) from hirsute and newer Status in musescore package in Ubuntu: Triaged Bug description: src:musescore has been renamed to src:musescore3 in Debian. The renamed package is newer and already part of hirsute, so src:musescore should be garbage-collected in hirsute and newer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/musescore/+bug/1904060/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
