Installation fails if no DBMS is available

Bug #65933 reported by Lorenzo J. Lucchini
12
Affects Status Importance Assigned to Milestone
Dapper Backports
Invalid
Undecided
Tollef Fog Heen
Edgy Backports
Invalid
Undecided
Tollef Fog Heen
phpgroupware (Debian)
Fix Released
Unknown
phpgroupware (Ubuntu)
Fix Released
Undecided
Unassigned
Dapper
Invalid
Undecided
Unassigned
Edgy
Won't Fix
Undecided
Unassigned

Bug Description

The phpgroupware package only lists "postgresql | mysql-server" as a Suggests, not as a strict dependency. However, when installing without any DBMS available, dpkg reports the following error:

[...]
Setting up wwwconfig-common (0.0.46) ...
Setting up phpgroupware-phpgwapi (0.9.16.011-2) ...
Setting up phpgroupware-setup (0.9.16.011-2) ...
Setting up phpgroupware-admin (0.9.16.011-2) ...
Setting up phpgroupware-preferences (0.9.16.011-2) ...
Setting up phpgroupware (0.9.16.011-2) ...
setting up apache
setting up apache-ssl
setting up apache-perl
setting up apache2
/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
E: Sub-process /usr/bin/dpkg returned an error code (1)

Changed in phpgroupware:
status: Unknown → Unconfirmed
Revision history for this message
Kai Kasurinen (kai-kasurinen) wrote :

Thanks for the bug report.

I'm closing this bug because it has been fixed in Feisty.

phpgroupware (0.9.16.011-2.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Add missing depends on mysql-client | postgresql-client, since these
     are used in the package's postinst (Closes: #398635).
   * Update FSF address in debian/*copyright.

Changed in phpgroupware:
status: Unconfirmed → Fix Released
Changed in phpgroupware:
status: Unknown → Fix Released
Revision history for this message
Rouben (rouben) wrote :

Requesting backports to Edgy and Dapper from Feisty to fix the issue. This should be a no brainer, since there's no actual "porting" involved.

DEB builds fine on dapper and edgy, therefore:
+1 for edgy and
+1 for dapper.

Revision history for this message
Martin Meredith (mez) wrote : Re: [Bug 65933] Re: Installation fails if no DBMS is available

Approved for backporting to edgy and dapper (backports fine in prevu)

 subscribe ubuntu-archive
 status inprogress

Changed in dapper-backports:
status: Unconfirmed → In Progress
John Dong (jdong)
Changed in edgy-backports:
status: Unconfirmed → In Progress
Revision history for this message
Tollef Fog Heen (tfheen) wrote :

Backports are not a substitute for SRUs, please do a proper SRUs for problems making the package uninstallable.

Changed in dapper-backports:
assignee: nobody → tfheen
status: In Progress → Rejected
Changed in edgy-backports:
assignee: nobody → tfheen
status: In Progress → Rejected
Revision history for this message
Martin Meredith (mez) wrote :

Confirmed- subscribed motu-sru

Changed in phpgroupware:
status: Unconfirmed → Confirmed
status: Unconfirmed → Confirmed
Revision history for this message
StefanPotyra (sistpoty) wrote :

Unsubscribing motu-sru and subscribing MOTU instead.

Please follow https://wiki.ubuntu.com/MOTU/SRU and (re)subscribe motu-sru, once there is a debdiff to review, thanks.

Revision history for this message
Hew (hew) wrote :

Ubuntu Edgy Eft is no longer supported, so a SRU will not be issued for this release. Marking Edgy as Won't Fix.

Changed in phpgroupware:
status: Confirmed → Won't Fix
Revision history for this message
JC Hulce (soaringsky) wrote :

Thank you for reporting this bug to Ubuntu. The version of Ubuntu referenced in this issue has reached end of life, and the issue is fixed in newer versions of Ubuntu. Therefore, I am closing the Dapper task.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Changed in phpgroupware (Ubuntu Dapper):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.