Package: keystone Version: 2012.1~e4-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts
Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded... This is a violation of policy 10.7.3, see http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3, which says "[These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens." http://wiki.debian.org/DpkgConffileHandling should help with figuring out how to do this properly. In http://lists.debian.org/debian-devel/2009/08/msg00675.html and followups it has been agreed that these bugs are to be filed with severity serious. >From the attached log (scroll to the bottom...): [...] Selecting previously unselected package keystone. Unpacking keystone (from .../keystone_2012.1~e3-4_all.deb) ... [...] Setting up keystone (2012.1~e3-4) ... dbconfig-common: writing config to /etc/dbconfig-common/keystone.conf Creating config file /etc/dbconfig-common/keystone.conf with new version warning: database package not installed? sanity check failed for sqlite3. error encountered creating database: No sqlite3 client to execute. (have you installed the sqlite3 package?) dbconfig-common: keystone configure: noninteractive fail. dbconfig-common: keystone configure: ignoring errors from here forwards SUCCESS: Role Admin created successfully. SUCCESS: Role Member created successfully. SUCCESS: Role KeystoneAdmin created successfully. SUCCESS: Role KeystoneServiceAdmin created successfully. SUCCESS: Role sysadmin created successfully. SUCCESS: Role netadmin created successfully. invoke-rc.d: policy-rc.d denied execution of start. Processing triggers for python-support ... [...] Preparing to replace keystone 2012.1~e3-4 (using .../keystone_2012.1~e4-1_all.deb) ... invoke-rc.d: policy-rc.d denied execution of stop. Unpacking replacement keystone ... [...] Setting up keystone (2012.1~e4-1) ... Configuration file `/etc/keystone/keystone.conf' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. 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. *** keystone.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing keystone (--configure): EOF on stdin at conffile prompt cheers, Andreas
keystone_2012.1~e4-1.log.gz
Description: GNU Zip compressed data