Your message dated Sat, 03 Dec 2005 21:17:06 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#325575: fixed in bandersnatch 0.4-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 29 Aug 2005 13:25:53 +0000
>From [EMAIL PROTECTED] Mon Aug 29 06:25:53 2005
Return-path: <[EMAIL PROTECTED]>
Received: from vpn12-189.users.lucky.net (148-66.trifle.net) [62.244.12.189]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E9je5-0004h1-00; Mon, 29 Aug 2005 06:25:53 -0700
Received: from localhost (localhost [127.0.0.1])
(uid 1001)
by tag with local; Mon, 29 Aug 2005 16:25:30 +0300
id 0008CE9D.43130CCA.00006887
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Wladimir Mutel <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: bandersnatch: has crippled sql script
X-Mailer: reportbug 3.17
Date: Mon, 29 Aug 2005 16:25:30 +0300
Message-ID: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
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
---------------------------------------
Received: (at 325575-close) by bugs.debian.org; 4 Dec 2005 05:21:08 +0000
>From [EMAIL PROTECTED] Sat Dec 03 21:21:08 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
id 1EimFG-0004dx-2y; Sat, 03 Dec 2005 21:17:06 -0800
From: Polkan Alexis Garcia Rodriguez <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.60 $
Subject: Bug#325575: fixed in bandersnatch 0.4-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sat, 03 Dec 2005 21:17:06 -0800
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Source: bandersnatch
Source-Version: 0.4-1
We believe that the bug you reported is fixed in the latest version of
bandersnatch, which is due to be installed in the Debian FTP archive:
bandersnatch-frontend_0.4-1_all.deb
to pool/main/b/bandersnatch/bandersnatch-frontend_0.4-1_all.deb
bandersnatch_0.4-1.diff.gz
to pool/main/b/bandersnatch/bandersnatch_0.4-1.diff.gz
bandersnatch_0.4-1.dsc
to pool/main/b/bandersnatch/bandersnatch_0.4-1.dsc
bandersnatch_0.4-1_all.deb
to pool/main/b/bandersnatch/bandersnatch_0.4-1_all.deb
bandersnatch_0.4.orig.tar.gz
to pool/main/b/bandersnatch/bandersnatch_0.4.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Polkan Alexis Garcia Rodriguez <[EMAIL PROTECTED]> (supplier of updated
bandersnatch package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sun, 30 Oct 2005 15:13:18 -0500
Source: bandersnatch
Binary: bandersnatch bandersnatch-frontend
Architecture: source all
Version: 0.4-1
Distribution: unstable
Urgency: low
Maintainer: Polkan Alexis Garcia Rodriguez <[EMAIL PROTECTED]>
Changed-By: Polkan Alexis Garcia Rodriguez <[EMAIL PROTECTED]>
Description:
bandersnatch - Log Jabber conversations to a peer-visible database
bandersnatch-frontend - Web interface to view logs of bandersnatch
Closes: 301889 301891 325575
Changes:
bandersnatch (0.4-1) unstable; urgency=low
.
* New upstream release
* New release 0.4 works fine with libnet-jabber-perl 2.0.x (closes: #301889)
* Correct the location of config file to bandersnatch-frontend and set
permissions to be readable only by root and the www-data user/group
(closes: #301891)
* Add jabber's configuration example to set correctly bandersnatch.
* New release have new sql schema file (closes: #325575)
Files:
c6e3dd0d85579cb04c92a2d3cf48d20e 622 net optional bandersnatch_0.4-1.dsc
4a0122ccff74282304efec2b396b0405 114827 net optional
bandersnatch_0.4.orig.tar.gz
bba448ec85098ca3d3fed33dfd2be7aa 16507 net optional bandersnatch_0.4-1.diff.gz
8649760f1cde1c34873bc27a446d49d8 60716 net optional bandersnatch_0.4-1_all.deb
7dab5ec6781d6dbe8f80faaf9c37abc6 53630 net optional
bandersnatch-frontend_0.4-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDkniZipBneRiAKDwRAmWYAJwKkcDKBu0ZDEri3fd6yo4++MIMTQCeJ/Vg
uwzrH0qQrwbk3w4IwKbeddY=
=jVA7
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
