From: Jan <tona_kosmicznego_smiecia@interia.pl>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Jami: Bug source investigation
Date: Thu, 16 Apr 2020 13:57:02 +0200 [thread overview]
Message-ID: <20200416135702.44c2a080@kompiuter> (raw)
In-Reply-To: <87lfmv4zhg.fsf@ambrevar.xyz>
On Thu, 16 Apr 2020 10:16:27 +0200
Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> Hi Jan,
>
> If I understand correctly, your updated package works better than the
> one we've current got in Guix.
Chat seems to work, sending recorded audio/video messages works,
sending files works, audio/video calls work (ignoring the crash when
disconnecting). Works better I guess, last time nothing was working.
> What I suggest is that you send the patch set, we review and merge it,
> then the Jami developers will be able to reproduce the bug easily by
> simply installing Guix on their system.
> What do you think?
>
Seems to be a good idea. The question is if Jami developers
will have time to help us, they're not volunteers, but are employed by
Savoir-Faire Linux after all.
I'll prepare the patches later today, or you can just clone it from
here:
https://gitlab.com/kromka_chleba/jami-package-and-other-things-for-guix.git
My work is on the wip-jami branch.
Jan Wielkiewicz
next prev parent reply other threads:[~2020-04-16 11:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 23:20 Jami: Bug source investigation Jan
2020-04-13 21:21 ` Jami: Bug source investigation (help needed) Jan
2020-04-15 18:31 ` Jami: Bug source investigation Marius Bakke
2020-04-15 18:54 ` Jan
2020-04-16 8:16 ` Pierre Neidhardt
2020-04-16 11:57 ` Jan [this message]
2020-04-17 0:53 ` Jan
2020-05-03 7:54 ` Pierre Neidhardt
2020-05-03 14:05 ` Jan
2020-05-03 14:17 ` Pierre Neidhardt
2020-05-03 14:50 ` Jan
2020-05-03 15:26 ` Pierre Neidhardt
2020-05-03 15:28 ` sirgazil
2020-05-03 16:11 ` Jan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200416135702.44c2a080@kompiuter \
--to=tona_kosmicznego_smiecia@interia.pl \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).