add jami repo

[13werwolf13]

today I saw the news about the new release of jami. decided to add it. the only thing I don't understand is how to make a repository for leap. they have it like https://dl.jami.net/nightly/opensuse-leap_15.4/jami-nightly.repo

[13werwolf13]

also found out one problem with jami official repositories. it does not affect the changes in this PR in any way, but without fixing it, it is impossible to check the work on tumbleweed.
https://forum.jami.net/t/tumbleweed-jami-repo-artifact-build-fail/1793
https://git.jami.net/savoirfairelinux/jami-project/-/issues/1546

[13werwolf13]

@asdil12 I'm not sure if this PR should be completed before the above problem is fixed, but I'm leaning towards it. in any case, it's up to you.

[asdil12]

According to https://en.wikipedia.org/wiki/Jami_(software) Jami seems to be licensed under GPLv3.
So is there a specific reason why this is not packaged via https://build.opensuse.org?

[13werwolf13]

According to https://en.wikipedia.org/wiki/Jami_(software) Jami seems to be licensed under GPLv3. So is there a specific reason why this is not packaged via https://build.opensuse.org?

I do not know this. but I think that if there are official repositories from the developer, then it is necessary to give them the opportunity to use them conveniently.

[13werwolf13]

checked in container 15.4
everything works as it should

[13werwolf13]

it seems that I rushed with these repositories. Based on this thread, they don't have the resources to further maintain rpm repositories for opensuse. if we don't find a solution then the package will move to OBS and I will make a PR to remove this plugin.

[asdil12]

Moving to obs would be the best solution as the packages are then built within a trusted environment and anyone can see the source code that is actually used to build the packages.

If they already built RPM packages in the past, maybe they can provide a spec file that we can reuse.

[13werwolf13]

Moving to obs would be the best solution as the packages are then built within a trusted environment and anyone can see the source code that is actually used to build the packages.

If they already built RPM packages in the past, maybe they can provide a spec file that we can reuse.

I have already started to do this, if with their spec I can assemble packages without problems then wait for PR.