04-25-2022, 03:53 AM
It's 'potentially unsafe' because it hasn't come from a known repository so can't be checked for a valid signature or checksum by the package manager. Anyone could make a package claiming to be icecat and make it available for download, but unless they were using a repeatable build system (which most don't) it's hard to be sure that the binary was build from the source it claims it was, was modified somehow, or is a flat out trojan. If it _was_ built with a repeatable build system then you need to build it yourself to check. In your case you've made it from a different package format from another reputable source, but the package manager doesn't know that so it gives you a warning.
The workaround described at https://www.jertype.com/upgrading-glibc/ might work if you're lucky with the rest of the dependencies, but that page notes it's not a preferred solution.
I hadn't previously spotted the docker images Mobian provide for easier crossdev packaging:
https://gitlab.com/mobian1/wiki/-/wikis/Crosscompiling
The workaround described at https://www.jertype.com/upgrading-glibc/ might work if you're lucky with the rest of the dependencies, but that page notes it's not a preferred solution.
I hadn't previously spotted the docker images Mobian provide for easier crossdev packaging:
https://gitlab.com/mobian1/wiki/-/wikis/Crosscompiling