Daniel,
the speedy reply is just plain luck - I sometimes don't read this old
mail account for weeks or months.
Hi Schmitz--
On 11/15/2012 10:48 PM, schmitz wrote:
what you see is not a bug, but caused by your attempt to install a
powerpc package (which provides 'clock' separate from utli-linux') onto
a i386 Debian installation (which has 'clock' installed from it's
version of util-linux).
In a word: you cannot do this. Extract the powerpc package into a
separate directory tree using dpkg -x, please.
Thanks for the very speedy followup. What i'm trying to do should be
possible within debian's multiarch framework these days, but it think
the problem is that grub-ieee1275-bin isn't yet properly multiarch.
Thanks for pointing that out - I had skipped over the multiarch aspect
of your bug. I have no experience with multiarch packages, and would
need to take patches or hints from more knowledgeable developers.
I've opened http://bugs.debian.org/693400 to try to solve the underlying
problem (resolving that bug should make it so there is no attempt to
jointly install a powerpc version of powerpc-utils on the same system as
an i386 version of util-linux).
That might be a more generic way to flag and fix this. You might also
want to explore why grub-ieee1275-bin declares a dependency on
powerpc-utils in the first place - what component of powerpc-utils is
needed? As a workaround, such a component might be split off into a
separate package.
I'm a little surprised that apt let me get as far as i did without
declaring that there was a conflict ahead of time, though. Is it
possible to declare cross-architecture conflicts, now that there are the
possibilities of multi-architecture installs?
There are no conflicts declared at the package level - and that is all
apt does check (otherwise apt would need knowledge of the package's
files list, something that is internal to the package and not provided
by the package lists). It looks as though a cross arch conflict
declaration is necessary here. Such a thing may exist, I'm a bit rusty
on this.
This is likely a corner case and will only happen for packages that
provide architecture hardware support of some sort. Someone needs to go
through all package file lists and find potential conflicts in multiarch
situations - might be combinatorially hard to do that.
Cheers,
Michael
--dkg
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
