Hello Jan,
Jan Wielkiewicz ezt írta (időpont:
2019. nov. 3., V, 22:20):
> Dnia 2019-11-03, o godz. 11:15:56
> Pierre Neidhardt napisał(a):
>
> > Can you share the complete recipe?
> >
>
> Yes. I guess you want a patch of my entire work so far, because
> pjproject-jami is meaningless without
Dnia 2019-11-03, o godz. 11:15:56
Pierre Neidhardt napisał(a):
> Can you share the complete recipe?
>
Yes. I guess you want a patch of my entire work so far, because
pjproject-jami is meaningless without changes in jami, so I'm attaching
the whole patch. Also the commit messages are messy, any
Jan writes:
> On Sun, 03 Nov 2019 19:12:03 +0100
> Marius Bakke wrote:
>
>> You can safely ignore the 'read only' messages, they are actually just
>> warnings.
>
> Good to know, so they get applied anyway, no matter if read-only?
Correct, at least as long as you use the '--force' flag to the
On Sun, 03 Nov 2019 19:12:03 +0100
Marius Bakke wrote:
> You can safely ignore the 'read only' messages, they are actually just
> warnings.
Good to know, so they get applied anyway, no matter if read-only?
> The problem is that 2/3 hunks in the patch for
> pjnath/src/pjnath/ice_strans.c failed
Jan Wielkiewicz writes:
> I have good and bad news.
> The good news is I fixed curl by using the most recent Jami source
> tarball - 20191031.3.40360d8.
> The bad news is that pjproject-jami didn't really build, because the
> patches failed to get applied again - the curl problem had occured
>
Jan writes:
> On Sun, 03 Nov 2019 17:37:10 +0100
> Marius Bakke 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
On Sun, 03 Nov 2019 18:07:24 +0100
Marius Bakke wrote:
> Git checkouts are read-only because they are copied to the store,
> which strips write permissions. It could be mitigated by having
> 'git-fetch' return a tarball instead of a directory, but in practice
> read-only checkouts rarely causes
On Sun, 03 Nov 2019 17:37:10 +0100
Marius Bakke 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
Jan Wielkiewicz writes:
> Why "pjnath/src/pjnath/turn_session.c is read-only; trying to patch
> anyway"? Why is it read-only. I don't get it, are we missing some
> permissions? Somehow this wasn't a problem before - the previous
> version of pjproject-jami didn't have this problem. Is it a bug
Jan Wielkiewicz writes:
> Dnia 2019-10-31, o godz. 23:26:39
> Marius Bakke napisał(a):
>
>> Do you have a link to the patches that Jami/pjproject needs?
> You can find patches in the ring-project/daemon/contrib/src/pjproject
> directory from the latest source tarball here:
>
Sorry, wrong command, sending the patch again...
Jan
>From 2f67e4c77ffb675bed3019b4289b3135db140015 Mon Sep 17 00:00:00 2001
From: Jan Wielkiewicz
Date: Sun, 27 Oct 2019 01:16:52 +0200
Subject: [PATCH 1/9] change the fetch method of pjproject to git; fetch the
exact commit needed for Jami; do
Dnia 2019-11-01, o godz. 20:01:26
Pierre Neidhardt napisał(a):
> Git preserves permissions, so if upstream made it read-only (probably
> a mistake), then it will be read-only in the checkout. No problem,
> you can make it writable with
> `make-file-writable'.
>
Don't know why, but it doesn't
Dnia 2019-11-01, o godz. 20:02:22
Pierre Neidhardt napisał(a):
> Because gnutls with Jami patches should not be called gnutls: it's a
> non-vanilla version of GnuTLS. And I doubt it would be useful to
> anyone but Jami.
Actually gnutls is without patches, just an older version. What has
Jan Wielkiewicz writes:
> Why "pjnath/src/pjnath/turn_session.c is read-only; trying to patch
> anyway"? Why is it read-only. I don't get it, are we missing some
> permissions? Somehow this wasn't a problem before - the previous
> version of pjproject-jami didn't have this problem. Is it a bug
Jan Wielkiewicz writes:
> Why can't we just keep paralell version for a package? Like
> gnutls @ 3.6.7, gnutls @ 3.6.9 etc?
Because gnutls with Jami patches should not be called gnutls: it's a
non-vanilla version of GnuTLS. And I doubt it would be useful to anyone
but Jami.
--
Pierre
Dnia 2019-10-31, o godz. 23:26:39
Marius Bakke napisał(a):
> Do you have a link to the patches that Jami/pjproject needs?
You can find patches in the ring-project/daemon/contrib/src/pjproject
directory from the latest source tarball here:
https://dl.jami.net/ring-release/tarballs/
> It would be
Jan Wielkiewicz writes:
> Also as for packaging Jami generally, I think we should keep a separate
> versions of things like gnutls and pjproject (basically all
> dependencies of pjproject), because version used by Jami are often not
> up to date and considering patches getting applied, using an
Fantastic!
I suggest you ask upstream which precise version of Curl they use.
You can still try to skip the tests in the meantime, but the messages
are not very reassuring... :p
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
Dnia 2019-10-27, o godz. 19:18:19
Pierre Neidhardt napisał(a):
> Thanks for the update! :)
> Which failing patch and what fails? Output?
Sorry, I sent a mail explaining everything yesterday, but it seems it
got lost somewhere - your or mine mail provider does something
(blocks?) or the ML has
Dnia 2019-10-26, o godz. 12:12:44
Pierre Neidhardt napisał(a):
> Nice, thank you for getting in touch with the developers, this is
> very informative.
>
> Have you tried using pjproject
> 5dfa75be7d69047387f9b0436dd9492bbbf03fe4 ?
> Does the patching still fail?
I've tried this today and it
Dnia 2019-10-27, o godz. 19:18:19
Pierre Neidhardt napisał(a):
> Thanks for the update! :)
> Which failing patch and what fails? Output?
Sorry, I sent a mail explaining everything yesterday, but it seems it
got lost somewhere - your or mine mail provider does something
(blocks?) or the ML has
Thanks for the update! :)
Jan Wielkiewicz writes:
> also gnutls needed for pjproject-jami has
> the wrong version - 3.6.9, whereas the current version used by Jami is
> 3.6.7 according to this commit
> https://review.jami.net/c/ring-daemon/+/12108/1/contrib/src/gnutls/rules.mak
> (but I'll ask
Dnia 2019-10-25, o godz. 17:03:01
Pierre Neidhardt napisał(a):
> Hi Jan,
>
> any luck with Jami? Let me know if you need more specific help (my
> previous message was maybe not too clear :p), I can dig into this
> deeper in the coming days.
>
I had little time recently, but I've been trying
Hi Jan,
any luck with Jami? Let me know if you need more specific help (my
previous message was maybe not too clear :p), I can dig into this deeper
in the coming days.
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
Hi Jan,
> On Sat, 19 Oct 2019 22:52:58 +0200
> Ricardo Wurmus wrote:
>
>> We always try to unbundle libraries, because that ensures that all
>> packages benefit from security fixes.
>>
>
> Great, so I have to package everything recursively :)
> Just to make it clear, because I'm a bit
On Sat, 19 Oct 2019 22:52:58 +0200
Ricardo Wurmus wrote:
> We always try to unbundle libraries, because that ensures that all
> packages benefit from security fixes.
>
Great, so I have to package everything recursively :)
Just to make it clear, because I'm a bit unfamiliar with build systems
Jan Wielkiewicz writes:
> Why are third party directories removed if they're necessary to build
> pjproject? Should I package contents of these folders as separate
> package?
We always try to unbundle libraries, because that ensures that all
packages benefit from security fixes.
--
Ricardo
Hello,
Dnia 2019-10-19, o godz. 11:02:35
Pierre Neidhardt napisał(a):
> Hi Jan,
>
> glad you are interested in picking this one up! :)
> I'm the last packager of Jami, so I might be able to help.
Yes, thank you, I definitely will need help.
> After a quick glance, here is the situation it
Hello Jan,
Jan writes:
> Hi all,
> It seems Jami package is outdated and unmaintained, so I would like to
> become a maintainer of the package.
> I know the basics of Guile Scheme and Guix System, I'm more or
> less familiar with how Jami works and what are its dependencies, but I
> don't know
Hi all,
It seems Jami package is outdated and unmaintained, so I would like to
become a maintainer of the package.
I know the basics of Guile Scheme and Guix System, I'm more or
less familiar with how Jami works and what are its dependencies, but I
don't know much about development, git or build
30 matches
Mail list logo
