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: Jami bug investigation #2
Date: Thu, 21 May 2020 01:11:57 +0200	[thread overview]
Message-ID: <20200521011157.78cae455@kompiuter> (raw)

Hello,

I'm still trying to fix the bug, Jami devs are still busy doing other
things, so I decided to do an experiment.
I discovered tarballs published at
https://dl.jami.net/release/tarballs/ often have some faults - one time
it didn't contain client-gnome and lrc folders, and the most recent one
doesn't contain daemon/contrib folder. My idea is the automatically
generated tarballs contain some undiscovered yet faults that make our
package behave differently.

To check if it's true, I decided not to use these tarballs and use
git-fetch instead - I did it with Jami daemon and daemon client lib,
but I can't apply patches for pjproject - the patch command tells me
files are read-only. This is really strange, because I make the files
writable using "make-file-writable", which works on the current
Jami package and works for ffmpeg-jami (even after modifying jami
daemon and the procedures applying patches).

Is it possible that there's something wrong with permissions in the
pjproject repository, which makes it impossible to apply the patches?
I'm using the exact same pjproject version as Jami developers, yet
patching fails.

Any ideas?


Jan Wielkiewicz


             reply	other threads:[~2020-05-20 23:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 23:11 Jan [this message]
2020-05-22  9:07 ` Jami bug investigation #2 Pierre Neidhardt
2020-05-22 13:35   ` Jan
2020-05-22 14:15   ` Jan
2020-05-25 22:36   ` 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=20200521011157.78cae455@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.