Philipp Kern <pk...@debian.org> writes:
> On Sat, Jun 30, 2012 at 11:24:04AM +0000, Debian Bug Tracking System wrote:
>> with the introduction of multi-arch in wheezy the ia32-libs package can
>> finally be retired. There will be a transitional package for ia32-libs
>> to help users migrate more smoothly to multi-arch but that package is
>> empty and depends on the relevant 32bit packages from i386 to preserve
>> functionality.
>>
>> Because of this I am closing this bug-report. If the problem still
>> exists under multi-arch then please file a new bug-report against the
>> relevant 32bit package directly.
>
> This problem pretty obviously cannot be solved with multiarch. You'd need to
> depend on the libacl1-dev package, which cannot be multiarch-ified with the
> current spec.
>
> Kind regards
> Philipp Kern
You can install libacl1-dev:i386 under multiarch which means the problem
is basically solved:
======================================================================
root@frosties:/# apt-get install --no-install-recommends libacl1-dev:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libattr1-dev:i386 libc-dev-bin libc6-dev:i386 linux-libc-dev:i386
Suggested packages:
glibc-doc:i386 manpages-dev:i386
Recommended packages:
manpages-dev gcc:i386 c-compiler:i386
The following NEW packages will be installed:
libacl1-dev:i386 libattr1-dev:i386 libc-dev-bin libc6-dev:i386
linux-libc-dev:i386
0 upgraded, 5 newly installed, 0 to remove and 104 not upgraded.
Need to get 6049 kB of archives.
After this operation, 21.9 MB of additional disk space will be used.
Do you want to continue [Y/n]?
======================================================================
>From the bug text I gather you have a workaround in some local
tivoli.deb that adds the link in postinst. Under multiarch build your
tivoli.deb as architecture i386 and add a dependency on libacl1-dev, if
you don't already have an i386 deb that does already do that. The only
snag with this is that the *-dev:i386 packages conflict with the
*-dev:amd64 packages. This obviously is a problem if you want to, for
example, be able to compile anything on the same system without a
chroot.
If that is a blocker for you then you can create a new package
tivoli-libacl1-so-link (Architecture: i386) that contains
/usr/lib/i486-linux-gnu/libacl.so -> ../libacl.so.1.1.0
diverts the file from libacl1-dev (so a future multiarch libacl1-dev can
be installed in parallel) and depends on libacl1. Unfortunately you
can't conflict on libacl1-dev as that afaik would also conflict
libacl1-dev:amd64. The diversion works around that.
In your tivoli.deb (rebuild as Architecture: i386) you use
Depends: libacl1-dev | tivoli-libacl1-so-link
That way you can install libacl1-dev:amd64 and tivoli-libacl1-so-link on
64bit systems and have a working tivoli.
MfG
Goswin
PS: Or just include that link and diversion in your tivoli.deb
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
