package apache2.2-common 2.2.8-1 failed to install/upgrade:

Bug #221932 reported by Nizar Kerkeni
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)
Fix Released
Low
Unassigned
Hardy
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: apache2

fail to upgrade from gutsy server to hardy server

ProblemType: Package
Architecture: i386
Date: Fri Apr 25 16:03:13 2008
DistroRelease: Ubuntu 8.04
ErrorMessage:
 ErrorMessage: le sous-processus post-installation script a retourné une erreur de sortie d'état 1
Package: apache2.2-common 2.2.8-1
PackageArchitecture: i386
SourcePackage: apache2
Title: package apache2.2-common 2.2.8-1 failed to install/upgrade:
Uname: Linux 2.6.22-14-server i686

Revision history for this message
Nizar Kerkeni (nizarus) wrote :
Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi there
could you please provide the full error message, hopefully in english, you can accomplish this by preceding the "LC_ALL=C" environment variable to your command, this is without the quotation symbols, I.E.:

LC_ALL=C sudo apt-get -f install

Thanks in advance.

Changed in apache2:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Mathias Gug (mathiaz) wrote :

Could you also post the log messages related to the dist-upgrade (found in /var/log/dist-upgrade) ?

Revision history for this message
Nizar Kerkeni (nizarus) wrote :

~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
6 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up apache2.2-common (2.2.8-1) ...
cp: not writing through dangling symlink `/var/www/index.html'
dpkg: error processing apache2.2-common (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of apache2-mpm-prefork:
 apache2-mpm-prefork depends on apache2.2-common (= 2.2.8-1); however:
  Package apache2.2-common is not configured yet.
dpkg: error processing apache2-mpm-prefork (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of apache2:
 apache2 depends on apache2-mpm-worker (>= 2.2.8-1) | apache2-mpm-prefork (>= 2.2.8-1) | apache2-mpm-event (>= 2.2.8-1); however:
  Package apache2-mpm-worker is not installed.
  Package apache2-mpm-prefork is not configured yet.
  Package apache2-mpm-event is not installed.
dpkg: error processing apache2 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libapache2-mod-php5:
 libapache2-mod-php5 depends on apache2-mpm-prefork (>> 2.0.52) | apache2-mpm-itk; however:
  Package apache2-mpm-prefork is not configured yet.
  Package apache2-mpm-itk is not installed.
 libapache2-mod-php5 depends on apache2.2-common; however:
  Package apache2.2-common is not configured yet.
dpkg: error processing libapache2-mod-php5 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of php5:
 php5 depends on libapache2-mod-php5 (>= 5.2.4-2ubuntu5) | php5-cgi (>= 5.2.4-2ubuntu5); however:
  Package libapache2-mod-php5 is not configured yet.
  Package php5-cgi is not installed.
dpkg: error processing php5 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of php5-gd:
 php5-gd depends on phpapi-20060613+lfs; however:
  Package phpapi-20060613+lfs is not installed.
  Package libapache2-mod-php5 which provides phpapi-20060613+lfs is not configured yet.
dpkg: error processing php5-gd (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 apache2.2-common
 apache2-mpm-prefork
 apache2
 libapache2-mod-php5
 php5
 php5-gd
E: Sub-process /usr/bin/dpkg returned an error code (1)

Revision history for this message
Nizar Kerkeni (nizarus) wrote :

The log files

Revision history for this message
Chuck Short (zulcss) wrote :

Which version of php5-gd are you using and where did it come from?

Thanks
chuck

Revision history for this message
Stefan Fritsch (sf-sfritsch) wrote :

This is a bug in apache2.2-common's postinst (doesn't check for dangling symlinks). The fix will be in 2.2.8-4:

http://svn.debian.org/wsvn/pkg-apache/trunk/apache2/apache2.2-common.postinst?op=diff&rev=658&sc=1

Revision history for this message
Chuck Short (zulcss) wrote :

As per above this is a bug in apache2.2-common's postinst (doesn'c check for dangling symlinks). I have backported the fix from intrepid to hardy.

I have attached the debdiff that includes the fix.

TEST CASE:

1. Install gutsy in a kvm session
2. Creating a dangling symlink for index.html
3. Upgrade to hardy.

If you have any questions please feel free to let me know.

Thanks
chuck

Revision history for this message
Martin Pitt (pitti) wrote :

According to comment 7 this should be fixed in intrepid:

   apache2 | 2.2.8-4 | intrepid | source, all

Changed in apache2:
status: Incomplete → Fix Released
status: New → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

Accepted into -proposed, please test and give feedback here

Revision history for this message
Martin Pitt (pitti) wrote :

Any testers?

Revision history for this message
Nizar Kerkeni (nizarus) wrote :

Installed from proposed and no problems to report in my case.

Revision history for this message
Martin Pitt (pitti) wrote :

I actually meant a gutsy -> hardy-proposed update of apache.

Revision history for this message
Albert Damen (albrt) wrote :

+1

Created a dangling symlink (/var/www/index.html -> /home/ubuntu/fake, cat: /var/www/index.html: No such file or directory) and tried to upgrade from gutsy to hardy. The upgrade failed with -proposed disabled and succeeded with -proposed enabled. Tested in kvm VM.

Revision history for this message
Martin Pitt (pitti) wrote :

Copied to hardy-updates.

Changed in apache2:
status: Fix Committed → Fix Released
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.