Description of problem: ms-fonts package is a dependence of mscore (Musescore) but is obsolete and causes problems. This bug affects Official and Cauldron. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Musescore 2.0.3 is now available as an Appimage package (new to me.) It has no dependencies, and can be run from its download location. I ran the Appimage under Official, and there were font errors when I exported a PDF. I reported this to Musescore. Relevant parts of that thread follow. ---- Musescore: This seems to indicate that on your system you have some MuseScore font installed. A common cause of issues like this, esp. on Linux machines, some distributions seem to erroneously install the musescore fonts, and installed once take precedence over the built in ones. Me: Yes, a Musescore fonts package is a dependency. It contains 3 files: â/usr/share/fonts/mscore/mscore-20.ttf /usr/share/fonts/mscore/mscore-MuseJazz.ttf /usr/share/fonts/mscore/mscore1-20.ttf Musescore: delete those, these are not needed at all, for no version of musescore and harm in some. ----- I uninstalled the whole Musescore 1.3 package in Official, and the problem disappeared. Apparently the package is still present in several distros, and the bug that results, is not news to the developers.
The name of the package is mscore-fonts Subject and rpm reference corrected accordingly
Summary: ms-fonts is obsolete and should be removed, not replaced. => mscore-fonts is obsolete and should be removed, not replaced.Source RPM: ms-fonts => mscore-1.3-6.mga5.src.rpm
Sorry Jim. Bug 2639 was also returned by a search, and I had been checking whether it was relevant. It relates to "msttcorefonts," and got my mind fixed on Microsoft.
CC: (none) => marja11Assignee: bugsquad => thomasSource RPM: mscore-1.3-6.mga5.src.rpm => mscore-1.3-6.mga5.src.rpm, mscore-2.0.2-6.mga6Whiteboard: (none) => MGA5TOO
We do build the fonts into a separate package and we are not the only distro doing so. Fedore says: The font files need to be separated due to the font packaging guidelines. I don't see a reason why we shouldn't do the same. Is there a problem in running the Mageia provided package. If so please provide a detailed report of the problem. If the problem is just that the upstream provided package cannot be used parallel to the Mageia provided package, then please just uninstall our package.
Yes, you build the fonts in a separate package, but they are a dependency of the mainstream package. I am not saying you shouldn't merge them in. The advice from the developers is that they aren't needed at all, and they have advised several other distros to that effect. I know to uninstall them, but until I posted to the Musescore list, I thought there was a bug in the fonts. Can't you just leave the fonts package right out? It isn't needed for 1.3, even.
For "mainstream package" I meant "main package", mscore-1.3.
Great. So why do they include them in source package. Can you test if the package runs after uninstalling the font package?
No new information on comment 6. I'll close this as invalid
Status: NEW => RESOLVEDResolution: (none) => INVALID
Who are "they"? If the result is unusable, I don't see how the bug can be invalid. But I do take your point, that the fonts are still there in the 2.0.3 tarball, and the 2.0 series will be the default version in Cauldron. If it is an "upstream" bug, say so. I said in Comment 4 that the fonts are a dependency. If I uninstall the fonts package, it takes the program package with it. I haven't been keeping up with things, but I will now take it back to the authors.
The 3 fonts I mentioned originally aren't in the "fonts" directory in 2.0.3, and Version 1 is history. The guy from MuseScore said that the fonts in the directory in 2.0.3 must be retained, and not those in mscore-fonts for 1.3. The packaging issue mentioned in Comment 3 should make no difference, only the content of the packages. From memory, despite what he claims, there was a problem only with Version 2, not Version 1. Version 2 has a lot more features, but they have been moved around the desktop so much that I can't find many of them. I need to familiarise myself with everything again. Hopefully, I am getting my "marbles" back sufficiently. I am 73, but not yet due for a nursing home. And I don't keep a log.
Well, we have mscore 1.3 in mga5 and 2.0.2 in cauldron, same with mscore-fonts.
That is what I said. 2.0.2 in Cauldron will hopefully replace 1.3 in Official. The package isn't the problem, only the 3 fonts I listed in the Description. They have been omitted from mscore-fonts in 2.0 So the whole issue should become history. I am too elderly and ill to take it any further.