http://bugzilla.opensuse.org/show_bug.cgi?id=992519
http://bugzilla.opensuse.org/show_bug.cgi?id=992519#c28
--- Comment #28 from Simon Lees
(In reply to Simon Lees from comment #26)
It, itself is still not a bug, your locking the wrong thing, as far as I can see nothing requires yast2-qt-branding-openSUSE so why don't you remove and lock that instead?
# zypper rm yast2-qt-branding 2 additional packages to remove: yast2-theme yast2-x11
Seems to me that would mean no GUI YaST2, one of, if not the, openSUSE traditionally top feature/attraction/selling point.
That didn't happen here, maybe because I have other yast branding packages installed or maybe something changed (I checked on my leap machine)
And what about the others in the bug 1153854 attachment?:
gtk3-metatheme-adwaita requires cantarell-fonts
This is perfectly acceptable if someone designs / tests a specific theme around a specific font they should be entitled to require it. Last time I checked there are other gtk3 theme's available so you should be able to use one of them. If a non branding package explicitly requires gtk3-metatheme-adwaita then that would be the bug.
plasma5-integration-plugin requires hack-fonts and noto-sans
Without being a KDE developer and understanding why they might have such requirements (maybe something breaks without them). For font's I don't think we have a mechanism like we do for display managers where by a font can say it provides say "monospace-font" and then some package can require "monospace-font" and be happy with anything marked as such, if your interested in putting work in here to implement this I can help you, bug because related to the size of a desktop or toolkit the size of a font isn't massive so force including one font hasn't been seen as a big issue. If you are passionate about seeing this changed its not hard it'll just take a little bit of time and effort and would be a good beginner developer task.
Any font should be no more than suggested or recommended, unless functional loss would result from a particular font package's absence, such as might occur (?) with postscript/ghostscript/pdf apps.
Are you suggesting this or bug 1153854 should be a metabug and bugs specifically against yast2-qt-branding-openSUSE, gtk3-metatheme-adwaita and plasma5-integration-plugin are the appropriate path to take? Bug 1153854 is about apparent policy that allows hard requires of any specific font rather than any generically compatible font.
The bug shouldn't be against yast2-qt-branding-openSUSE but against yast2 for not shipping a yast2-qt-branding-upstream creating such wouldn't be hard but whether someone actually feels like implementing it is another question, but if you felt like maintaining it, it wouldn't be hard and no one should block you and I could help you get started or I could help you create a yast2-qt-branding-felix package if you want that would take even less time and should be even easier to maintain seen as you are the only one who strongly wants this. -- You are receiving this mail because: You are on the CC list for the bug.