Michael Meskes wrote: > Testing was created so we have something like a release candidate > continously evolving. So shouldn't that mean testing is in an > installable state all the time? But for several days now it is not. > libc6 in testing collides with php4 (<< 4.2.3-5) and php4 in testing is > 4.2.3-3. Isn't this a situation that should never happen? Or is this a > bug in one of the scripts? Or am I just making a mistake here? After a couple of thousands of complaints about glibc not entering testing it was forced into testing even though it was not quite ready. This was amply discussed on d-d and was actually announced: >From Anthony's announcement on d-d-announce: > php4 will be broken on all architectures. This will be fixed by the > removal of the Conflicts: line from the libc6 packages in a forthcoming > revision. It can be worked around by not upgrading until that version of > libc6 is available; by upgrading to php4 from unstable; or by manually > forcing the dependencies (and not using apt). Cheers T.
Attachment:
pgpzYSDoGy0tu.pgp
Description: PGP signature