On Sat, May 22, 2004 at 11:27:35PM +0200, Thiemo Seufer wrote: > An Example: > Starting with 2.4.20, the mips cache code underwent major changes. This > broke the r4k-kn04 subarchitecture, and some of the r4k-ip22 machines. > Most of the latter were fixed relatively quickly, with improved > performance, but some remained flaky, and the former remained broken > until 2.4.25, when the mips kernels were synced up again. A single > kernel package would elevate this from the architecture level to a > problem for whole debian.
Huh? changes in the interface to arch/ are very rare in stable series. It's not that difficult to drop arch/ from an older release into a more modern kernel, although it should really be a last ressort for rare cases like the one above. This trades a one-time big diff for continues headache about security fixes, etc.. So it's a good thing. > > Handle them the same as everywhere? Urgend per-arch changes become > > NMU, if anything interesting for the others happened just make it a > > normal release. > > You can't do a source NMU for a single arch. That is, unless you are > proposing to do arch-specific source packages, which would waste about > 500 MB mirror space and traffic per version. Ah, okay.
