Your message dated Sun, 16 Jan 2005 21:03:18 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug no longer relevant, so closing
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; 10 Nov 2003 03:45:55 +0000
>From [EMAIL PROTECTED] Sun Nov 09 21:45:46 2003
Return-path: <[EMAIL PROTECTED]>
Received: from 64-89-121-30.arpa.kmcmail.net (Matt) [64.89.121.30]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AJ2zq-0005df-00; Sun, 09 Nov 2003 21:45:46 -0600
Received: from matthew by Matt with local (Exim 4.22)
id 1AJ3Br-0001OT-4r; Sun, 09 Nov 2003 21:58:11 -0600
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Matthew A. Nicholson" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kcontrol: /usr/bin/fileshareset broken
X-Mailer: reportbug 2.36
Date: Sun, 09 Nov 2003 21:58:09 -0600
Message-Id: <[EMAIL PROTECTED]>
Sender: "Matthew A. Nicholson" <[EMAIL PROTECTED]>
X-BadReturnPath: [EMAIL PROTECTED] rewritten as [EMAIL PROTECTED]
using "From" header
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-1.3 required=4.0
tests=FORGED_YAHOO_RCVD,HAS_PACKAGE
version=2.53-bugs.debian.org_2003_11_9
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_11_9
(1.174.2.15-2003-03-30-exp)
Package: kcontrol
Version: 4:3.1.3-1
Severity: normal
The /usr/bin/fileshareset script that is used to add a share to an nfs
or smb config is broken.
The scrpt appears to be written for Mandrake linux, and makes refrence
to /sbin/pidof which should be /bin/pidof in debian.
Another similar problem near the end of the file the /etc/init.d/smb
file is refrenced which should be /etc/init.d/samba and it is told to
stop, start, which could(/should?) be replaced by restart.
Also as it is installed the script does not have the right permissions
to edit /etc/samba/smb.conf, the file that it needs to update to add and
subtract shares. Even after I modified the permissions of smb.conf to
make it part of the samba group, and group writable (and added myself to
the samba group) the shares did not operate properly although they were
added. Perhaps the options set when adding a share should be adjusted.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux Matt 2.6.0-test9 #1 Mon Oct 27 13:21:13 CST 2003 i686
Locale: LANG=en_US, LC_CTYPE=en_US
Versions of packages kcontrol depends on:
ii kdelibs4 4:3.1.4-2 KDE core libraries
ii libart-2.0-2 2.3.16-1 Library of functions for 2D graphi
ii libasound2 0.9.6-3 Advanced Linux Sound Architecture
ii libc6 2.3.2.ds1-9 GNU C Library: Shared libraries an
ii libfam0c102 2.6.10-4 client library to control the FAM
ii libfontconfig1 2.2.1-8 generic font configuration library
ii libfreetype6 2.1.5-3 FreeType 2 font engine, shared lib
ii libgcc1 1:3.3.2-1 GCC support library
ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
ii libpcre3 4.3-3 Philip Hazel's Perl 5 Compatible R
ii libpng12-0 1.2.5.0-4 PNG library - runtime
ii libqt3c102-mt 3:3.2.1-6 Qt GUI Library (Threaded runtime v
ii libssl0.9.7 0.9.7c-5 SSL shared libraries
ii libstdc++5 1:3.3.2-1 The GNU Standard C++ Library v3
ii libxrender1 0.8.3-4 X Rendering Extension client libra
ii xlibs 4.3.0-0pre1v4 X Window System client libraries
ii zlib1g 1:1.1.4-16 compression library - runtime
-- no debconf information
---------------------------------------
Received: (at 219906-done) by bugs.debian.org; 17 Jan 2005 02:03:29 +0000
>From [EMAIL PROTECTED] Sun Jan 16 18:03:29 2005
Return-path: <[EMAIL PROTECTED]>
Received: from tomts25-srv.bellnexxia.net [209.226.175.188]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CqMEo-0002G9-00; Sun, 16 Jan 2005 18:03:26 -0800
Received: from [192.168.0.100] ([70.49.17.55])
by tomts25-srv.bellnexxia.net
(InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP
id <[EMAIL PROTECTED]>;
Sun, 16 Jan 2005 21:03:22 -0500
From: Christopher Martin <[EMAIL PROTECTED]>
Reply-To: Christopher Martin <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Bug no longer relevant, so closing
Date: Sun, 16 Jan 2005 21:03:18 -0500
User-Agent: KMail/1.7.1
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
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=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 31
Hello,
This bug is being closed because of its age and the vanishingly small
chance that it is still relevant to the current KDE packages, as it was
clearly since fixed, a random unreproducible bug that never had enough of
a follow-up to be useful, or else was forwarded upstream, where it was
marked fixed some time ago.
In case I'm mistaken, please do re-open the bug report in question, and
explain how the report is still relevant.
Thanks,
Christopher Martin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
