Bug#325551: Two disjunct aleph projects cause filename clash in Debian
Frank Küster <email@example.com> writes:
> Philippe Troin <firstname.lastname@example.org> wrote:
> >> Both programs provide the binary aleph, which means that currently they
> >> can hardly coexist. While it would certainly be possible to find a
> >> solution specific to Debian, I think both projects and their users
> >> benefit more if a we adopt a solution of general usefulness.
> >> What do you think?
> > Well the aleph (the language) project has been renamed to afnix, so as
> > soon as I have time to upload a new afnix package, the naming conflict
> > should disappear.
> I hoped something like this, since the homepage disappeared and
> information was so sparse.
> > However, I also plan to put an aleph "upgrade" package depending on
> > afnix. I don't think this will cause any inconvenience to the tetex
> > people, because as far as I understand, aleph will be part of the
> > tetex-bin package. Tetex-bin will have to conflict with a version of
> > the aleph package though.
> Yes, we'll do that. Which version will the upgrade package have?
I'll put a new epoch.
A 'Conflicts: aleph (<< 1:0)' should do.