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: Tue, 03 May 2016 22:24:37 +0200 Message-ID: <8737pykhyy.fsf@gnu.org> References: <20160124232439.GA8199@jasmine> <871t8t5ugq.fsf@gnu.org> 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]:43129) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1axgsg-00025u-9q for bug-guix@gnu.org; Tue, 03 May 2016 16:25:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1axgsU-0006KA-NX for bug-guix@gnu.org; Tue, 03 May 2016 16:25:12 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:51691) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1axgsU-0006F5-Kb for bug-guix@gnu.org; Tue, 03 May 2016 16:25:06 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1axgsR-0000y4-8z for bug-guix@gnu.org; Tue, 03 May 2016 16:25:03 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <871t8t5ugq.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 03 Feb 2016 22:56:21 +0100") 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" To: Leo Famulari Cc: 22458@debbugs.gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) skribis: > 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 i= nstall > its own bin/vdirsyncer? Ping? :-) Ludo=E2=80=99.