Re: Missing symbols file in libc6 for loong64

Hi

On 2026-05-28 19:08:26 +0200, Aurelien Jarno wrote:
> Hi,
> 
> On 2026-05-28 09:29, John Paul Adrian Glaubitz wrote:
> > Hi Miao,
> > 
> > On Thu, 2026-05-28 at 15:09 +0800, Miao Wang wrote:
> > > 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.
> > 
> > Good catch!
> > 
> > > 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.
> > 
> > That will warrant a rebuild of the affected packages.
> > 
> > Let's ask Aurelien what he thinks!
> 
> I do not really see what a rebuild would bring. That will indeed lower 
> the dependency, but the current dependency is already satisfied in 
> forky, and there is no trixie for loong64.
> 
> Anyway that's a decision for the release team, putting them in the loop.

Sorry for the delay. As this effectly does not change anything, I don't
think we need those rebuilds.

Cheers