all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jan <tona_kosmicznego_smiecia@interia.pl>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Maintaining Jami #3
Date: Thu, 6 Feb 2020 22:41:19 +0100	[thread overview]
Message-ID: <20200206224119.74803a5d@kompiuter> (raw)
In-Reply-To: <20200120155324.00935fdc@kompiuter>

Hello,
I think I found the source of the problems - there's a bug in pjproject
2.9
https://trac.pjsip.org/repos/ticket/2240
and 2.10 wasn't yet released, so I can't package it.
The error message is the same as I got during testing calls.
I guess the bug have been unnoticed by Jami developers, because:
1. their builds are not reproducible
2. software is tested and used in different network environments -
there's a chance specific settings trigger the bug

Until the release of pjproject 2.10 I can do nothing, but I actually
cleaned up my private guix repository, so DO NOT pull my changes,
because they're a total mess. I guess I'll close the current issue and
open a new one once I finish cleaning my code. I'll also finish
learning git, as I have some free time now.



Jan Wielkiewicz

  parent reply	other threads:[~2020-02-06 21:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 12:05 Maintaining Jami #3 Jan
2020-01-07 18:13 ` Jan
2020-01-18 23:47 ` Jan
2020-01-18 23:51 ` Jan
2020-01-18 23:55 ` Jan
2020-01-19  9:20   ` Pierre Neidhardt
2020-01-19 15:55     ` Jan
2020-01-20 14:53     ` Jan
2020-01-21 10:12       ` Pierre Neidhardt
2020-01-27 23:12         ` Jan
2020-02-06 21:41       ` Jan [this message]
2020-02-07 13:53         ` Pierre Neidhardt
2020-02-07 15:12           ` Jan
2020-02-07 17:17             ` Pierre Neidhardt
2020-02-07 22:34         ` Marius Bakke
2020-02-07 23:28           ` Jan
2020-02-08  1:39           ` Jan
  -- strict thread matches above, loose matches on Subject: below --
2020-01-10 20:17 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200206224119.74803a5d@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.