Bug#325551: How to handle filename conflict "aleph" (Packages aleph, tetex-bin, texlive-bin)?
- To: Andreas Barth <aba@not.so.argh.org>
- Cc: Thomas Bushnell <tb@becket.net>, debian-tex-maint@lists.debian.org, 325551@bugs.debian.org, 389163@bugs.debian.org, 379564@bugs.debian.org, paul-debian@home.paulcager.org
- Subject: Bug#325551: How to handle filename conflict "aleph" (Packages aleph, tetex-bin, texlive-bin)?
- From: Frank Küster <frank@kuesterei.ch>
- Date: Wed, 13 Dec 2006 15:09:42 +0100
- Message-id: <[🔎] 86d56nnazd.fsf@alhambra.kuesterei.ch>
- Reply-to: Frank Küster <frank@kuesterei.ch>, 325551@bugs.debian.org
- In-reply-to: <[🔎] 20061212205015.GX2733@mails.so.argh.org> (Andreas Barth's message of "Tue\, 12 Dec 2006 21\:50\:15 +0100")
- References: <[🔎] 86u0003lz6.fsf@alhambra.kuesterei.ch> <[🔎] 20061212205015.GX2733@mails.so.argh.org>
Andreas Barth <aba@not.so.argh.org> wrote:
> Why is it better than to drop aleph? If a package is way outdated, and
> RC buggy, and also aleph is practically unchanged since Sarge, I think
> that is still grounds for a removal.
I haven't investigated about aleph. I just thought that, since it
doesn't have many bugs, even the current version might be useful, and
better than nothing.
If Thomas packages afnix (together with Paul or separately), that's
probably the best choice. From a technical point of view, the package
names could also stay the same, so that we don't need to wait for NEW
processing (but you RMs might have a magic wand to speed up that?)
Regards, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
Reply to: