X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25]) by lists.alpinelinux.org (Postfix) with ESMTP id D2AEC5C4D9B for ; Tue, 2 Jan 2018 10:23:46 +0000 (GMT) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 9F9589E1ED5; Tue, 2 Jan 2018 10:23:46 +0000 (GMT) Received: from ncopa-desktop.copa.dup.pw (15.63.200.37.customer.cdi.no [37.200.63.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: n@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id 8844D9E1D76; Tue, 2 Jan 2018 10:23:45 +0000 (GMT) Date: Tue, 2 Jan 2018 11:23:40 +0100 From: Natanael Copa To: William Pitcock Cc: Oliver Smith , alpine-dev Subject: Re: [alpine-devel] Huh? Error reporter did not find the broken constraints. Message-ID: <20180102112340.2a2b3881@ncopa-desktop.copa.dup.pw> In-Reply-To: <20180102105540.2d175048@ncopa-desktop.copa.dup.pw> References: <20171231150048.044adbf9@ncopa-desktop.copa.dup.pw> <6bf51851-79fa-b9ff-3b0d-182358565e75@bitmessage.ch> <20180102105540.2d175048@ncopa-desktop.copa.dup.pw> X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.31; x86_64-alpine-linux-musl) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Tue, 2 Jan 2018 10:55:40 +0100 Natanael Copa wrote: > On Mon, 1 Jan 2018 22:49:07 -0600 > William Pitcock wrote: > > > Hello, > > > > On Mon, Jan 1, 2018 at 8:26 PM, William Pitcock > > wrote: > > > Hello, > > > > > > On Mon, Jan 1, 2018 at 7:19 PM, Oliver Smith > > > wrote: > > >> Sorry for not reporting it yet. > > >> > > >> In our case the bug was triggered by a "dbus-nox11" package we created - probably because it ended up providing the same "so:..." dependency as the official "dbus" package. It worked fine, and at some point (maybe after an apk upgrade?) the package didn't work anymore - after we removed it, it worked again. > > >> > > >> If it helps with debugging/fixing this issue, I could try to reproduce the way the bug affected us, and provide apk's installed DB. > > > > > > I think I can create a reproducer. I will do it after I finish cooking dinner. > > > > Unfortunately based on this data, I was unable to create a testcase. > > > > Adding two packages resulted in an unsatisfiable constraints problem, > > but it explained what the problem was (that it wanted the user to > > choose a provider). > > I did add those testcases to apk-tools git if you would like to look at them... > > > > Could somebody reproduce the failure with apk-tools git compiled with > > debug printing enabled? > > > > Thanks in advance! > > I have attached output from debug print. The problem is nvme-cli. ERROR PKG: nvme-cli: conflict: same name provided It seems that it comes from a local repository /home/ncopa/packages/testing where I have an older version of nvme-cli: $ tar -O -zxf /home/ncopa/packages/testing/x86_64/APKINDEX.tar.gz APKINDEX | grep -w -A 15 P:nvme-cli P:nvme-cli V:1.1-r0 A:x86_64 S:68384 I:192512 T:NVM-Express user space tooling for Linux U:https://github.com/linux-nvme/nvme-cli L:GPL o:nvme-cli m:Florian Heigl t:1482791353 c:3f5fcf3c09c78baca6ac5bde33ca8210aab75251 D:so:libc.musl-x86_64.so.1 p:nvme-cli C:Q135cWo/MbmAnhinSUHunVd/nBCcM= -- ... So it looks like I have a package named nvme-cli in community repo and an old version of nvme-cli in my local testing repo, which has a provides=nvme-cli for some reason. Some things that fixes my machine: - apk del nvme-cli - commenting out /home/ncopa/packages/testing in /etc/apk/repositories > > Thanks! > > -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---