How to handle filename conflict aleph (Packages aleph, tetex-bin, texlive-bin)?

2006-12-12 Thread Frank Küster
severity 389163 serious thanks Dear release team, I just noticed , Etch RC policy: | | | Packages must not install programs in the default PATH with | different functionality with the same file name, even if they | Conflict:. ` We've got a problem here, since all three

Re: How to handle filename conflict aleph (Packages aleph, tetex-bin, texlive-bin)?

2006-12-12 Thread Thomas Bushnell BSG
On Tue, 2006-12-12 at 21:20 +0100, Frank Küster wrote: We've got a problem here, since all three packages are in testing, provide /usr/bin/aleph, and conflict with each other (or rather, the *tex* packages conflict with aleph). Eek. The right solution to this would be to package the new

Re: How to handle filename conflict aleph (Packages aleph, tetex-bin, texlive-bin)?

2006-12-12 Thread Paul Cager
Frank Küster wrote: severity 389163 serious thanks Dear release team, I just noticed , Etch RC policy: | | | Packages must not install programs in the default PATH with | different functionality with the same file name, even if they | Conflict:. ` We've got