Your message dated 
with message-id <[email protected]>
and subject line phpgroupware removed from Debian unstable
has caused the Debian Bug report #417556,
regarding phpgroupware: fails to install if no postgresql client is available
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.)


-- 
417556: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417556
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: phpgroupware
Version: 0.9.16.011-2.2, 0.9.16.011-3
Severity: serious
Justification: Policy violation (section 7.2)

hi,

while doing archive wide piuparts tests some packages using
wwwconfig-common failed to install because of postgresql not beeing
available (this is moodle, for example):

  Creating config file /etc/moodle/config.php with new version
   /usr/share/wwwconfig-common/pgsql.get: line 77: psql: command not found
  dpkg: error processing moodle (--configure):
   subprocess post-installation script returned error exit status 127
  Errors were encountered while processing:
   moodle
  E: Sub-process /usr/bin/dpkg returned an error code (1)

and phpgroupware:

   /usr/share/wwwconfig-common/pgsql.get: line 77: psql: command not found
  /usr/share/wwwconfig-common/pgsql.get: line 77: psql: command not found
  dpkg: error processing phpgroupware (--configure):
   subprocess post-installation script returned error exit status 1
  Errors were encountered while processing:
   phpgroupware

reading policy section 7.2 i get the impression this is not policy
compliant:

 "The Depends field should also be used if the postinst, prerm or postrm
  scripts require the package to be present in order to run."

which is imho the case here .. both wwwconfig-common and moodle to
Recommend/Suggest postgresql, but they should nevertheless be
installable if the Recommends/Suggests are not satisfied:

Suggests: 
  "[..] Using this field tells the packaging system and the user
  that the listed packages are related to this one and can perhaps enhance
  its usefulness, but that installing this one without them is perfectly
  reasonable."

just like dbconfig-common goes ahead with installing the package even
if there is no mysql/postgresql client available.

Other packages using wwwconfig--common, like libapache-mod-acct-mysql do
check for mysql client to be available before calling dbconfig-common:

    if [ -x $(which mysql) ]; then
            [...]
    else
        echo "Not configuring MySQL database because we cannot locate"
        echo "the mysql client executable (mysql-client package missing)."
    fi

i dont know wwwconfig-commons best practises here, im assigning the bugs
to the packages now, please merge and reassign to wwwconfig-common if
appropriate.

bye,
    - michael



--- End Message ---
--- Begin Message ---
Version: 1:0.9.16.016+dfsg-1+rm

phpgroupware has been removed from Debian unstable: 
http://bugs.debian.org/584986

Closing its bugs with a Version higher than the last unstable upload.

More information about this script at:
  
http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD


--- End Message ---

Reply via email to