Package: xine-lib
Version: 1.1.8-4
Severity: serious

>From changelog.Debian:

,----
| xine-lib (1.1.8-4) unstable; urgency=low
| 
|   [Darren Salt]
|   [...] 
|   * Except for libxine1-doc, libxine1-bin and libxine-dev, symlink to
|     libxine1-bin's documentation. (AUTHORS is now in libxine1-bin.)
`----

This is not allowed by Debian policy, because the packages do *not*
depend _on the very same version_ of libxine1-bin, for instance libxine1-x
depends on libxine1-bin (<< 1.1.9), libxine1-bin (>= 1.1.8).  See
section 12.3 of the policy manual:

,----
|      `/usr/share/doc/<package>' may be a symbolic link to another directory
|      in `/usr/share/doc' only if the two packages both come from the same
|      source and the first package Depends on the second.[2]
| 
|      [...]
|   
| [2]  Please note that this does not override the section on changelog files
|      below, so the file `/usr/share/<package>/changelog.Debian.gz' must
|      refer to the changelog for the current version of <package> in
|      question.  In practice, this means that the sources of the target and
|      the destination of the symlink must be the same (same source package
|      and version).
`----


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22.15
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libxine1 depends on:
ii  libxine1-console              1.1.8-4    libaa/libcaca/framebuffer/directfb
ii  libxine1-misc-plugins         1.1.8-4    Input, audio output and post plugi
ii  libxine1-x                    1.1.8-4    X desktop video output plugins for

Versions of packages libxine1 recommends:
ii  libxine1-doc [libxine-doc]    1.1.8-4    the xine video player library, doc
ii  libxine1-ffmpeg               1.1.8-4    MPEG-related plugins for libxine1

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to