The problem: All official Debian arches are eglibc based. So musl will never provide libc-dev for them. The main reason why the musl debian package exists is for bootstrapping a new debian port "musl-linux-armhf" which is already supported by dpkg. For that arch musl is providing the libc-dev package.
The solution: As discussed in the IRC channel #debian-devel, it is legitime to let musl-dev provide libc-dev, as long it does it only for this particular musl libc based architecture. I will remove the Provides: libc-dev from the package musl-dev until the new architecture musl-linux-armhf is bootstrapped and then limit the provide statement to: Provides: libc-dev [musl-linux-armhf] I hope this will solve the problem. On Fri, Oct 4, 2013 at 9:28 PM, Sven Joachim <svenj...@gmx.de> wrote: > Package: musl-dev > Version: 0.9.14-1 > Severity: serious > > Providing libc-dev in musl-dev is incorrect, since other -dev packages > that currently depend on libc-dev are not going to work with musl-dev > and need the eglibc libc-dev implementation. Please drop this Provides > from the package. > > > -- System Information: > Debian Release: jessie/sid > APT prefers unstable > APT policy: (500, 'unstable'), (101, 'experimental') > Architecture: i386 (x86_64) > > Kernel: Linux 3.11.3-nouveau (SMP w/2 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
