From: Jan <tona_kosmicznego_smiecia@interia.pl>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Maintaining Jami #3
Date: Tue, 28 Jan 2020 00:12:10 +0100 [thread overview]
Message-ID: <20200128001210.654960d0@kompiuter> (raw)
In-Reply-To: <87a76hjeyt.fsf@ambrevar.xyz>
Hi Pierre,
I made some tests Guix System <-> Devuan on my current Jami package
20200124 version or something similar to this and I managed to
reproduce bugs you pointed out.
Didn't get answer from Jami developers yet, but it seems something is
wrong with our pjproject package:
That's what the daemon prints while crashing:
dring: ../src/pjsip-ua/sip_inv.c:246: pjsip_inv_dec_ref: Assertion `inv
&& inv->ref_cnt' failed.
Now I am going to investigate what's wrong with pjproject, mostly
finish our currently not working pjproject package (it won't compile,
only pjproject-jami works) and then I'll update it to the latest
version, if it got outdated much since the last time I checked.
I also wait for merging core-updates, because another bug - the
screen sharing one may be caused by something related to glibc, which
got updated on core-updates. Or webkit-gtk or Qt or whatever - anything
can be a problem, if the package has about 1GB of dependencies...
Jan Wielkiewicz
next prev parent reply other threads:[~2020-01-27 23:12 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 [this message]
2020-02-06 21:41 ` Jan
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=20200128001210.654960d0@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.