[Pkg-telepathy-maintainers] Bug#601026: telepathy-logger: daemon should probably hard-depend on the same version of the library

Will Thompson will at willthompson.co.uk
Fri Oct 22 16:30:17 UTC 2010

Package: telepathy-logger
Version: 0.1.6-1
Severity: normal

Today I hit the bug I fixed for 0.1.6 again, despite believing that I'd
upgraded the logger. But it turns out I'd only upgraded the daemon, not
its guts.

Is there any reason not to make the daemon depend on the exact version
of the library, particularly since they're built from the same source
tree and aren't really meaningfully separate?

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.35-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages telepathy-logger depends on:
ii  libc6                      2.11.2-6      Embedded GNU C Library: Shared lib
ii  libdbus-1-3                1.2.24-3      simple interprocess messaging syst
ii  libdbus-glib-1-2           0.88-2        simple interprocess messaging syst
ii  libglib2.0-0               2.26.0-1      The GLib library of C routines
ii  libsqlite3-0               3.7.2-1       SQLite 3 shared library
ii  libtelepathy-glib0         0.13.2-1~ccu1 Telepathy framework - GLib library
ii  libtelepathy-logger1       0.1.5-1       Telepathy logger service - utility
ii  libxml2                    2.7.7.dfsg-4  GNOME XML library

Versions of packages telepathy-logger recommends:
ii  libdconf0                     0.5.1-1    Simple key-based configuration sys

telepathy-logger suggests no packages.

-- no debconf information

More information about the Pkg-telepathy-maintainers mailing list