From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
Cc: guix-devel@gnu.org
Subject: Re: Maintaining GNU Jami package for Guix
Date: Mon, 28 Oct 2019 08:53:43 +0100 [thread overview]
Message-ID: <871ruxgvaw.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20191027012445.636b1070@interia.pl>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
Got your 3 emails! :)
>> Have you tried using pjproject
>> 5dfa75be7d69047387f9b0436dd9492bbbf03fe4 ?
>> Does the patching still fail?
> I've tried this today and it still fails. Don't know if the fails with
> the exact commit are much different from 2.9 fetched from the tarball.
> If they're not different, then you can see what happens in one of my
> comments here
> https://git.ring.cx/savoirfairelinux/ring-project/issues/691
Then this is not related to the Guix packages or the inputs, it's
related to the source you are fetching.
What if you `diff -r` the offending package in the third party folder
with the aforementioned commit?
The Jami developer should know more about this. I'm starting to be a
little scared of how out of hands dep management goes :p
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-10-28 7:53 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 [this message]
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
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=871ruxgvaw.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--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).