Bug#677784: marked as done (cpp-4.7: Please mark package as Multi-Arch: foreign)
Your message dated Sun, 17 Jun 2012 13:03:46 +0200
with message-id <E1SgDGk-0004eG-VG@frosties.localnet>
and subject line Undoing cpp-4.7: Please mark package as Multi-Arch: foreign
has caused the Debian Bug report #677784,
regarding cpp-4.7: Please mark package as Multi-Arch: foreign
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.)
--
677784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677784
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-4.7
Version: 4.7.1-1
Severity: normal
Hi,
one of the (many many many) packages in ia32-libs has a dependency on
cpp-4.7. Please mark the cpp-4.7 package as Multi-Arch: foreign so
that the dependency can be fullfilled by the native architecture.
More info: http://wiki.debian.org/ReleaseGoals/MultiArch
http://wiki.debian.org/Multiarch/Implementation
MfG
Goswin
-- System Information:
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
--- End Message ---
--- Begin Message ---
- To: 677784-done@bugs.debian.org
- Subject: Undoing cpp-4.7: Please mark package as Multi-Arch: foreign
- From: Goswin von Brederlow <goswin-v-b@web.de>
- Date: Sun, 17 Jun 2012 13:03:46 +0200
- Message-id: <E1SgDGk-0004eG-VG@frosties.localnet>
Hi,
I tracked down the dependency on cpp-4.7 to libidl0. The multiarch patch
for libidl0 already has a workaround for the cpp problem and setting cpp-4.7
to M-A: foreign wouldn't be quite right due to its architecture dependend
behaviour. So I'm closing this bug. Sorry for the noise.
MfG
Goswin
--- End Message ---
Reply to: