Bug#679526: Build-Depends on obsolete package ia32-libs-dev

June 29th, 2012 - 08:40 am ET by Goswin von Brederlow | Report spam
Package: zsnes
Version: 1.510+bz2-3
Severity: serious

Hi,

as has long been anounced ia32-libs-dev will not be in wheezy since
32bit support will be replaced by multiarch. Since your package still
Build-Depends on ia32-libs-dev this means it will no longer build from
source. Please multiarchify your package.

MfG
Goswin


Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash



To UNSUBSCRIBE, email to debian-bugs-rc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 7 repliesReplies Make a reply

Replies

#1 Ron
June 29th, 2012 - 10:10 am ET | Report spam
Hi,

On Fri, Jun 29, 2012 at 02:57:08PM +0200, Etienne Millon wrote:
* Fabian Greffrath [120629 14:44]:
> That's easier said than done. This week I tried to install
> zsnes:i386 on amd64 and it failed, because one of its dependencies
> was not yet multiarchyfied. I am looking at you, libao!

Hello,

As far as zsnes is concerned, I will upload a package removing
zsnes:amd64. Whether zsnes:i386 will be installable or not will then
only depend on #638741.



If zsnes really is i386-only, then that seems like the best answer to me.
It's not really blocked on libao being converted - at least not in the
sense that it will need further changes after it is, or can't change until
it is.

I only took over libao a few weeks ago, and I'm not really any more keen
to relocate all its files on the eve of the freeze than I was to do that
just a couple of weeks before it. I don't know if anybody else has done
a proper audit of this to be sure there will be no problems with its
plugins - a cursory glance seems to indicate they'll probably be ok, but
I'm far from being certain enough about that to do a "beat the freeze"
upload making this change.

This one had gone on my "worry about m-a for wheezy+1" list - when m-a
itself is hopefully a little more settled and some of its intrinsic
problems might actually have solutions. I might push one to experimental
in the meantime if there is real call for it - but I think it's way too
late to be experimenting with this in wheezy release candidates now.

Cheers,
Ron





To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Similar topics