Package: bandersnatch Version: 0.3-2 Severity: normal
MySQL documentation recommends to use GRANT/REVOKE commands to manage user's permissions. While Bandersnatch HOWTO and their script (bandersnatch.sql) prefer to manipulate MySQL security tables directly (via INSERT), and then you have to restart MySQL. Very strange recipe, to my mind. So I would propose equivalent commands to be used instead : create database bandersnatch; grant usage on bandersnatch.* to [EMAIL PROTECTED] identified by 'bandersnatch'; grant select,insert,update,delete,create,drop on bandersnatch.* to [EMAIL PROTECTED] identified by 'bandersnatch'; use bandersnatch; #so that following commands know where to create their tables. Don't know if this proposal is to be pushed upstream, or made into patch to Debian package build. Hope there would be some reason/use in it. -- System Information: Debian Release: testing/unstable APT prefers breezy-updates APT policy: (500, 'breezy-updates'), (500, 'breezy-security'), (500, 'breezy'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12 Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8) Versions of packages bandersnatch depends on: ii libclass-dbi-perl 0.96-1 A convenient abstraction layer to ii libdbi-perl 1.48-1 Perl5 database interface by Tim Bu ii libnet-jabber-perl 2.0-2 Perl modules for accessing the Jab ii libxml-stream-perl 1.22-2 Perl module for accessing XML Stre ii perl 5.8.7-4 Larry Wall's Practical Extraction Versions of packages bandersnatch recommends: pn bandersnatch-frontend <none> (no description available) pn jabber | ejabberd <none> (no description available) ii mysql-client-4.1 [mysql-clien 4.1.13a-3 mysql database client binaries ii mysql-server-4.1 [mysql-serve 4.1.13a-3 mysql database server binaries -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
