Your message dated Wed, 23 Feb 2005 06:28:22 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#296062: Bug has been fixed in 0.8.7-2
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; 19 Feb 2005 23:37:57 +0000
>From [EMAIL PROTECTED] Sat Feb 19 15:37:57 2005
Return-path: <[EMAIL PROTECTED]>
Received: from sccrmhc13.comcast.net [204.127.202.64]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D2eAf-0002jg-00; Sat, 19 Feb 2005 15:37:57 -0800
Received: from smtp.misumasu.dyndns.org (misumasu.dyndns.org[69.240.85.203])
by comcast.net (sccrmhc13) with ESMTP
id <2005021923372601600sbbcqe>; Sat, 19 Feb 2005 23:37:26 +0000
Received: from server.misumasu.dyndns.org (ip6-localhost [IPv6:::1])
by smtp.misumasu.dyndns.org (Postfix) with ESMTP id 7B4711177DB;
Sat, 19 Feb 2005 16:37:25 -0700 (MST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Michael Berg <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: smbldap-tools: Incorrect config file paths in smbldap_tools.pm
X-Mailer: reportbug 3.8
Date: Sat, 19 Feb 2005 16:37:25 -0700
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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: smbldap-tools
Version: 0.8.7-1
Severity: important
In the new version of smbldap-tools (0.8.7-1),
/usr/share/perl5/smbldap_tools.pm has the following at lines 32 and 33
my $smbldap_conf="/etc/opt/IDEALX/smbldap-tools/smbldap.conf";
my $smbldap_bind_conf="/etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf";
/etc/opt/IDEALX/smbldap-tools/ does not exist.
Because of this, the smbldap tools fail with error messages like:
# smbldap-userinfo -h
Unable to open /etc/opt/IDEALX/smbldap-tools/smbldap.conf for reading !
Compilation failed in require at /usr/sbin/smbldap-userinfo line 10, <DATA>
line 225.
BEGIN failed--compilation aborted at /usr/sbin/smbldap-userinfo line 10, <DATA>
line 225.
Everything works again after editing lines 32 and 33 in
/usr/share/perl5/smbldap_tools.pm to match the correct location in the file
system
of /etc/smbldap-tools/ (which is what was used in previous versions of this
package
and is more in line with the Debian file system standards).
my $smbldap_conf="/etc/smbldap-tools/smbldap.conf";
my $smbldap_bind_conf="/etc/smbldap-tools/smbldap_bind.conf";
This bug report should serve to document the fix/workaround for other users
until a new package can be released.
And let me just say "thank you" for maintaining this package.
I find this package very useful and have been using it for quite a while.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-k7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages smbldap-tools depends on:
ii libcrypt-smbhash-perl 0.02-6 generate LM/NT hash of a password
ii libio-socket-ssl-perl 0.96-1 Class implementing an object orien
ii libnet-ldap-perl 0.3202-2 A Client interface to LDAP servers
ii perl 5.8.4-6 Larry Wall's Practical Extraction
-- no debconf information
---------------------------------------
Received: (at 296062-done) by bugs.debian.org; 23 Feb 2005 05:28:54 +0000
>From [EMAIL PROTECTED] Tue Feb 22 21:28:54 2005
Return-path: <[EMAIL PROTECTED]>
Received: from 224.red-80-59-203.pooles.rima-tde.net (smtp.mixinet.net)
[80.59.203.224]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D3p4w-0004hc-00; Tue, 22 Feb 2005 21:28:54 -0800
Received: by smtp.mixinet.net (Postfix, from userid 1000)
id 25C7D44649D; Wed, 23 Feb 2005 06:28:22 +0100 (CET)
Date: Wed, 23 Feb 2005 06:28:22 +0100
From: Sergio Talens-Oliag <[EMAIL PROTECTED]>
To: "Berg, Michael" <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Re: Bug#296062: Bug has been fixed in 0.8.7-2
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="VS++wcV0S1rZb1Fb"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.6+20040907i
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-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
X-Spam-Level:
--VS++wcV0S1rZb1Fb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
El Tue, Feb 22, 2005 at 07:17:21PM -0700, Berg, Michael va escriure:
> This bug appears to have been fixed in smbldap-tools_0.8.7-2 and can be=
=20
> closed.
Yes, it shoud have been done automatically by the upload, but I've put
(Bug#296062) on the changelog instead of (Closes: Bug#296062).
Anyway, this message closes the bug, a patch for the path change has been
included on the package.
--=20
Sergio Talens-Oliag <[EMAIL PROTECTED]> <http://people.debian.org/~sto/>
Key fingerprint =3D 29DF 544F 1BD9 548C 8F15 86EF 6770 052B B8C1 FA69
--VS++wcV0S1rZb1Fb
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFCHBR1Z3AFK7jB+mkRAs+zAKDT5v0onACuQLffNdgwK+l8ooE3VwCg2bW/
QdUH6xqX7oCQH5bW8iBJOLQ=
=by81
-----END PGP SIGNATURE-----
--VS++wcV0S1rZb1Fb--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
