From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6647481443636215808 X-Received: by 2002:a5d:6b52:: with SMTP id x18mr1052021wrw.19.1547744089338; Thu, 17 Jan 2019 08:54:49 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:b686:: with SMTP id g128ls221254wmf.8.gmail; Thu, 17 Jan 2019 08:54:48 -0800 (PST) X-Google-Smtp-Source: ALg8bN7EpRL+NxcaSSx7xm0zxnTtf7M2/RKmsUMsL7feErkVLWaKNF27S4UymLm/wmhZ+sc5+qiR X-Received: by 2002:a1c:9cc3:: with SMTP id f186mr1288652wme.11.1547744088897; Thu, 17 Jan 2019 08:54:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547744088; cv=none; d=google.com; s=arc-20160816; b=vCczdRof3oOmqdX+b5j9LZiMIPXGE941N/mCYICHA5KqnoMlZM9Vy75zDr0Btuz0Dx FCesJhx8C/jnwOfP9xJtlWd/pzt6fOzfh5eWCO9vy/WQXLBgBL/dwakoNsudLeoJbMFk eJcp8zTOCmo5/HwTGaeXrUHGCm9RyPkfQUro/KrvEPOV/5DHAvksseFLMmECGeOLEvme exzdrGoO5qNWAL+vo5eqg+HMaLPbvccEal1Lvo1NH27hbpTBezsL92OqY4VV7EMTvJD0 YQ1VS2/+kJ9Jd7TklsPsJF8XIMHekMDdQRzjhBxmv888Oxih3F1R6hURmTlAY6MOl+lz +chw== 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=3IBKZmRaFMl9pqztuQQKAnN8FuZtuITuNqnVJfd5pp8=; b=lmIMq/IDHDfZwD7BqWHTI7qGXtSdDJ/BHwHazsSWgyWfq/X/0YyEbdQZGlTPznalZA I56kiysK1PNFETnuGdZ2OGWTRAY+/37Ush1dSFU3/GQAfsh+HgBK3uLzTi3vc73sVS6k p1owkYyvJXHJx76kfNOPcFLNF3mCHFchFulgNSTZy4OY5ff72p7JCUi4FttRSr7kCGrA xeXYky5TYgwUArtElaKi4Hw2gyezt0e75elVbTh4HXAu3G++Rogy7HPMalYM4wc6RqKo 5WVbbWFY/9uLSY/EZbIwZHn73G1WOvmUgzSnigG20Mkrc+zPYUmbSLtjr2EYdm4Jwp2h r/OQ== 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 20si943553wmy.2.2019.01.17.08.54.48 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Jan 2019 08:54:48 -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 x0HGskHO008540 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 17 Jan 2019 17:54:47 +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 x0HGseoF013954 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 17 Jan 2019 17:54:41 +0100 Received: (from ibr@localhost) by yssyq.m.ilbers.de (8.15.2/8.15.2/Submit) id x0HGseim013953 for isar-users@googlegroups.com; Thu, 17 Jan 2019 17:54:40 +0100 Date: Thu, 17 Jan 2019 17:54:40 +0100 From: Baurzhan Ismagulov To: isar-users Subject: Re: https://github.com/ilbers/hello conflicts with upstream hello Message-ID: <20190117165440.GL12226@yssyq.m.ilbers.de> Mail-Followup-To: isar-users References: <20190117160301.6928bd98@md1za8fc.ad001.siemens.net> <20190117152809.GK12226@yssyq.m.ilbers.de> <20190117171002.3b6dfdac@md1za8fc.ad001.siemens.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190117171002.3b6dfdac@md1za8fc.ad001.siemens.net> User-Agent: Mutt/1.10.1 (2018-07-13) X-TUID: GWsreK8Hz71N On Thu, Jan 17, 2019 at 05:10:02PM +0100, Henning Schild wrote: > Yes, but conflicts that are known are mentioned in the metadata. > (debian/control) > So apt sees it before dpkg unpacks it and finds it. Conflicts: isn't the only way to handle various kinds of interoperability problems that arise in a large distribution like Debian. There are also diversions, which allow installing packages with conflicting files by renaming them in a controlled way after installation. > I just sent a series that shows the problem. You can also see it if you > IMAGE_INSTALL=example-hello and IMAGE_PREINSTALL=hello I see, thanks. I think we should use this opportunity to also rename the source package to hello-isar to avoid conflicts with apt-get source hello. > That or the metadata should know about the conflict. We can not change > upstream metadata, maybe one side is good enough. Conflicts: on the Isar side would be enough to make the packages incompatible, but apt-get installing example-hello after hello would fail. > 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. I agree that using upstream hello would be nice. An alternative could be building e.g. arc for the time being. In parallel, Maxim has started fixing example-hello. I'd prefer merging your code without breaking example-hello. With kind regards, Baurzhan.