Re: arch-specific dependencies and M-A: foreign

On Fri, Apr 17, 2015 at 03:39:14PM +0200, Johannes Schauer wrote: > > And is therefore also "bar" the same as "bar:amd64" > > no because different packages might provide "bar" and "bar:amd64". So even on > amd64 this dependency might be resolved differently. huh? Can you give an example? My poi

Re: [Multiarch-devel] arch-specific dependencies and M-A: foreign

Hi, Quoting David Kalnischkies (2015-04-18 17:24:45) > On Fri, Apr 17, 2015 at 03:39:14PM +0200, Johannes Schauer wrote: > > no because different packages might provide "bar" and "bar:amd64". So even > > on amd64 this dependency might be resolved differently. > > huh? Can you give an example? >

Re: DPKG-DEB error

Hi! This list is not for user support, but for dpkg development, you should use debian-us...@lists.debian.org instead. On Tue, 2015-04-07 at 14:14:19 -0400, Rajesh Krishnan wrote: > Hi I am trying to install a TI MultiCoreSDK for High Performance computing > application. The installation script w

dpkg, apt and dose3 do not agree in many synthetic dependency situations involving multiarch

Hi, when comparing dpkg, apt and dose3 behavior on 7744 synthetic test cases, then they disagree on 43.5% of them. I wrote a testsuite which tests the following setup: two packages pkga and pkgb are to be co-installed on a system with native architecture amd64 and foreign architecture i386. Both

Re: arch-specific dependencies and M-A: foreign

+++ David Kalnischkies [2015-04-17 11:27 +0200]: > Hi Multi-Archers! > > > Consider this situation: > > Native Architecture: amd64 > Foreign Architecture(s): i386 > > and these two packages: > > Package: foo > Architecture: amd64 > Depends: bar:i386 > > Package: bar > Architecture: amd64 > Mu

Re: arch-specific dependencies and M-A: foreign

+++ David Kalnischkies [2015-04-17 11:27 +0200]: > I never even considered that another way of interpreting it might exist > until my nose got rubbed in it yesterday…. Sorry - meant to ask: What was the case/bug/conversation that brought this up? Wookey -- Principal hats: Linaro, Debian, Wook

Re: arch-specific dependencies and M-A: foreign

Hi! On Fri, 2015-04-17 at 11:27:07 +0200, David Kalnischkies wrote: > Consider this situation: > > Native Architecture: amd64 > Foreign Architecture(s): i386 > > and these two packages: > > Package: foo > Architecture: amd64 > Depends: bar:i386 > > Package: bar > Architecture: amd64 > Multi-Ar

Re: [Multiarch-devel] arch-specific dependencies and M-A: foreign

On Sat, 2015-04-18 at 19:33:25 +0200, Johannes Schauer wrote: > Quoting David Kalnischkies (2015-04-18 17:24:45) > > What about a package blub2:i386 which Provides: bar ? Isn't that > > providing bar:i386 as well, because that is what bar stands for… ? > > On the other hand blub2:amd64 which 'Provi

Re: arch-specific dependencies and M-A: foreign

Hi! I think the rest is covered in my previous replies, otherwise I can tackle specific points I might have missed or that might be unclear. On Fri, 2015-04-17 at 15:39:14 +0200, Johannes Schauer wrote: > Quoting David Kalnischkies (2015-04-17 11:27:07) > > My personal opinion is (unsurprisingly