Package Details: jitsi 2.11.5633-1

Git Clone URL: https://aur.archlinux.org/jitsi.git (read-only, click to copy)
Package Base: jitsi
Description: An audio/video SIP VoIP phone and instant messenger written in Java (formerly SIP-Communicator)
Upstream URL: https://desktop.jitsi.org/Main/HomePage
Licenses: Apache
Submitter: psychedelicious
Maintainer: figue (figuepluto, jfigueras)
Last Packager: figue
Votes: 365
Popularity: 1.02
First Submitted: 2011-05-11 11:22
Last Updated: 2020-12-12 16:22

Dependencies (3)

Required by (0)

Sources (3)

Pinned Comments

figue commented on 2020-12-12 17:04

I've built with jdk8... Like this:

env JAVA_HOME=/usr/lib/jvm/java-8-openjdk PATH=/usr/lib/jvm/java-8-openjdk/jre/bin:$PATH makepkg -sic

But if you want to execute jitsi, it's better to set it globally:

archlinux-java set java-8-openjdk

See pinned comment.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

jotoho commented on 2021-03-20 15:59

@figue Thanks for the advice! I'll change my $PATH to use $HOME then.

figue commented on 2021-03-20 15:34

@jotoho when I include something in my home, I usually use $HOME variable, so you can do: export PATH="$PATH:$HOME/scripts"

jotoho commented on 2021-03-20 09:41

@figue Sorry for the late response. My path does not contain . but simply a subfolder of the home directory, which contains frequently used scripts.

I do not know why find claimed that using it with the -execdir is insecure but when reading through the error message again, it seems that the problem is that it sees ~/scripts as a relative path and not that is in the home directory of the current user. Changing the entry in $PATH from ~/scripts to /home/<my username>/scripts fixed it.

Maybe find incorrectly assumes that ~ makes paths relative and that all relative paths are inside the current working directory? If so, that seems like shoddy work on their part. Then again, I don't know what potential vulnerability they are talking about, so I'm not qualified to judge that.

Since I don't know enough about the situation and have never made a PKGBUILD before, I am sadly unable to provide a fix for this. Hopefully making you aware of my testing results will help you if someone else comes along with this problem in the future.

figue commented on 2021-03-14 14:43

@jotoho Never heard about this security concern... I've never added "." in my $PATH so user that does this has to know the possible consequenses. To have ~/scripts in PATH should not be a problem. Can you provide an example so I can reproduce or can you provide a patch to avoid it?

Thank you

jotoho commented on 2021-03-14 10:30

Even after temporarily changing environment variables to point to OpenJDK8 instead of the newest version, the installation failed when running find.

It complained that one of the folders in my home directory ~/scripts has been added to the $PATH because thats a security risk when using find with the flag -execdir. This script seems very unstable to me, if it fails just for having a slightly different system configuration than the maintainer.

figue commented on 2021-01-03 19:12

@MichaelARCH in a pinned comment you have a makepkg temporary command to build jitsi with JDK8.

MichaelARCH commented on 2021-01-03 18:38

On my system OpenJDK14 (default) and OpenJDK8 are installed. And I want to keep openJDK14 as standard for other purposes. During Build, got the error:
/jitsi/src/jitsi-5633/build.xml:269: Compile failed; see the compiler error output for details.

Do you recommend that I change it temporarily for the build to Version 8, like described here? Or to prefer another procedure?

Thanks, Michael

ArthurBorsboom commented on 2020-12-15 20:51

Hi Figue,

Do you think you can adapt the PKGBUILD in a way that the java compiler is forced to OpenJDK8 before compiling? For example, in pseudo:

JavaSettings originalJavaSetting = RequestCurrentJava();
boolean changeJavaVersion = originalJavaSetting != openjdk-8;

if (changeJavaVersion) {
  force openjdk-8
}

compile and package jitsi

if (changeJavaVersion) {
  restore originalJavaSetting;
}

figue commented on 2020-12-12 18:45

Ok... If the version is not stable enough I will revert the last commit. I don't use anymore Jisti, so I'm maintaining just for you guys. If anyone is interested in maintaining this package, please comment and I'll orphan.

Zappo-II commented on 2020-12-12 17:44

Ok, after the update and having it running in java-8-openjdk again, my installation kept SegFaulting and CoreDumping when I was some seconds into the application, no matter what I did or did not do...

Before the update it was just working fine and everything I changed was just to newly build jitsi...

To have it running stable again I had to delete all my jitsi settings in ~/.jitsi and had to rebuild them using the jitsi settings dialogs...

ThankYou @figue for packaging jitsi, it's my daily sip-phone app and I really appreciate having it at hand...