1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#267204: libmodplug0: wrong dependency information in debian/control

    From Wolfgang Sourdeau@1:229/2 to All on Sat Aug 21 08:00:10 2004
    From: [email protected]

    Package: libmodplug0
    Version: 1:0.7-2
    Severity: important

    Hi Zed,


    By looking at the debian/control of libmodplug, I have noticed a few
    problems, one of which might affect other packages later.

    Here are my recommendations:
    - remove libglib2.0-dev and libxmms-dev from the build dependencies
    because they are not required to build the package, although this is not
    a serious problem per se.
    - it's untrue that libmodplug0 and libmodplug-dev "Replace" xmms-modplug
    Because xmms-modplug contain the plugin for XMMS while libmodplug is
    only a library that xmms-modplug uses.
    - also, I am not sure they conflict with it but it might be true... A
    conflict has to be indicated when file names within a package may conflict
    with filenames in another package.
    - the reason why I've set this report's severity to "important" is the
    following: libmodplug-dev depends on an unversioned libmodplug0. While
    this causes no problem for the moment, it might be the case later if,
    for example, the libmodplug.so file refers to another file than
    "libmodplug.so.0.0.0". In which case, the libmodplug.so of the -dev package
    won't be valid and the dependency information won't trigger the
    required update.
    So you have to indicate the version of the package. The debian scripts
    will do this for you if you write something like:
    "Depends: libmodplug0 (= ${Source-Version})". Source-Version will be
    replaced with whatever version string you have put in your changelog
    entry.


    Thanks!


    Wolfgang
    -- System Information:
    Debian Release: 3.1
    APT prefers unstable
    APT policy: (500, 'unstable')
    Architecture: i386 (i686)
    Kernel: Linux 2.6.7
    Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set to fr_CA.ISO8859-1)

    Versions of packages libmodplug0 depends on:
    ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an ii libgcc1 1:3.4.1-7 GCC support library
    ii libstdc++5 1:3.3.4-9 The GNU Standard C++ Library v3

    -- no debconf information


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

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Zed Pobre@1:229/2 to Wolfgang Sourdeau on Sat Aug 21 18:00:19 2004
    From: [email protected]

    On Sat, Aug 21, 2004 at 01:33:40AM -0400, Wolfgang Sourdeau wrote:

    By looking at the debian/control of libmodplug, I have noticed a few problems, one of which might affect other packages later.

    The cause of most of these things is leftover information from
    when libmodplug was built from the same package as xmms-modplug.


    Here are my recommendations:
    - remove libglib2.0-dev and libxmms-dev from the build dependencies
    because they are not required to build the package, although this is not
    a serious problem per se.

    Yep. This is a real bug. This used to be true, and isn't anymore.

    - it's untrue that libmodplug0 and libmodplug-dev "Replace" xmms-modplug
    Because xmms-modplug contain the plugin for XMMS while libmodplug is
    only a library that xmms-modplug uses.

    They do Replace the *older* version of xmms-modplug which
    included all the files in libmodplug0 and libmodplug-dev. If I change
    this, it will break upgrades from these very old versions.s


    - also, I am not sure they conflict with it but it might be true... A
    conflict has to be indicated when file names within a package may conflict
    with filenames in another package.

    I thought that was versioned, but I'm not at a computer right now
    where I can check. If it's versioned, this is still correct. If it's
    missing a version, then it's a bug.


    - the reason why I've set this report's severity to "important" is the
    following: libmodplug-dev depends on an unversioned libmodplug0. While
    this causes no problem for the moment, it might be the case later if,
    for example, the libmodplug.so file refers to another file than
    "libmodplug.so.0.0.0". In which case, the libmodplug.so of the -dev package
    won't be valid and the dependency information won't trigger the
    required update.

    I'll fix this in the next update (with luck, tomorrow).

    --
    Zed Pobre <[email protected]> a.k.a. Zed Pobre <[email protected]>
    PGP key and fingerprint available on finger; encrypted mail welcomed.

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.2.0 (GNU/Linux)

    iQEVAwUBQSdswx0207zoJUw5AQEKfQf/fuYsIOuyXzaNZ1AQIZu9EKbEU6MM/eGx jaFAIr7gfs/QzWvHcSDZD4CrZVRLp4eDEkRMnvmUhZ/AzM0U/siyHpupCkr6gOt2 xiXHZ5vztCnPVz4SUMSq6l1x4wUPvttSmkCWqZ2k97NUW6qmt5nNFB6sdAz2nkIC JrC9PLQ4gEdC9ejgvqdg0bUBllv8KV8dfwx+n0aV644NtHXCyPJIiUE8Y0LXleJz Fu1ntQJCfT/KhsPFc+9N3tDimLK+fI+Px/T7abv8B2PiGLrJcVFAOpwJt8ECpOCm 84H6bRTW+ICqEJq/ba9AX6WUvkM4aD+Qdj+lCyp0ZXOvvImEhFdgvA==
    =IuUS
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)