Bug#382669: gconf2: maintainer scripts introduce new dependencies
Emil Nowak
emil5 at go2.pl
Sat Aug 12 15:30:06 UTC 2006
Package: gconf2
Version: 2.14.0-4
Severity: normal
Normally upstream package of gvonf2 doesn't depend on python. In all other
distributions gconf2 also doesn't depend on python.
But in debian we have "gconf-schemas" script which is written in python, and
so all programs that need gconf now automatically depend on python.
I'm not sure but IMHO such "new dependencies" should be against debian policy.
What if libc6 guys decide to write some post-install script-helper with
JavaBeanShell ?
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)
Versions of packages gconf2 depends on:
ii gconf2-common 2.14.0-4 GNOME configuration database syste
ii libc6 2.3.6-15 GNU C Library: Shared libraries
ii libgconf2-4 2.14.0-4 GNOME configuration database syste
ii libglib2.0-0 2.10.3-1 The GLib library of C routines
ii libpopt0 1.10-2 lib for parsing cmdline parameters
ii libxml2 2.6.26.dfsg-2 GNOME XML library
ii psmisc 22.3-1 Utilities that use the proc filesy
ii python 2.3.5-11 An interactive high-level object-o
Versions of packages gconf2 recommends:
ii libgtk2.0-0 2.8.18-1 The GTK+ graphical user interface
-- no debconf information
More information about the Pkg-gnome-maintainers
mailing list