[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#626222: marked as done (dpkg-cross: does not honour -convert-anyway flag)

Your message dated Tue, 10 May 2011 08:40:52 +0100
with message-id <20110510084052.c82721ad.codehelp@debian.org>
and subject line Re: Bug#626222: dpkg-cross: does not honour -convert-anyway flag
has caused the Debian Bug report #626222,
regarding dpkg-cross: does not honour -convert-anyway flag
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
626222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626222
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: dpkg-cross
Version: 2.6.3
Severity: important

Hi,

  Since 2.6.3 version, dpkg-cross does not convert anyway packages:
  dpkg-cross -A -a armel -b libc-dev-bin_2.13-2_armel.deb
  dpkg-cross: Skipping Multi-Arch package 'libc-dev-bin_2.13-2_armel.deb'.

  On 2.6.2, used to do:
  dpkg-cross -A -a armel -b libc-dev-bin_2.13-2_armel.deb
  Building libc-dev-bin-armel-cross_2.13-2_all.deb
  dpkg-deb: building package `libc-dev-bin-armel-cross' in `./libc-dev-bin-armel-cross_2.13-2_all.deb'.

  That causes breakeage when building toolchains and I suspect it breaks xapt and other software.

Best regards,
  -- Héctor Orón

-- Package-specific info:

-- (/etc/dpkg-cross/cross-compile not submitted) --


-- System Information:
Debian Release: wheezy/sid
  APT prefers stable
  APT policy: (700, 'stable'), (600, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.37-1-686 (SMP w/2 CPU cores)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dpkg-cross depends on:
ii  cdebconf [debconf-2.0]    0.153+squeeze2 Debian Configuration Management Sy
ii  debconf [debconf-2.0]     1.5.38         Debian configuration management sy
ii  dpkg-dev                  1.16.0.2       Debian package development tools
ii  libconfig-auto-perl       0.34-1         magical config file parser
ii  libdebian-dpkgcross-perl  2.6.2          functions to aid cross-compiling D
ii  perl                      5.10.1-18      Larry Wall's Practical Extraction 

Versions of packages dpkg-cross recommends:
ii  fakeroot                      1.14.5-1   Gives a fake root environment

Versions of packages dpkg-cross suggests:
pn  binutils-multiarch            <none>     (no description available)

-- debconf information excluded

--- End Message ---
--- Begin Message --- 
notfound 626222 2.6.3
quit

On Tue, 10 May 2011 03:43:06 +0200
Hector Oron <zumbi@debian.org> wrote:

> Package: dpkg-cross
> Version: 2.6.3
> Severity: important
> 
> Hi,
> 
>   Since 2.6.3 version, dpkg-cross does not convert anyway packages:
>   dpkg-cross -A -a armel -b libc-dev-bin_2.13-2_armel.deb
>   dpkg-cross: Skipping Multi-Arch package 'libc-dev-bin_2.13-2_armel.deb'.

This is a Multi-Arch package, therefore if you want this processed,
pass the Multi-Arch flag: -M

See dpkg-cross (1)

Multiarch behaviour
       By default <dpkg-cross> does nothing with packages from Debian
which already support Multi-Arch - the package is simply copied to the
current work directory, if it does not already exist. Any package
containing a Multi-Arch: field in DEBIAN/control is skipped in this
manner.

       --convert-multiarch can be specified to instead force the
generation of a -<arch>-cross package with the files moved into the
conventional dpkg-cross locations.

       The Multiarch spec ensures that multiarch packages will only be
available from Debian mirrors once dpkg itself is capable of installing
the packages and installing a Multiarch package means being able to
install a 32bit multiarch package alongside a 64bit multiarch package.
Installing an armel multiarch package alongside an x86 multiarch
package is no different to 32bit vs 64bit. (What changes is how the
multiarch package itself handles the header files and pkg-config files.)


>   That causes breakeage when building toolchains and I suspect it breaks xapt and other software.

xapt has been explicitly modified to support this behaviour because the
behaviour is transitional - once a particular subset of packages are
properly Multi-Arch aware, builds can stop using this option.

http://packages.debian.org/changelogs/pool/main/e/emdebian-crush/current/changelog#version2.2.16

The switch exists in xapt  since 2.2.14 - I'll add documentation of the
switch similar to the docs for dpkg-cross.

-- 


Neil Williams
=============
http://www.linux.codehelp.co.uk/

Attachment: pgpAwxWBYLJeO.pgp
Description: PGP signature


--- End Message ---
Reply to: