On Mon, Sep 03, 2012 at 12:21:06PM -0700, Russ Allbery wrote:
[...]
> linux-libc-dev maintainers, when upgrading to squeeze, there is currently
> nothing preventing linux-libc-dev from being upgraded to a version that
> uses multiarch paths in advance of upgrading any compiler to understand
> those paths, which results in a broken C compilation environment. In this
> case, this affected dkms, since dkms runs a compiler from postinst
> scripts.
linux-libc-dev is of course not used to build kernel modules. But
perhaps openafs also needlessly rebuilds userland code every time the
kernel is upgraded.
> I believe linux-libc-dev needs the same Breaks logic as
> libc6-dev, namely something like:
>
> Breaks: gcc-4.4 (<< 4.4.6-4), gcc-4.5 (<< 4.5.3-2), gcc-4.6 (<< 4.6.0-12)
That sounds plausible, yes.
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120903211640.gt29...@decadent.org.uk
