You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
debugedit funnelweb git-core kpartx liblua5.2-0 libnspr4 libnss3 librpm3 librpmbuild3 librpmio3 librpmsign3 python-egenix-mxtexttools python-egenix-mxtools python-pexpect python-ptyprocess python-smartpm rpm
rpm-common rpm2cpio smartpm-core
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
pdk* pdk-mediagen*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 1,564 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 49213 files and directories currently installed.)
Removing pdk (1.0.0~alpha1) ...
dpkg: warning: while removing pdk, directory '/usr/lib/python2.7/dist-packages/picax' not empty so not removed
dpkg: warning: while removing pdk, directory '/usr/lib/python2.7/dist-packages/pdk/xml_legacy/utils' not empty so not removed
dpkg: warning: while removing pdk, directory '/usr/lib/python2.7/dist-packages/pdk/xml_legacy/sax' not empty so not removed
dpkg: warning: while removing pdk, directory '/usr/lib/python2.7/dist-packages/pdk/xml_legacy/parsers/xmlproc' not empty so not removed
Processing triggers for man-db (2.7.6.1-2) ...
The text was updated successfully, but these errors were encountered:
I will look into that, thanks for the tip!. Usually I handle this kind of thing via the debian/postrm file because it enables you to have different actions for remove versus purge of the package. A purge should leave nothing behind, but in some cases you want the remove to leave certain parts intact to support a later install.
The text was updated successfully, but these errors were encountered: