Re: Missing symbols file in libc6 for loong64

Hi,

> 2026=E5=B9=B46=E6=9C=8823=E6=97=A5 04:02=EF=BC=8CSebastian Ramacher =
<[email protected]> =E5=86=99=E9=81=93=EF=BC=9A
>=20
> Hi
>=20
> On 2026-05-28 19:08:26 +0200, Aurelien Jarno wrote:
>> Hi,
>>=20
>> On 2026-05-28 09:29, John Paul Adrian Glaubitz wrote:
>>> Hi Miao,
>>>=20
>>> 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.
>>>=20
>>> Good catch!
>>>=20
>>>> 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.
>>>=20
>>> That will warrant a rebuild of the affected packages.
>>>=20
>>> Let's ask Aurelien what he thinks!
>>=20
>> I do not really see what a rebuild would bring. That will indeed =
lower=20
>> the dependency, but the current dependency is already satisfied in=20
>> forky, and there is no trixie for loong64.
>>=20
>> Anyway that's a decision for the release team, putting them in the =
loop.
>=20
> Sorry for the delay. As this effectly does not change anything, I =
don't
> think we need those rebuilds.
>=20

I can see from the build logs that packages are getting expected =
dependencies since
2026-06-21 23:29:07

Cheers,

Miao Wang