Hi Ben, I can certainly apply upstream openafs's patch to wheezy-backports, but the fact remains that a kernel update in stable changed the KPI, which hardly seems "stable".
I have only become the openafs maintainer relatively recently, so my apologies if this is well-trodden ground, but what is supposed to happen when the stable KPI changes? Is it really just that all consumers are supposed to scramble to update their packages? Thanks, Ben P.S. If I understand correctly, the issue with d_alias is that d_rcu was previously overlapping with d_child in a union, and that was incorrect/buggy. There was no need to move it to overlapping with d_alias other than to save a bit of space; the KBI was already changing, so the KPI could have been preserved by just moving d_child out of the union and accepting the extra space as the price of preserving the KPI. On Fri, 20 Mar 2015, Debian Bug Tracking System wrote: > Processing commands for [email protected]: > > > reassign 780865 openafs-modules-dkms > Bug #780865 [linux-headers-amd64] linux-headers-amd64: openafs-modules-dkms > no longer builds > Bug reassigned from package 'linux-headers-amd64' to 'openafs-modules-dkms'. > No longer marked as found in versions linux-latest/46. > Ignoring request to alter fixed versions of bug #780865 to the same values > previously set > > thanks > Stopping processing here. > > Please contact me if you need assistance. > -- > 780865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780865 > Debian Bug Tracking System > Contact [email protected] with problems > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
