unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jan <tona_kosmicznego_smiecia@interia.pl>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Maintaining GNU Jami package for Guix
Date: Sun, 3 Nov 2019 18:43:29 +0100	[thread overview]
Message-ID: <20191103184329.47f70c05@kompiuter> (raw)
In-Reply-To: <878sowq5l5.fsf@devup.no>

On Sun, 03 Nov 2019 17:37:10 +0100
Marius Bakke <mbakke@fastmail.com> wrote:

> I did not find any cURL or GnuTLS patches there.  Maybe I
> misunderstood something?

Gnutls is a dependency of Jami, curl is probably a dependency of a
dependency of Jami, but that's all - what is important here is that
Jami uses a modified version of pjproject, which adds support for
gnutls - that's why patching fails. What happened with curl is a
mystery for me, the only thing I know is that building curl had failed
before building pjproject-jami, so I thought the patching process
succeeded. But since it works now, it doesn't matter (at least for me).

> Both GnuTLS and cURL have stable ABIs.  That means, a package linked
> against cURL 7.63 will almost certainly work with cURL 7.66 without
> changes (even without recompilation).

Don't know why, but Jami seems to use a specific version of gnutls, but
if what you say is true, then it doesn't matter. I started looking for
outdated dependencies, because I thought they could be the source of
the problem.

> There are many reasons not to include multiple versions of a package,
> but for cURL and GnuTLS in particular, the main reason is that there
> are security fixes in nearly every new version.  Thus, we can only
> support the latest one.

Okay, I'll try using the latest packages for Jami then.


Jan Wielkiewicz

  reply	other threads:[~2019-11-03 17:43 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 18:56 Maintaining GNU Jami package for Guix Jan
2019-10-18 19:28 ` Marius Bakke
2019-10-19  9:02   ` Pierre Neidhardt
2019-10-19 20:38     ` Jan Wielkiewicz
2019-10-19 20:52       ` Ricardo Wurmus
2019-10-19 22:37         ` Jan
2019-10-20 11:14           ` Ricardo Wurmus
2019-10-20 11:51           ` Pierre Neidhardt
2019-10-20 11:48       ` Pierre Neidhardt
2019-10-25 15:03         ` Pierre Neidhardt
2019-10-25 19:44           ` Jan Wielkiewicz
2019-10-26 10:12             ` Pierre Neidhardt
2019-10-26 23:24               ` Jan Wielkiewicz
2019-10-28  7:53                 ` Pierre Neidhardt
2019-10-27 18:13 ` Jan Wielkiewicz
2019-10-27 18:18   ` Pierre Neidhardt
2019-10-27 19:23     ` Jan Wielkiewicz
2019-10-27 21:52 ` Jan Wielkiewicz
2019-10-31 20:19 ` Jan Wielkiewicz
2019-10-31 21:37   ` Pierre Neidhardt
2019-10-31 22:26   ` Marius Bakke
2019-11-01 12:01     ` Jan Wielkiewicz
2019-11-01 19:02       ` Pierre Neidhardt
2019-11-01 20:42         ` Jan Wielkiewicz
2019-11-02  9:38           ` Pierre Neidhardt
2019-11-03 16:37       ` Marius Bakke
2019-11-03 17:43         ` Jan [this message]
2019-11-03 18:06           ` Marius Bakke
2019-11-01 12:29 ` Jan Wielkiewicz
2019-11-01 19:01   ` Pierre Neidhardt
2019-11-01 23:16     ` Jan Wielkiewicz
2019-11-03 10:15       ` Pierre Neidhardt
2019-11-03 10:54         ` Jan Wielkiewicz
2019-11-04 10:02           ` Gábor Boskovits
2019-11-03 10:59         ` Jan Wielkiewicz
2019-11-03 17:07   ` Marius Bakke
2019-11-03 17:47     ` Jan
2019-11-03 18:12   ` Marius Bakke
2019-11-03 18:27     ` Jan
2019-11-03 18:52       ` Marius Bakke

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=20191103184329.47f70c05@kompiuter \
    --to=tona_kosmicznego_smiecia@interia.pl \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.com \
    /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).