At Sun, 14 Dec 2003 00:08:45 -0500, C. Scott Ananian <[EMAIL PROTECTED]> wrote: > This bug upgrading libc6 on mips is actually a kernal bug with > interprocess communication, which makes the forked process appear to > have failed even when it did not. On MIPS, you *MUST* upgrade the > kernel *BEFORE* you upgrade libc6: if you do not, the broken libc6 > will make it impossible to revert to a previous libc without a > rescue disk or reinstallation. I believe that this condition is > serious enough to warrant a BIG warning/refusal-to-upgrade in the > libc6 package. IIRC, libc6 warns that "it may break some programs, > including perl" -- but doesn't state that among the programs it will > break is dpkg, which will severely Cramp Your Style. > > The solution, as suggested on the debian-mips mailing list, is to grab > the kernel-image-2.4.22-r4k-ip22 package from unstable, and force > an upgrade with 'dpkg --force-all'. Then you will need to install > the kernel with dvhtool and reboot *before* proceeding with the > upgrade to unstable. apt will initially complain heartily because > of broken dependencies; I forget the exact sequence of commands I needed > to use to satify these before the standard 'apt-get upgrade' would > work. > > IMHO, a fixed kernel-image for MIPS should be installed in the archives > which does *NOT* have dependencies which prevent it from being installed > from stable. Then libc-on-mips should depend on or suggest this > kernel-image package, and *refuse* to install unless the running kernel > is recent enough. (I think 2.4.19 is the first version that will work). > This will ensure that stable distributions will correctly dist-upgrade > to the next stable release (when it occurs).
From glibc 2.3.2.ds1-8, libc6.preinst checks kernel version on mips because of this IPC issue. I wonder why libc6.postrm in libc6 2.3.2-7 causes this error. Alexandre, please show us your kernel version. Moreover, please show us where your script was stopped. I think the recent version should work. Is this really "grave" bug? Is this bug happened on other mips users' machines? Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
