Ubuntu
quagga package

Package breaks apt, then can't be removed

Bug #45761 reported by alp
18
Affects Status Importance Assigned to Milestone
quagga (Ubuntu)
Fix Released
High
Matthias Klose
Ubuntu ubuntu-7.04

Bug Description

The 'quagga' package in Dapper, once installed, prevents all other installed packages from being configured.

It additionally can't be removed without hacking /var/lib/dpkg/info/quagga.prerm changing an exit 1 to exit 0

This lead to a system running crippled for months, and nobody was able to fix it because they didn't have the knowhow to edit the .prerm file.

The problem has been observed on more than one system, including a production system running the latest Ubuntu release, so the problem has existed for some time.

Revision history for this message
James Green (james-green) wrote :

Version 6.06 server edition.

Quagga installed. On removal (or purge, doesn't matter):

(Reading database ... 13338 files and directories currently installed.)
Removing quagga ...
As requested via Debconf, the Quagga daemon will not stop.
dpkg: error processing quagga (--purge):
 subprocess pre-removal script returned error exit status 1
Errors were encountered while processing:
 quagga
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Press return to continue.

Does not prevent other packages installing/configuring. Package removed successfully after changing exit code per suggestion.

Revision history for this message
Mikko Korkalo (keitsi) wrote :

Same problem here. This package is seriously flawed. I'm running Ubuntu 6.06 server on amd64 platform.

I installed quagga normally using "apt-get install quagga". I used it for a while, then stopped the daemon.

Then I tried removing it using "apt-get remove quagga". I lost the exact messages, but here's what happened:
- quagga starts, saying it's executing /etc/init.d/quagga start (I have no idea why)
- dpkg fails to remove quagga with the similar error message reported above by James Green.

Michael Vogt (mvo)
Changed in quagga:
importance: Medium → High
status: Unconfirmed → Confirmed
Revision history for this message
Michael Vogt (mvo) wrote :

I analyzed the situation and the edgy version of quagga does ask a debconf question with priority medium if quagga should be stopped or not. We only show questions with "high" debconf priority.

This is fixed in feisty, but we need to make sure that the prerm script that is run with the failed-upgrade paramter checks $2 and reasks the question with priority "high" on a edgy->feisty upgrade to get things right here.

Revision history for this message
Tollef Fog Heen (tfheen) wrote :

Assign to mvo who has analysed the problem. Please make sure this is fixed for the release.

Changed in quagga:
assignee: nobody → mvo
Revision history for this message
Matthias Klose (doko) wrote :

fixed in quagga_0.99.6-2ubuntu2

Changed in quagga:
assignee: mvo → doko
Matthias Klose (doko)
Changed in quagga:
status: Confirmed → Fix Released
Revision history for this message
Josh Mize (jgmize) wrote :

this bug re-appeared in version 0.99.2-1ubuntu3.1 on my dapper amd64 system when going through the automatic upgrade. I was able temporarily "fix" it on my system by editing /var/lib/dpkg/info/quagga.prerm and changing the "exit 1" to "exit 0" on line 16 as described in the original bug submission (thanks alp).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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