<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi maintainers,<br>
</p>
<p>On Wed, 17 Jan 2024 19:35:24 +0000 Simon McVittie <smcv@debian.org>
wrote:</smcv@debian.org></p>
<p><smcv@debian.org></smcv@debian.org></p>
<smcv@debian.org>> Control: block -1 by 1051323<br>
> <br>
> On Wed, 17 Jan 2024 at 12:58:07 -0500, Jeremy Bícha wrote:<br>
> > On Thu, Dec 14, 2023 at 7:24 AM zhangdandan <zhangdandan@loongson.cn>
wrote:<br>
> > > The gnome-initial-setup source package lacks
LoongArch architecture support.<br>
> > > We need to enable PARENTAL_CONTROL for
loongarch64.<br>
> > ><br>
> > > Please consider the patch I have attached.<br>
> > <br>
> > I do not believe this change makes sense until
malcontent is built on<br>
> > loong64. Please ask again then.<br>
> <br>
> malcontent requires flatpak, which requires libseccomp,
which requires<br>
> architecture-specific porting and is not available on
loong64.<br>
> <br>
> After resolving that, there is a cyclic build-dependency
between<br>
> malcontent and flatpak. To break the cycle, you will need
to build<br>
> malcontent on loong64 with the pkg.malcontent.nogui build
profile, then<br>
> use that to build flatpak, and then you can rebuild
malcontent with<br>
> full functionality. This sort of thing is a normal part of
the process<br>
> of bootstrapping new architectures.<br>
</zhangdandan@loongson.cn></smcv@debian.org>
<p><smcv@debian.org><zhangdandan@loongson.cn></zhangdandan@loongson.cn></smcv@debian.org></p>
flatpak has been available on loong64 since 26, March. Please review
<br>
<a class="moz-txt-link-freetext" href="https://buildd.debian.org/status/package.php?p=flatpak&suite=sid">https://buildd.debian.org/status/package.php?p=flatpak&suite=sid</a>.<br>
<br>
Please add loong64 support in next upload.<br>
<br>
Best regards,<br>
Dandan Zhang<br>
</body>
</html>