Hi, Adrian I noticed that many binary packages on loong64 have a dependency to libc6 with a version constraint no lower than the latest version of glibc, which is different from other architectures, where the version constraint is derived from the actual symbol version sused in the executables. I believe that it is because of missing symbols file in libc6 for loong64.
I have opened a merge request to glibc packaging adding the missing symbols file and the merge request has been merged and is pending for upload. I wonder what should be done to existing packages which requires a unnecessary higher version of libc6. Cheers, Miao Wang
