Your message dated Thu, 08 Feb 2007 13:43:14 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#394584: lilypond-data: Should predepend on texlive or tetex
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: lilypond-data
Version: Should depend on tetex or texlive
Severity: wishlist

As it is now, lilypond-data PreDepends on tetex-bin, which make lilypond 
pulls in tetex.  Which is a problem if you have installed texlive instead
of tetex.

So lilypond-data should PreDepend on texlive-base-bin | tetex-bin
(or something like this). 

Yours
A Jackson

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-amd64
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)


--- End Message ---
--- Begin Message ---
Thomas Bushnell BSG <[EMAIL PROTECTED]> wrote:

> Anders Jackson <[EMAIL PROTECTED]> writes:
>
>> Package: lilypond-data
>> Version: Should depend on tetex or texlive
>> Severity: wishlist
>>
>> As it is now, lilypond-data PreDepends on tetex-bin, which make lilypond 
>> pulls in tetex.  Which is a problem if you have installed texlive instead
>> of tetex.
>>
>> So lilypond-data should PreDepend on texlive-base-bin | tetex-bin
>> (or something like this). 

The alternative on texlive has been added meanwhile, so I'm closing this
bug. 

Just a comment, with TeX maintainer hat on, to the rest of the
discussion in this bug:

> Why do texlive and tetex-bin conflict?

Because they provide binaries of the same name and functionality.

> It is not allowed for two Priority: optional packages to conflict.

Where do you get this impression from?
http://release.debian.org/etch_rc_policy.txt says:

,----
| If two packages cannot be installed together, one must list the other
| in its "Conflicts:" field.
| 
| [...]
| 
| Packages must not install programs in the default PATH with different
| functionality with the same file name, even if they Conflict:.
`----

teTeX and TeXLive both conform to this policy, and I also cannot find
anything in the Debian Policy that would disallow conflicting (and also,
nobody has ever complained).

In lenny, teTeX will be dropped, but this was not yet possible for
etch. 

Regards, Frank
-- 
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)

--- End Message ---

Reply via email to