On Fri, 01 Oct 2010 18:41:03 -
Steve Langasek wrote:
> Ah. But in that case, because the unpack ordering is not guaranteed,
> you would need to reinstall *both* binutils and binutils-multiarch,
The unpack ordering *could* be guaranteed as multistrap handles each
package individually. It is
On Fri, Oct 01, 2010 at 02:10:58PM -, Wookey wrote:
> The re-install issue is that we can't run pre-insts when doing the
> initial unpacking to make a system with multistrap (because multistrap
> is designed to work for cross rootfs creation). We have to use dpkg -X
> because dpkg --unpack does
The re-install issue is that we can't run pre-insts when doing the
initial unpacking to make a system with multistrap (because multistrap
is designed to work for cross rootfs creation). We have to use dpkg -X
because dpkg --unpack doesn't have a 'don't run preinsts' option.
The only useful thing m
This bug was fixed in the package multistrap - 2.1.6ubuntu3
---
multistrap (2.1.6ubuntu3) maverick; urgency=low
* cross/ubuntu/armel.conf: Set config to use maverick now that all the
packages are in the archive. LP: #646901
* Always use the host apt keyring when bootstrapping,
On Fri, Oct 01, 2010 at 02:05:17AM -, Wookey wrote:
> The binutils-multiarch re-install line is there because it is the fairly
> crufty way we deal with diversions. Nothing guarantees correct ordering
> (pre-depends ignored) so diverts may happen before the thing they direct
> are present. Si
The binutils-multiarch re-install line is there because it is the fairly crufty
way we deal with diversions.
Nothing guarantees correct ordering (pre-depends ignored) so diverts may happen
before the thing they direct are present. Simplest fix is to re-install any
package doing diversions at the
Attached is my proposed debdiff for this, fixing multistrap to use the
host keyring instead of turning off gpg checking. This is sufficient
for running multistrap with the ubuntu/armel profile from an existing
Ubuntu system (i.e., a system that has the Ubuntu keyring already in
trusted.gpg). It d
oh, why are we switching from g++-4.4-arm-linux-gnueabi to *gcc*-arm-
linux-gnueabi? The latter doesn't pull in g++, does it?
--
multistrap needs to be updated for new apt and cross-tools in main
https://bugs.launchpad.net/bugs/646901
You received this bug notification because you are a member o
as commented in bug #645147, I'm not going to upload anything to the
Ubuntu archive that forcibly bypasses apt's gpg checking. I'll have a
look at the apt bug.
[UbuntuToolchains]
-packages=g++-4.4-arm-linux-gnueabi linux-libc-dev-armel-cross
binutils-arm-linux-gnueabi
-source=http://archive.ub
It would be nice to remove the --force-yes stuff and more correctly deal
with archive-keyrings in chroot configs, but right now I don;t know how
to make that work (see
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/646499 )
--
multistrap needs to be updated for new apt and cross-tools in main
** Patch added: "multistrap-2.1.6ubuntu3.patch"
https://bugs.launchpad.net/bugs/646901/+attachment/1631574/+files/multistrap-2.1.6ubuntu3.patch
** Package changed: ubuntu => multistrap (Ubuntu)
** Changed in: multistrap (Ubuntu)
Status: New => Confirmed
** Changed in: multistrap (Ubu
11 matches
Mail list logo
