all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jan <tona_kosmicznego_smiecia@interia.pl>
To: guix-devel@gnu.org
Subject: Packaging Jami "progress"
Date: Mon, 6 Apr 2020 18:35:56 +0200	[thread overview]
Message-ID: <20200406183556.560f8e62@kompiuter> (raw)

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.

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?

If not this, I will have to wait for Jami developers to investigate the
problem for me which can be difficult, since they're busy working and
they're probably not familiar enough with Guix to help.

I still wonder what could be the source of the problem. Would be cool
if someone could help me check whether it's reproducibility or
packaging problem.

I know they use gcc on debian 10, fedora 31 and ubuntu 19.10 to build
Jami and the bug isn't present there - it's Guix-only problem (packages
build using Guix don't work properly on foreign distributions either).



Jan Wielkiewicz

             reply	other threads:[~2020-04-06 16:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 16:35 Jan [this message]
2020-04-06 18:26 ` Packaging Jami "progress" Marius Bakke
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

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

  git send-email \
    --in-reply-to=20200406183556.560f8e62@kompiuter \
    --to=tona_kosmicznego_smiecia@interia.pl \
    --cc=guix-devel@gnu.org \
    /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.