From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#22458: Collision between khal and vdirsyncer "bin/vdirsyncer" Date: Wed, 03 Feb 2016 22:56:21 +0100 Message-ID: <871t8t5ugq.fsf@gnu.org> References: <20160124232439.GA8199@jasmine> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57273) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aR5QB-0007NN-BR for bug-guix@gnu.org; Wed, 03 Feb 2016 16:57:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aR5Q6-0008VL-Bh for bug-guix@gnu.org; Wed, 03 Feb 2016 16:57:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:49887) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aR5Q6-0008VG-97 for bug-guix@gnu.org; Wed, 03 Feb 2016 16:57:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aR5Q6-0001Or-4g for bug-guix@gnu.org; Wed, 03 Feb 2016 16:57:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20160124232439.GA8199@jasmine> (Leo Famulari's message of "Sun, 24 Jan 2016 18:24:39 -0500") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Leo Famulari Cc: 22458@debbugs.gnu.org Leo Famulari skribis: > The packages khal and vdirsyncer are meant to be used together. Khal is > a console calendar program and vdirsyncer synchronizes CalDAV data from > a remote server to the local filesystem so that khal can use it. Then why do they both provide the same file? :-) > For some reason, the khal package is creating an > "EASY-INSTALL-ENTRY-SCRIPT" (as "bin/.vdirsyncer-real") that wraps the > propagated vdirsyncer executable. This means that both the khal and > vdirsyncer packages contain the path "bin/vdirsyncer", which is > annoying. Thankfully, they both end up executing the real vdirsyncer. I=E2=80=99m not sure I follow. Does upstream khal explicitly intend to ins= tall its own bin/vdirsyncer? Ludo=E2=80=99.