From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id OQ+jMWO5xV5eUwAA0tVLHw (envelope-from ) for ; Wed, 20 May 2020 23:12:35 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id gCDxLGO5xV6/JgAA1q6Kng (envelope-from ) for ; Wed, 20 May 2020 23:12:35 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 5DDD0940428 for ; Wed, 20 May 2020 23:12:35 +0000 (UTC) Received: from localhost ([::1]:45506 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jbXt4-0002mc-7r for larch@yhetil.org; Wed, 20 May 2020 19:12:34 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:60076) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jbXsu-0002m8-FF for guix-devel@gnu.org; Wed, 20 May 2020 19:12:24 -0400 Received: from smtpo.poczta.interia.pl ([217.74.65.233]:37753) by eggs.gnu.org with esmtps (TLS1.2:RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jbXss-0001le-UB for guix-devel@gnu.org; Wed, 20 May 2020 19:12:24 -0400 X-Interia-R: Interia X-Interia-R-IP: 89.64.42.134 X-Interia-R-Helo: Received: from kompiuter (89-64-42-134.dynamic.chello.pl [89.64.42.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by poczta.interia.pl (INTERIA.PL) with ESMTPSA for ; Thu, 21 May 2020 01:12:17 +0200 (CEST) Date: Thu, 21 May 2020 01:11:57 +0200 From: Jan To: guix-devel@gnu.org Subject: Jami bug investigation #2 Message-ID: <20200521011157.78cae455@kompiuter> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Interia-Antivirus: OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interia.pl; s=biztos; t=1590016338; bh=zk0txpi7X81J6D2gpR3ucbLoHpRoJlLYqSEzmBi3yqA=; h=X-Interia-R:X-Interia-R-IP:X-Interia-R-Helo:Date:From:To:Subject: Message-ID:X-Mailer:MIME-Version:Content-Type: Content-Transfer-Encoding:X-Interia-Antivirus; b=Gk4T/JfJMO1pDOpPjNvrPjiEoy8DaBbSXglQXIYForBPhbgCFzRAUvzSqzvQUFusm lwm8rFhzzgbX7Dge2BLv2oSSqmjIUwv8jI7Qy+1KPoPoOwm+Wwg7g1RgbyPkdnOUtY ngRntEuE50iYlYTCAo6SVntmWGr3N88o+Qk75CDk= Received-SPF: pass client-ip=217.74.65.233; envelope-from=tona_kosmicznego_smiecia@interia.pl; helo=smtpo.poczta.interia.pl X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/20 19:12:18 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x (no timestamps) [generic] X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=interia.pl header.s=biztos header.b=Gk4T/JfJ; dmarc=none; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Spam-Score: -0.71 X-TUID: C3Nku432XuOM 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