On Sat, 2 Apr 2011 05:47:47 +0200
Guillem Jover wrote:
Adding linaro people and debian-embedded to CC:
> Hi!
>
> On Fri, 2011-04-01 at 22:31:07 +0100, Neil Williams wrote:
> > dpkg cannot be executed inside the chroot because it has not
> > necessarily been unpacked at this stage, it certainly
Hi!
On Fri, 2011-04-01 at 22:31:07 +0100, Neil Williams wrote:
> dpkg cannot be executed inside the chroot because it has not
> necessarily been unpacked at this stage, it certainly has not been
> configured. (dpkg is running from outside the chroot).
(An Essential package does not need to be con
On Fri, 1 Apr 2011 22:31:07 +0100
Neil Williams wrote:
> Inside:
> /home/test# dpkg-query --control-path libc6 postinst
> /var/lib/dpkg/info/libc6:amd64.postinst
>
> /home/test# dpkg-query --admindir /var/lib/dpkg --control-path libc6 control
> /var/lib/dpkg/info/libc6:amd64.control
>
> $ ls -l
On Thu, 3 Mar 2011 08:31:51 +0100
Raphael Hertzog wrote:
> > > 3/ Any program that assumes the current layout of control files
> > >(/var/lib/dpkg/info/.) will be broken (at
> > > least for some packages) since the layout will change to support
> > > Multi-Arch: same packages that can be co-i
Hi,
(I'm not commenting on the approach used by multistrap in general, I just
reply to your questions)
On Wed, 02 Mar 2011, Neil Williams wrote:
> What will happen with maintainer scripts of Multi-Arch packages when
> installed alongside native packages? Why are these being retained if
> they can
On Wed, 2 Mar 2011 15:06:11 +0100
Raphael Hertzog wrote:
> 1/ Anywhere where the user might specify a package name, he should be
> able to specifiy "package:arch" to cope with Multi-Arch: same
> packages that can be co-installed (e.g. libc6:i386 and libc6:amd64 on
> the same system). Those packag
6 matches
Mail list logo
