Adding the testing repo is a really, really BAD idea. As the name implies these packages are still being tested. Enabling testing and doing an update/upgrade is a great way to end up with a severely broken system sooner or later. It's OK to enable it to install specific packages but be sure you disable it again afterwards.

Adding the testing repo is a really, really BAD idea. As the name implies these packages are still being tested. Enabling testing and doing an update/upgrade is a great way to end up with a severely broken system sooner or later.

So don't do that! I like to see what's available and so for sure I have the testing repo enabled. If you look at the Common tab in GSlapt for a program you've highlighted, in the Source line it tells you where the file is located. If it says http://vectorlinux.osuosl.org/veclinux-5.9/testing/ or anything similar, that's a red flag to me to be sure I know where it's coming from and the implications of that (could be risky and might break things). I generally don't install updates from /testing unless I know for sure that I want something and am willing to assume any risks.

I ALWAYS check what repo files are coming from before I install them.--GrannyGeek

No, it has nothing to do with the repo. It has everything to do with the upstream developer. The Indic fonts package is originally a Slackware package. Sadly, while I did build the package I do not speak or read any Indian language so I had no way to know whether or not there are any issues with the fonts. It's in testing so that someone like you could tell us if it is a good package or not. I take it that it is NOT a good package. Is that correct?

I think it would score 10 or 15 out of 100 marks. I could guess some of the words and some of them appear to be alien in the URL posted by me in this. You know something! I'm very very interested in linguistics (and also in open community) that made me search for Indic fonts.