Your message dated Sun, 25 Mar 2012 23:11:28 +0900
with message-id 
<CADk97TwJSr7hvaLxqDcQ=3aREjZXGsqSNqHPAp8iO=qsejc...@mail.gmail.com>
and subject line Re: should /etc/default/kumofs stay a conffile ?
has caused the Debian Bug report #645096,
regarding should /etc/default/kumofs stay a conffile ?
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
645096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645096
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kumofs
Version: 0.4.13-1+b1
Severity: minor

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear Maintainer,

On a clean install kumofs says that /etc/default/kumofs has been
changed :

# LANG=C  aptitude install kumofs
The following NEW packages will be installed:
  kumofs libmsgpack-ruby1.8{a} libmsgpack3{a} libmsgpackc2{a} 
0 packages upgraded, 4 newly installed, 0 to remove and 269 not upgraded.
Need to get 0 B/611 kB of archives. After unpacking 1843 kB will be used.
Do you want to continue? [Y/n/?] 
Preconfiguring packages ...              
Selecting previously deselected package libmsgpack3.
(Reading database ... 361553 files and directories currently installed.)
Unpacking libmsgpack3 (from .../libmsgpack3_0.5.4-2_amd64.deb) ...
Selecting previously deselected package libmsgpackc2.
Unpacking libmsgpackc2 (from .../libmsgpackc2_0.5.4-2_amd64.deb) ...
Selecting previously deselected package libmsgpack-ruby1.8.
Unpacking libmsgpack-ruby1.8 (from .../libmsgpack-ruby1.8_0.4.5-1_amd64.deb) ...
Selecting previously deselected package kumofs.
Unpacking kumofs (from .../kumofs_0.4.13-1+b1_amd64.deb) ...
Processing triggers for man-db ...
Setting up libmsgpack3 (0.5.4-2) ...
Setting up libmsgpackc2 (0.5.4-2) ...
Setting up libmsgpack-ruby1.8 (0.4.5-1) ...
Setting up kumofs (0.4.13-1+b1) ...

Configuration file `/etc/default/kumofs'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** kumofs (Y/I/N/O/D/Z) [default=N] ? D

- --- /etc/default/kumofs 2011-10-12 15:32:12.000000000 +0200
+++ /etc/default/kumofs.dpkg-new        2010-09-05 18:50:17.000000000 +0200
@@ -1,13 +1,6 @@
- -###DO_NOT_EDIT_BELOW_THIS_LINE_DEBCONF###
- -# Run "dpkg-reconfigure kumofs" when you'd like to edit them.
- -
- -RUN_KUMO_MANAGER="yes"
- -KUMO_MANAGER_ARGS="-l localhost"
- -
- -RUN_KUMO_SERVER="yes"
- -KUMO_SERVER_ARGS="-m localhost -l localhost -s /var/lib/kumofs/kumofs.tch"
- -
- -RUN_KUMO_GATEWAY="yes"
- -KUMO_GATEWAY_ARGS="-m localhost -t 11211"
+# Defaults for kumofs initscript
+# sourced by /etc/init.d/kumofs
+# installed at /etc/default/kumofs by the maintainer scripts
 
+###DO_NOT_EDIT_BELOW_THIS_LINE_DEBCONF###
 ###DO_NOT_EDIT_ABOVE_THIS_LINE_DEBCONF###


/etc/default/kumofs is created by debconf, and provided by the 
package.

Il don't know if it is the best answer to this problem but maybe 
/etc/default/kumofs shouldn't be a conffile.

Sincerly,
     Jean Charles Delépine

- -- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kumofs depends on:
ii  adduser                3.113           
ii  debconf [debconf-2.0]  1.5.40          
ii  libc6                  2.13-18         
ii  libgcc1                1:4.6.1-4       
ii  libmsgpack-ruby1.8     0.4.5-1         
ii  libmsgpack3            0.5.4-2         
ii  libmsgpackc2           0.5.4-2         
ii  libssl1.0.0            1.0.0e-2        
ii  libstdc++6             4.6.1-4         
ii  libtokyocabinet8       1.4.37-6.1      
ii  ruby                   4.8             
ii  ruby1.8 [ruby]         1.8.7.352-2     
ii  zlib1g                 1:1.2.3.4.dfsg-3

kumofs recommends no packages.

kumofs suggests no packages.

- -- Configuration Files:
/etc/default/kumofs changed [not included]

- -- debconf-show failed

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk6VmHIACgkQNE22OINSnCpXLQCeOQfYzcKvBMeSj1QkjjdgJX3h
R6MAn1D/xnK5n99TbXbx3wo3aE0qVK2W
=gjdk
-----END PGP SIGNATURE-----



--- End Message ---
--- Begin Message ---
I removed debian/default file on 0.4.13-2.
The bug has been fixed.

Thanks,

-- 
Taku YASUI <[email protected]>


--- End Message ---

Reply via email to