[SOLVED] spacefm 1.0.6 upgrade-error in MX-17.1

[fehlix]

Hmm... ok we have now version spacefm version 1.0.6-1.1~mx17+1.
The installation/upgrade went fine.
But... trying to remove spacefm results now in a situation
where apt can't remove this package.

Code: Select all

 
apt-get remove spacefm
...
Removing spacefm (1.0.6-1.1~mx17+1) ...
postrm called with unknown argument `remove'
dpkg: error processing package spacefm (--remove):
 subprocess installed post-removal script returned error exit status 1
Errors were encountered while processing:
 spacefm
E: Sub-process /usr/bin/dpkg returned an error code (1)
 

Further trying the fix the defect package with

Code: Select all

 apt-get install -f 

issues the same error message.

I've cleared the apt-error for now by reinstalling previous version with

Code: Select all

 apt-get install spacefm=1.0.5-2 spacefm-common=1.0.5-2 

followed by upgrading again to 1.0.6-1.1~mx17+1
with:

Code: Select all

 apt-get upgrade 

To summarize: The current deb-package spacefm_1.0.6-1.1~mx17+1_amd64.deb
still has a broken postrm-controll-file due to missing remove-tag.

[anticapitalista]

I removed the package from the antiX repo.

You could try deleting that spacefm postrm file in /var/lib/dpkg/info

Note the antiX main repo is down at the moment.

[fehlix]

I removed the package from the antiX repo.

Yes I noticed that yesterday already.
I guess we have it now as mx-package which Stevo might just have generated.

Code: Select all

LANG=C apt policy spacefm
spacefm:
  Installed: 1.0.6-1.1~mx17+1
  Candidate: 1.0.6-1.1~mx17+1
  Version table:
 *** 1.0.6-1.1~mx17+1 500
        500 https://ftp.fau.de/mxlinux-packages/mx/repo stretch/main amd64 Packages
        100 /var/lib/dpkg/status
     1.0.5-2 500
        500 http://ftp2.de.debian.org/debian stretch/main amd64 Packages

Perhabs I need to learn to create / build packeges within your environment so I might help you guys ( in the future ).

[anticapitalista]

Ok, does a manual removal of that postrm file work?

[anticapitalista]

If it doesn't then the postrm script needs to look like this:

Code: Select all

#!/bin/sh
# postrm script for spacefm-gtk2
#
# see: dh_installdeb(1)

set -e

# summary of how this script can be called:
#        * <postrm> `remove'
#        * <postrm> `purge'
#        * <old-postrm> `upgrade' <new-version>
#        * <new-postrm> `failed-upgrade' <old-version>
#        * <new-postrm> `abort-install'
#        * <new-postrm> `abort-install' <old-version>
#        * <new-postrm> `abort-upgrade' <old-version>
#        * <disappearer's-postrm> `disappear' <overwriter>
#          <overwriter-version>
# for details, see http://www.debian.org/doc/debian-policy/ or
# the debian-policy package


case "$1" in
    remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
	if which update-mime-database >/dev/null 2>&1 && which update-desktop-database >/dev/null 2>&1; then
        update-mime-database /usr/share/mime > /dev/null
        update-desktop-database -q
        fi
    ;;

    purge)
        #fix 782975
        rm -rf /etc/spacefm
    ;;

    *)
        echo "postrm called with unknown argument \`$1'" >&2
        exit 1
    ;;
esac

# dh_installdeb will replace this with shell code automatically
# generated by other debhelper scripts.

#DEBHELPER#

exit 0

[fehlix]

Ok, does a manual removal of that postrm file work?

Yes, afte removing postrm via

Code: Select all

mv  /var/lib/dpkg/info/spacefm.postrm /tmp

I could un-install the package and apt didn't complain anymore about defect package

Code: Select all

apt-get install -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

So yes removing the postrm ( /var/lib/dpkg/info/spacefm.postrm ) cured the symptom.

[fehlix]

If it doesn't then the postrm script needs to look like this:

Code: Select all

#!/bin/sh
# postrm script for spacefm-gtk2
#
# see: dh_installdeb(1)

set -e

# summary of how this script can be called:
#        * <postrm> `remove'
#        * <postrm> `purge'
#        * <old-postrm> `upgrade' <new-version>
#        * <new-postrm> `failed-upgrade' <old-version>
#        * <new-postrm> `abort-install'
#        * <new-postrm> `abort-install' <old-version>
#        * <new-postrm> `abort-upgrade' <old-version>
#        * <disappearer's-postrm> `disappear' <overwriter>
#          <overwriter-version>
# for details, see http://www.debian.org/doc/debian-policy/ or
# the debian-policy package


case "$1" in
    remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
	if which update-mime-database >/dev/null 2>&1 && which update-desktop-database >/dev/null 2>&1; then
        update-mime-database /usr/share/mime > /dev/null
        update-desktop-database -q
        fi
    ;;

    purge)
        #fix 782975
        rm -rf /etc/spacefm
    ;;

    *)
        echo "postrm called with unknown argument \`$1'" >&2
        exit 1
    ;;
esac

# dh_installdeb will replace this with shell code automatically
# generated by other debhelper scripts.

#DEBHELPER#

exit 0

Yes exactly! This is the correct postrm which I yesterday used to fix the deb manually.
This postrm need to go into the mx-deb package spacefm_1.0.6-1.1~mx17+1_amd64.deb.

[Stevo]

???? Why would anyone ever want to remove one of my packages! Treason!!!!!

OK, the fix will be easy, so I'll roll out a new version.

The upstream maintainer may have changed the script to add a feature that only a newer version of dpkg can recognize.

Sent the packages up to main, but they are here too for a while: https://drive.google.com/open?id=1ER0qd ... -ncrAMwtfb

I also fixed the spacefm-gtk3.postrm script the same way.

[fehlix]

???? Why would anyone ever want to remove one of my packages! Treason!!!!!

Indeed a good question . I do have spacefm installed on all my nn++ linux system with different DE's since version 0.8 which is about 5 years ago. And I've never un-installed it. I do also run antiX mainly with spacefm. Sometimes I do even use XFCE with spacefm-desktop-manager which is another cool feature by spacefm.
Anyway thanks. Stevo!

[fehlix]

Sent the packages up to main
...
I also fixed the spacefm-gtk3.postrm script the same way.

As the fixed version did not yet arrived here in the german repo-mirror

Code: Select all

LANG=C apt policy spacefm
spacefm:
  Installed: 1.0.6-1.1~mx17+2
  Candidate: 1.0.6-1.1~mx17+2
  Version table:
 *** 1.0.6-1.1~mx17+2 100
        100 /var/lib/dpkg/status
     1.0.6-1.1~mx17+1 500
        500 https://ftp.fau.de/mxlinux-packages/mx/repo stretch/main amd64 Packages
     1.0.5-2 500
        500 http://ftp2.de.debian.org/debian stretch/main amd64 Packages

I just switched to the mirror in Utah

Code: Select all

 LANG=C apt policy spacefm
spacefm:
  Installed: 1.0.6-1.1~mx17+2
  Candidate: 1.0.6-1.1~mx17+2
  Version table:
 *** 1.0.6-1.1~mx17+2 500
        500 http://mxrepo.com/mx/repo stretch/main amd64 Packages
        100 /var/lib/dpkg/status
     1.0.5-2 500
        500 http://ftp2.de.debian.org/debian stretch/main amd64 Packages

and the fixed spacefm installs and runs perfectly!

Thanks indeed Stevo for your swift actions!