From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jan <tona_kosmicznego_smiecia@interia.pl>
Subject: Re: Maintaining Jami #3
Date: Sun, 19 Jan 2020 16:55:35 +0100
Message-ID: <20200119165535.0cd52bc0@kompiuter>
References: <20200107130521.5a781f53@kompiuter>
 <20200119005543.0f86942a@interia.pl> <87ftgbu7ik.fsf@ambrevar.xyz>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:46814)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <tona_kosmicznego_smiecia@interia.pl>)
 id 1itCvU-0005cm-Uu
 for guix-devel@gnu.org; Sun, 19 Jan 2020 10:55:50 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <tona_kosmicznego_smiecia@interia.pl>)
 id 1itCvT-0004Ms-GJ
 for guix-devel@gnu.org; Sun, 19 Jan 2020 10:55:48 -0500
Received: from smtpo.poczta.interia.pl ([217.74.65.156]:46743)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
 (Exim 4.71) (envelope-from <tona_kosmicznego_smiecia@interia.pl>)
 id 1itCvS-0004Ll-Tz
 for guix-devel@gnu.org; Sun, 19 Jan 2020 10:55:47 -0500
In-Reply-To: <87ftgbu7ik.fsf@ambrevar.xyz>
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org
Sender: "Guix-devel"
 <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org

On Sun, 19 Jan 2020 10:20:51 +0100
Pierre Neidhardt <mail@ambrevar.xyz> wrote:

> Hi Jan,
> 
> I tested the Jami package we have in upstream Guix:
> 
> - It fails to start on my desktop, it only works on my laptop.
> 
> - The client kept disconnecting.  I could send a few text messages
> here and there, but most of them didn't go through.
> 
> - I could not give an audio or video call.
> 
> - I can receive text messages perfectly.
> 
> - I can receive calls, but when I click on the "pick up" button, Jami
>   crashes.
> 
> In general, Jami crashed _a lot_.  I wonder if it's upstream or if we
> have something wrong with our package.
> 
> Did you have a similar experience?
> Does your work fix any of those issues?
> 

Well, generally I started working on Jami, because it never worked for
me well - crashes, bugs, issues with UPnP and NAT. That was on Devuan,
but on Guix it is like this also. I think bugs are present upstream,
but Guix only makes them reproducible :)
I also don't know which releases are beta and which are not, I once
tried asking, but did not get real answer.
Their release naming system is YYYYMMDD and it tells you nothing, I
asked them to change it, but they didn't. 
I just package the latest version available at
https://dl.jami.net/ring-release/tarballs/?C=M;O=D
and sometimes its okay, but once I couldn't build gnome client on
Devuan at all.

Jami should not be considered stable for now, at least my package - they
make too many changes for it to be stable, without any code freeze.
The software was started in 2016 and two years ago it was a deep beta,
they need some time to clean this up.

Current versions also use beta software - OpenDHT 2.0 is currently at
beta stage.

Once my changes are merged, I can try updating everything to the latest
versions and maybe it'll work, if not we can rename jami to jami-beta
and rename it back when it's ready.



Jan Wielkiewicz