- User Since
- Nov 4 2022, 12:23 AM (30 w, 12 h)
Sat, May 6
I have a feeling this can be closed, seeing as there's likely not enough information to reproduce the issue, we're probably not going to get more info since it's a year old, and whatever it is may have been solved by an update since then.
I have a feeling this can just be closed, seeing as it's a year old hardware issue, it might even have been solved by kernel updates or something.
Hmm, there's some weird versioning in the tags on jitsi. The building document didn't even exist at 5633, and the only two versions tagged past that are in a different format r2.14.695 and r2.14.721, these two versions do have the build doc claiming it can use jdk11. Definitely looks like a project on the tail end of it's lifecycle though as stated previously, in the ReadMe it states:
Jitsi Desktop is the heritage of Jitsi Meet. While some components are still used in e.g. Jigasi, the project is not actively developed anymore. Improvements, bugfixes and builds are entirely based on community contributions.
Looks like the icedtea-web in the repository is now up to jdk17 and if we update to the newest version of jitsi (https://github.com/jitsi/jitsi/blob/master/docs/building.md) it is now using jdk11. We can probably update that and close this task I would think.
Fri, May 5
Apr 28 2023
Looks like it does still depend on binder, and either ashmem or (since 1.2.1) memfd (see https://wiki.archlinux.org/title/Waydroid#Kernel_Modules). I don't know if memfd is still as problematic as ashmem but I assume binder is still an issue. These two modules were previously discussed in T4904 with respect to Anbox and are part of the reason it wasn't included. I'm guessing this probably cannot be included for the same reasons.
Dec 29 2022
Made requested changes (except removing HOME_DIR=1 as that does not appear to be set by default)
Dec 28 2022
Properly alphabetized deps, cleaned up patches, build, and install
Dec 20 2022
Dec 18 2022
Dec 12 2022
Dec 10 2022
Dec 9 2022
That does look much neater
Ok, no problem, I'll add those!
Dec 8 2022
Do I need to add that link in the summary or something Staudey or did you just need it for reference?
Dec 7 2022
I know this is closed, but seeing as it's quite old, if sentiment has changed and this package can be approved, I'd be interested in packaging and maintaining it.
I have the package for this working now.
Nov 30 2022
I've submitted an update for this.
Nov 23 2022
Also, I am willing to maintain this, I'll probably start working on packaging it very soon.
Nov 21 2022
Nov 12 2022
Rebuilt package to update files
Nov 11 2022
I have applied all the suggested changes, so I believe™ this package should be good to go.
Nov 10 2022
Removed second component.
Removed redundant dependencies.
Added trailing newline.
Nov 9 2022
Nov 6 2022
Thanks! Yes I followed the steps in Building a Package, I'll take a look at the Submitting section and get to work on that. Thanks again!
I'm wiling to maintain this. With some help from the forum I just got a package build working, I've also got the MAINTAINER.md. What next steps do I need to take? Thanks!