From: Marius Bakke <mbakke@fastmail.com>
To: Jan <tona_kosmicznego_smiecia@interia.pl>, guix-devel@gnu.org
Subject: Re: Packaging Jami "progress"
Date: Mon, 06 Apr 2020 20:26:36 +0200 [thread overview]
Message-ID: <87o8s4o4gz.fsf@devup.no> (raw)
In-Reply-To: <20200406183556.560f8e62@kompiuter>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
Jan <tona_kosmicznego_smiecia@interia.pl> writes:
> Hello everybody,
>
> I recently tested Jami using the latest pjproject version - 2.10 which
> was supposed to fix some strange bugs that are present only on Guix,
> but it didn't.
> https://git.jami.net/savoirfairelinux/jami-packaging/issues/63
> Jami developer - Sébastien Blin told me: "Imho the probable issue
> is related to our codebase... and this would need some bisect to
> understand what's wrong... This can be long and painful" and I'm
> currently out of ideas what could cause this bug.
Do you have a patch we can use to reproduce this issue on Guix?
> My last chance is waiting for core-updates to be merged into master and
> maybe something will fix the problem magically. When is
> the 1.1.0 release planned?
You can easily test the patch on core-updates by simply checking out the
branch and apply your patches. Or 'guix pull --branch=core-updates' if
you are testing via a channel.
1.1.0 will be released before the core-updates merge.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-04-06 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 16:35 Packaging Jami "progress" Jan
2020-04-06 18:26 ` Marius Bakke [this message]
2020-04-06 18:51 ` Jan
2020-04-07 22:51 ` Jan
2020-04-07 23:06 ` Marius Bakke
2020-04-07 23:52 ` Jan
2020-04-08 0:34 ` Leo Famulari
2020-04-08 0:39 ` 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=87o8s4o4gz.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=tona_kosmicznego_smiecia@interia.pl \
/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).