tags 338638 -sarge stop Bill Allombert <[EMAIL PROTECTED]> wrote:
> tags 338638 sarge > quit Why do you believe so? As far as I remember the problem, it will be triggered when the sarge package is removed (instead of upgraded). Since this will be the case when upgrading to etch (I think the explanation is in the bug report), it's a problem for etch. I haven't had time to think about this and do any coding. But I believe it can only be solved by a upload *to*sarge*, because during etch upgrade there won't be a fallback maintainer script from a new version. The upload I did on this was rejected by the stable release manager. I always wanted to raise this issue again, now that there are new persons on this position. However, I think there was also a technical problem with the previous upload, therefore I didn't have time to actually do it. Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
