520278 - dpkg --purge does not work correctly for Fennec

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[Armen [:armenzg]]

Attachment: log from different actions against dpkg

Reproducible: Probably always
1) ssh to device
2) dpkg --purge fennec

The error is that it can't remove /usr/local/fennec since it is not empty. It contains extensions and updates.

In the man page below mentions the steps involved when purging. I bet this is related with why bug 520171 does not complete a second installation of Fennec.

I have also attached the log of running dpkg with different actions.

### Output when trying to purge
Nokia-N810-43-7:~# dpkg --purge fennec
(Reading database ... 15697 files and directories currently installed.)
Removing fennec ...
dpkg - warning: while removing fennec, directory `/usr/local/fennec' not empty so not removed.

### Version of dpkg on Nokia N810
Nokia-N810-43-7:~# dpkg --version
Debian `dpkg' package management program version 1.14.7maemo5 (armel).
This is free software; see the GNU General Public License version 2 or
later for copying conditions. There is NO warranty.
See dpkg --license for copyright and license details.

### From dpkg's man page (NOTE that this man page is from "1.10.28 (i686-darwin)"):

       dpkg -r | --remove | -P | --purge package ... | -a | --pending
              Remove an installed package.  -r or --remove  remove  everything
              except  configuration files.  This may avoid having to reconfig-
              ure the package if  it  is  reinstalled  later.   (Configuration
              files  are  the  files  listed  in  the debian/conffiles control
              file).  -P or --purge removes everything,  including  configura-
              tion  files.   If  -a or --pending is given instead of a package
              name, then all packages unpacked, but marked to  be  removed  or
              purged  in  file  /var/lib/dpkg/status,  are  removed or purged,
              respectively.

              Removing of a package consists of the following steps:

              1. Run prerm script

              2. Remove the installed files

              3. Run postrm script

Comment 1

[Armen [:armenzg]]

The same happens for xulrunner:

Nokia-N810-43-7:~# dpkg -l xulrunner
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name                      Version                   Description
+++-=========================-=========================-==================================================================
ii  xulrunner                 1.9.2b1pre-20091002010458 XUL runtime package
Nokia-N810-43-7:~# dpkg --purge xulrunner
(Reading database ... 15654 files and directories currently installed.)
Removing xulrunner ...
Purging configuration files for xulrunner ...
dpkg - warning: while removing xulrunner, directory `/usr/local' not empty so not removed.
dpkg - warning: while removing xulrunner, directory `/etc/gre.d' not empty so not removed.

Comment 2

[Antonio Gomes (tonikitoo)]

armen, see comments in bug 450434 and bug 455350

Comment 3

[Armen [:armenzg]]

I wonder why it mentions alpha values.
Nokia-N810-43-7:~# cat /etc/gre.d/1.9.2a*
[1.9.2a1pre]
GRE_PATH=/usr/local/lib/xulrunner-1.9.2a1pre
xulrunner=true
abi=[1.9.2a2pre]
GRE_PATH=/usr/local/lib/xulrunner-1.9.2a2pre
xulrunner=true


I just realized that I might be hitting this since I borrowed this Nokia N810 and whoever used it might have used the alpha installers from the tar balls since there were no deb files at that time. This makes really likely that this bug and bug 520171 might be invalid.

Comment 4

[BMO Automation]

Closing all opened bug in a graveyard component