Package: crossfire-common
Version: 1.8.0-1

While testing crossfire-server upgrades from sarge to etch to sid with
piuparts, I get the problem that dpkg complains that the
conffile /etc/crossfire/exp_table has been modified by me (which I
obviously didn't) or a script (which would be in one of the crossfire
packages). This kind of problem (assuming it is a problem in the package
and not in my test setup; if the latter, please yell at me) is
detrimental to smooth upgrading from Debian release to release.
Obviously, if the sysadmin has modified the conffile, prompting will
happen, but if they haven't, prompting shouldn't happen. 

The hopefully relevant snippet from the log file:

  Setting up crossfire-maps (1.8.0-2) ...
  Setting up crossfire-common (1.8.0-1) ...

  Configuration file `/etc/crossfire/exp_table'
   ==> 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     : background this process to examine the situation
   The default action is to keep your current version.
  *** exp_table (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing
crossfire-common (--configure):
   EOF on stdin at conffile prompt
  dpkg: dependency problems prevent configuration of crossfire-server:
   crossfire-server depends on crossfire-common; however:
    Package crossfire-common is not configured yet.
  dpkg: error processing crossfire-server (--configure):
   dependency problems - leaving unconfigured

The log file is about 180 kilobytes, so I won't attach it to this bug
report, but I gladly mail it on request. The command I used was " sudo
piuparts -ab sarge.tar.gz -d sarge -d etch -d sid crossfire-server",
where sarge.tar.gz was built with "sudo piuparts -s sarge.tar.gz -d
sarge hello".

-- 
RFC 1437 - yet another MIME specification Microsoft ignores



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to