Steve Langasek <[EMAIL PROTECTED]> wrote: > On Wed, Oct 19, 2005 at 07:50:16PM +0200, Frank Küster wrote: >> Norbert Preining <[EMAIL PROTECTED]> wrote: > >> > How do we continue, Frank? I guess best is to do nothing and wait until >> > tetex3 hits testing, and everything is fixed. Or? > >> Yes, I think so. I fear the bug behind this is that one should not >> declare "Replaces" on a packages that may not be installed by the time >> of the installation or upgrade, in other words, it is only possible if >> the replacing package depends on the replaced package. > > That's not true. It's a dpkg bug if installing the replaced package after > the replacing package prevents the Replaces: from taking effect. Actually, > I was pretty sure this was a dpkg bug that's been *fixed* recently.
Vincent's statements whether he is using etch or sid were a little confusing, but since tetex-bin_2.0.2-31 is now only in etch, it might be that he is using this; and if that bug fix has not yet propagated to etch... Do you know which version of dpkg is supposed to fix this? Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
