What's causing the weird apt behaviour here is cascading from
libfreetype6-dev depending on "libc6-dev | libc-dev" which is entirely
pointless, since build-essential takes care of that. This doesn't seem
to be an uncommon thing for development packages to do, mind you, so
fixing it just in freetype doesn't help much. It's probably a practice
we should stamp out, regardless.
As for the libc6-dev recommends on a C compiler, that seems generally
sane, but perhaps it could be qualified with [any] or something? Are we
allowed to do that in dpkg deps yet, or only in build-depends?
** Package changed: eglibc (Ubuntu) => freetype (Ubuntu)
** Also affects: eglibc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: eglibc (Ubuntu)
Status: New => Triaged
** Changed in: freetype (Ubuntu)
Status: Triaged => New
** Changed in: eglibc (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/990982
Title:
[Multiarch] libfreetype6-dev:i386 dependencies issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/990982/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
