Your message dated Wed, 25 Jan 2017 16:09:27 +0000
with message-id <e1cwq8v-0003i9...@fasolo.debian.org>
and subject line Bug#852516: fixed in request-tracker4 4.4.1-3
has caused the Debian Bug report #852516,
regarding request-tracker4: prompting due to modified conffiles which were not 
modified by the user: /etc/request-tracker4/RT_SiteConfig.pm
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 ow...@bugs.debian.org
immediately.)


-- 
852516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: request-tracker4
Version: 4.4.1-2
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
https://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."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://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.

This was observed during an upgrade from stretch to sid.

>From the attached log (scroll to the bottom...):

  Setting up request-tracker4 (4.4.1-2) ...
  
  Configuration file '/etc/request-tracker4/RT_SiteConfig.pm'
   ==> 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.
  *** RT_SiteConfig.pm (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing 
package request-tracker4 (--configure):
   end of file on stdin at conffile prompt
  Processing triggers for libc-bin (2.24-9) ...
  Errors were encountered while processing:
   request-tracker4


cheers,

Andreas

Attachment: request-tracker4_4.4.1-2.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Source: request-tracker4
Source-Version: 4.4.1-3

We believe that the bug you reported is fixed in the latest version of
request-tracker4, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominic Hargreaves <d...@earth.li> (supplier of updated request-tracker4 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Wed, 25 Jan 2017 15:22:46 +0000
Source: request-tracker4
Binary: request-tracker4 rt4-clients rt4-standalone rt4-fcgi rt4-apache2 
rt4-db-postgresql rt4-db-mysql rt4-db-sqlite rt4-doc-html
Architecture: source
Version: 4.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Request Tracker Group 
<pkg-request-tracker-maintain...@lists.alioth.debian.org>
Changed-By: Dominic Hargreaves <d...@earth.li>
Description:
 request-tracker4 - extensible trouble-ticket tracking system
 rt4-apache2 - Apache 2 specific files for request-tracker4
 rt4-clients - mail gateway and command-line interface to request-tracker4
 rt4-db-mysql - MySQL database backend for request-tracker4
 rt4-db-postgresql - PostgreSQL database backend for request-tracker4
 rt4-db-sqlite - SQLite database backend for request-tracker4
 rt4-doc-html - HTML documentation for request-tracker4
 rt4-fcgi   - External FastCGI support for request-tracker4
 rt4-standalone - Standalone web server support for request-tracker4
Closes: 852516 852522
Changes:
 request-tracker4 (4.4.1-3) unstable; urgency=medium
 .
   * Revert RT_SiteConfig.pm handling to ucf, for smoother upgrades
     (Closes: #852516)
   * Correct Conflicts/Replaces on rt4-extension-authenexternalauth
     (Closes: #852522)
   * Correct typo when removing obsolete update-rt-siteconfig alternatives
     to fix a piuparts issue
   * Correctly install rt-ldapimport manpage links
Checksums-Sha1:
 2e88c56b0f9da86ed62147f74ed4cb2dac732e47 5454 request-tracker4_4.4.1-3.dsc
 03591c7985a12ae8dfbd0d2fd294a91390e031aa 79040 
request-tracker4_4.4.1-3.debian.tar.xz
Checksums-Sha256:
 088e5f9b5cb4ec39b3a06be98e428cb602e3a0414d34d3e700b35484658c4a5b 5454 
request-tracker4_4.4.1-3.dsc
 44fa613d1f0af83b98625b48d52a634fc05c10b90a1c3e087f9b9cae2d520a67 79040 
request-tracker4_4.4.1-3.debian.tar.xz
Files:
 cf1c39f08d22babd0a94a08c2b11a1e9 5454 misc optional 
request-tracker4_4.4.1-3.dsc
 7a096e7e68a190f8164a4c4a9e758d71 79040 misc optional 
request-tracker4_4.4.1-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJYiMopAAoJEMAFfnFNaU+ydZcP/2jd4ujihcgVNT6xVNBUI50W
fx5gMSpg+/qnD1T1V5wPgMxYRSMmtGsXx0stMoIQPoLW8evQwFhphknFPAuoObFw
Oa5Oq/YXJMDUcqFmbZr352PvApkvBf3GxwcUsmA2Utjf4sg30red/ab+I0zzDJbQ
/8yduaYwRCO7+HuZfBJwwpPpdfMcY5Qcs+YYR2H1l0uhD5aQT85cwC9PwMgUZ4sI
BzbwCdHzr9qs0qZLzNJEV+QZsPl/cUsW8mzhgzd3V28W+QGs/wcZxMnLFyOQs3z8
pVdOlOSLMpwkUPzq1rm1R1xAZXf0o5v8U+Olrw+HObISn4LNijkiVFAn3n3FsmE7
EzWh2+Y11gqzPNFE1UCVat/0+bY/uvCSJ/EkEX1Czv24Ii2dgzpKx51zh0AKxjOr
zLTManUmt+eDnH8qzOXHeyJDMzHGPVmQSZEfzlwV0m6mrrpnj8Cjp6rYxsl//EYP
/rElWiNhavWmlYlWCJsNA62AhXwZ7InU6PNNahD9dXZkvAxWrwu0N5iVIg4V9Gp8
w0HlS5BATpGPGxA02pDni7jcbWybFnUuW8fdOYVHXLqLGQDSK4DEP0DcbSfEBe6e
yMv5y9x7ruYSVfqb1UCCjVWq6kpzvdwmuh9x0yJvnJU231v+27HGiI1yQxXHghpq
XtSqVUiyZf+lvJgdMvLe
=1fX5
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to