I am sorry. The built has been done, but I didn't know that. The build was outside the current folder/directory. The packages I have got from the local build are: gjs_1.86.0-3_arm64.buildinfo gjs_1.86.0-3_arm64.changes gjs_1.86.0-3_arm64.deb gjs_1.86.0-3.debian.tar.xz gjs_1.86.0-3.dsc gjs_1.86.0.orig.tar.xz gjs-dbgsym_1.86.0-3_arm64.deb gjs-tests_1.86.0-3_arm64.deb gjs-tests-dbgsym_1.86.0-3_arm64.deb libgjs0_1.86.0-3_arm64.deb libgjs0-dbgsym_1.86.0-3_arm64.deb libgjs-dev_1.86.0-3_arm64.deb
And now I am doing the same thing with mozjs140: $ sudo apt build-dep mozjs140 $ apt source mozjs140 $ cd mozjs140-140.6.0 $ dpkg-buildpackage -us -uc -nc I hope everything will go easy. Thank you. On Sun, 2026-01-18 at 23:59 +0100, NoisyCoil wrote: > On 1/18/26 23:53, Sally A.haj wrote: > > Hi NoisyCoil, > > > > Thank you for you response. > > I have tried to reverse back to the previous release libmozjs-140- > > 0_140.5.0-1_arm64.deb, but that will remove almost the whole gnome, > > so > > I stopped. Here what happened when trying to downgrade > > https://0x0.st/PKjR.txt > > Oh, sorry about that, that didn't happen the last time I tried, it > seems > the dependency on the binNMU has been declared since then. Then I > guess > what you can do is rebuild the current gjs in unstable or testing, > and > then install the resulting libgjs. Can you do that? > > > Do we need to report this issue or this report is enough for that? > > No I don't think so, the GNOME maintainers are already aware of this > issue. > > > Regards, > > Cheers!
