On Wed, 18 Jan 2023 20:10:17 -0000 John via Replicant <[email protected]> wrote:
> Hello, Hi, > Can anyone please provide info how to build Replicant 6? The > documentation seems outdated (I have reported that in the tracker). The bug seems to be that one: https://redmine.replicant.us/issues/2329 I'll reply here because it's better to discuss it here, because even if technically it's a bug but the reason is a bug is another one (it'll be clarified below). > In dependencies installation: > > https://redmine.replicant.us/projects/replicant/wiki/Replicant60BuildDependenciesInstallation > > I see Debian 9 (stretch) - an old, discontinued OS. Unfortunately we don't know how to build Replicant 6.0 with another distribution. And this is a bug because Debian 9 isn't certified by the FSF (bug #1861 [1]), not because Debian 9 is outdated. We've tried to build it with Trisquel instead (because it's certified by the FSF) and I got close but It still need work. > Unfortunately, some of the dependency packages don't seem > to exist on Debian 11: eclipse-jdt, libandroidsdk-ddmlib-java, > libandroidsdk-sdklib-java and one more. I've tried the same approach than you already (for making the build work on an FSF certified distribution) and the biggest issue is that some of the Java packages were removed from more recent distributions, because they were abandoned, unmaintained and project using them were adapted to use newer replacement for these abandoned packages. Basically Replicant 6.0 needs an older distribution because Replicant 6.0 is based on Android 6.0 / LineageOS 13 which are unmaintained. So the real fix is to make Replicant 11 work for real. And I was funded by NLnet port Replicant to Android 11, with the Galaxy SIII (GT-I9300), but I spent way too much time trying to make the modem work (and it works but not everything is integrated properly), and a lot of things are still needed to have something really usable. So I've now applied for funding to add support for the Pinephone to Replicant 11 in a way that is reusable (the plan is to reuse GLODroid code and make it reusable by other Android distributions as well), to reuse some of this code on the Galaxy SIII, and then to get back at finishing the work of the Galaxy SIII and make sure that some of the work is also reusable by PostmarketOS. Assuming that I get funded, this means that unless/until people add support for the other phones in upstream Linux, we still need to be able to build Replicant 6.0, at least to continue testing modem related changes. As for building Replicant 6.0, I should probably document that better, but after installing the debian-keyring packge, I installed Debian stretch in a directory with debootstrap. I then used virtmanager with libvirt lxc to run it. It should be possible to setup the "libvirt LXC VM" in a way that doesn't require networking once the initial installation is done, as it is possible to share directories between the host and the "VM", so the repo sync can also be done on the host. Though having SSH inside the VM is very convenient, especially because virt-manager console is really fragile. I build releases without networking so we know for sure that at least building work fine without networking. References: ----------- [1]https://redmine.replicant.us/issues/1861 Denis.
pgpnae_wx8UOr.pgp
Description: OpenPGP digital signature
_______________________________________________ Replicant mailing list [email protected] https://lists.osuosl.org/mailman/listinfo/replicant
