Am Thu, 12 Jan 2017 16:32:53 +0100 schrieb Fabian Greffrath <fab...@debian.org>:
> Well, strange! I was just going to reproduce this issue on my own > testing/unstable system, but -- although I am using the fonts from > fonts-texgyre as substitutes for the base fonts -- I am not able to > reproduce this bug. > > Well, there are 22 revisions between the poppler versions in stable > and testing, so I assume the bug has been fixed in between (it has > not been fixed in the fonts-texgyre package between stable and > testing, I have checked that). > > So, not sure what to do with this bug report then... well. since the problem as you found out seems not to exist on testing/unstable the remaining question is about what to do on stable. hm. i think not many people have fonts-texgyre installed on stable. otherwise this bug would be triggered by a lot of people maybe. So one could argue this is an important bug if fonts-texgyre is installed, and no bug if that package is not installed. I do not know what debian policy says about such a problem regarding the possible fixes on stable :-) I think poppler cannot be fixed on stable. maybe fonts-texgyre could be removed from stable or the "wrong" font removed from fonts-texgyre or added with different name and README.Debian sais due to bug xxx you have to rename it manually to use that font. Hm. Simply doing nothing is also not optimal. As for me the system worked fine and one day I installed fonts-texgyre probably due to a maximum tex installation and then suddenly many things broke regarding the micro sign. Dunno.
