From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6647481443636215808 X-Received: by 2002:a2e:165c:: with SMTP id 28-v6mr1028506ljw.25.1547738898460; Thu, 17 Jan 2019 07:28:18 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a19:4bca:: with SMTP id y193ls1033688lfa.3.gmail; Thu, 17 Jan 2019 07:28:17 -0800 (PST) X-Google-Smtp-Source: ALg8bN6XiI2UCBPLuvXHGUzhOMcbt4VBhv3sjgBpkjB+ejs0YQC49ESy5TeETg/mp0BwL9Is1YtX X-Received: by 2002:a19:740a:: with SMTP id v10mr1057788lfe.16.1547738897909; Thu, 17 Jan 2019 07:28:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547738897; cv=none; d=google.com; s=arc-20160816; b=zGy9hI/NbkZUDlCZEyjM2mijQ10F5aZzcTZAT7jmq6NiGZ73OgLrctgGRxaYCPnu/w wtMs29hu3HJ4fP7A/DIdOc6u6pJWLKJY7ek0C5Ej/Lx/iYRcU86Qn2yfAIbG0AcKY40M 7lToCn+jcqLtcYoyRml0+eJFu17ttR8fd27Ma6sNZFuzE2C4UcKvUcKu/tc44rXurVPt fhSVcTwQXo1xJbhiqF9FOO3TnMRqNBhc66YVBuqa/4VDL9U7gXTWCWRP97wYcAnjLa7T G25nwE23yhh2nkFzQFTzdMOhRXieTRJzbJViP8b6a3UyZP0RmglJRGn1NuKWXZRAPXMM i21g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date; bh=GLf1iY8QMZt0NM14zS+Uf7mfcG3j0WVGLp+vei4xAeE=; b=EXZtzV3F2CmSq16n9YoHIveSMPDkx19u7VpSovkR4O7r8eNdrURU6oVREM156wRj1b 97jAYaHukoDpARpwrr8lqyLdAmZsy+Autw5F2hShi2j/jMmf8YyDT6FBiRXeVhMU5gvl lDOBF9tTFi3uYd8Is7Sq2RpSJofQICyeKKCxe/SdCKn/d1b5iuXWKO13iFrD3847ZrUK PxwsJdR3HzD2zR9SPFkYENtAEfJT3/29hK8tRZ67szJXmuAO8tnefdi1mz6U2yw3KjKT 3UjddPjEp5Oco8Ofi6cjnNQZeK6TWsviUWFNcKUHSnTm1Tq9k2tUY/6mTPvZ6i0JwyqB n7lA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id 81-v6si71041ljc.2.2019.01.17.07.28.17 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Jan 2019 07:28:17 -0800 (PST) Received-SPF: neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.62.211; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.m.ilbers.de ([88.74.195.228]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id x0HFSEc2008394 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 17 Jan 2019 16:28:16 +0100 Received: from yssyq.m.ilbers.de (localhost [127.0.0.1]) by yssyq.m.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPS id x0HFS9mB009670 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 17 Jan 2019 16:28:09 +0100 Received: (from ibr@localhost) by yssyq.m.ilbers.de (8.15.2/8.15.2/Submit) id x0HFS9Ef009669 for isar-users@googlegroups.com; Thu, 17 Jan 2019 16:28:09 +0100 Date: Thu, 17 Jan 2019 16:28:09 +0100 From: Baurzhan Ismagulov To: isar-users Subject: Re: https://github.com/ilbers/hello conflicts with upstream hello Message-ID: <20190117152809.GK12226@yssyq.m.ilbers.de> Mail-Followup-To: isar-users References: <20190117160301.6928bd98@md1za8fc.ad001.siemens.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190117160301.6928bd98@md1za8fc.ad001.siemens.net> User-Agent: Mutt/1.10.1 (2018-07-13) X-TUID: gwPG4NApxvx+ On Thu, Jan 17, 2019 at 04:03:01PM +0100, Henning Schild wrote: > i am building apt-get source support for Isar and am using "hello" as > an example application. Turn out that the upstream hello package > places /usr/bin/hello and example-hello from isar is doing the same. > > I suggest to update example-hello to choose another binary name and > resolve the collision. Conflicting packages are explicitly allowed in Debian. How can we reproduce your problem with /usr/bin/hello? > My series to Isar will just remove example-hello for now, it should be > re-added once the issue is solved. I don't have anything against renaming the binary to e.g. hello-isar, but I think the suggested approach is an unnecessary overkill. With kind regards, Baurzhan.