From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6647481443636215808 X-Received: by 2002:a17:906:2352:: with SMTP id m18-v6mr1887532eja.9.1547741403666; Thu, 17 Jan 2019 08:10:03 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a50:b1e2:: with SMTP id n31ls2424729edd.3.gmail; Thu, 17 Jan 2019 08:10:03 -0800 (PST) X-Google-Smtp-Source: ALg8bN7R1d+ewtNyHrA2wsbrYdrAyWlTKenzMkhJ0GatvtE/mMV7X5TzD/CSPqaVW7FxcezevBFb X-Received: by 2002:a50:aeaf:: with SMTP id e44mr2107130edd.4.1547741403279; Thu, 17 Jan 2019 08:10:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547741403; cv=none; d=google.com; s=arc-20160816; b=gWNy5CHFnt6x5b1CuY9NtH3Q2uUG0Bn2EixvwvCd+Dncvr6p9HzUzCuBk2NLZwjEHA aDQGmLDhRtVgcWKE775pmd3K/0CHZeZQkZV7dAJ14JHPGdEM3GcZtjEBkDarrPGiADDM UuYa865nSn4gtlQ8kSLAOUcWY38KHMddYXNMt2UaFYFIhdw/iPIihGaXB7jOp7UkJ2ZM j7RtYetxOdopgyCvFfvP1OTKiBsUxSTBtHqUCUZN2+AhnWwYnZdswW4t4UkPQvpbAelX 26g4IZBnkx170asvra7ZCPoPrNJgkz9QiOFsV6Jmf2zPlqbMm7HL+Z3tmSQg57M6yqBv eM2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=eWIyFBfRlwwh7K7fvZMBjV4xHp9WHRxTmgPAjHE7KE4=; b=GWGKq4eiatXk35Nb1CELdUaWEV6bPwehQPdhhYAYFpmnGtrks8UtMrvE0Vq71XhWeB 9dKE7kTG2/tTx2lpN/l9Xjy4Evyg2JOFfseAUPUhVXeMKbdEyIbM1NlMNQzFu5Z5D7o8 JwSYZkLMM3TmHE4WuM6wXxHMkPwq/v4XoTAVDiD38Z91GUTL4KZVpheZCeamEBNN6fPt kGWNosIDyMARnqd7xXJamGwTaHJ/lI6r7zFf8bIdzGrBJiPMC3iBoy2vOKmw76OtXyup mjZOBp8LJlfrA6gbiCszY7oWa5L4MnbTxYHmsxzdQXCGY1MyU+vIzxkvt0KnGnm7c2p6 zo+Q== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from gecko.sbs.de (gecko.sbs.de. [194.138.37.40]) by gmr-mx.google.com with ESMTPS id i2-v6si1278872ejj.1.2019.01.17.08.10.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Jan 2019 08:10:03 -0800 (PST) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.40 as permitted sender) client-ip=194.138.37.40; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by gecko.sbs.de (8.15.2/8.15.2) with ESMTPS id x0HGA2XU009882 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 17 Jan 2019 17:10:02 +0100 Received: from md1za8fc.ad001.siemens.net ([139.25.69.119]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x0HGA2OZ031136; Thu, 17 Jan 2019 17:10:02 +0100 Date: Thu, 17 Jan 2019 17:10:02 +0100 From: Henning Schild To: Baurzhan Ismagulov Cc: isar-users Subject: Re: https://github.com/ilbers/hello conflicts with upstream hello Message-ID: <20190117171002.3b6dfdac@md1za8fc.ad001.siemens.net> In-Reply-To: <20190117152809.GK12226@yssyq.m.ilbers.de> References: <20190117160301.6928bd98@md1za8fc.ad001.siemens.net> <20190117152809.GK12226@yssyq.m.ilbers.de> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: 6rc6pZ3F2MDg Am Thu, 17 Jan 2019 16:28:09 +0100 schrieb Baurzhan Ismagulov : > 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? Yes, but conflicts that are known are mentioned in the metadata. (debian/control) So apt sees it before dpkg unpacks it and finds it. I just sent a series that shows the problem. You can also see it if you IMAGE_INSTALL=example-hello and IMAGE_PREINSTALL=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. That or the metadata should know about the conflict. We can not change upstream metadata, maybe one side is good enough. One way or another. My series adds the feature to rebuild an upstream package, and hello is a very good example for that. A conflict would mean we could not test example-hello and hello in the same image, so avoiding the conflict will be useful for that case and not overkill. Henning > > With kind regards, > Baurzhan. >