Hello,
I'm trying to delete a package, purge its configuration files and remove its unused dependencies from Webmin->Software Packages.
-In "Installed Packages" section, I insert "libplack-perl" near "Search for Package:" button and I click on this button.
-In "Edit Package" section, I click on "Uninstall" button.
-On "Delete Package" section, I get: "Are you sure you want to delete the package libplack-perl ? Up to 234 files (575027 bytes) will be deleted forever.", I select "Yes" near the "Purge configuration files?" and I select "Yes" near "Removed unused dependencies as well?". Then I click on Delete button.
After the process described above, I get this error:
Error
Failed to delete package libplack-perl :
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
libcgi-compile-perl* libcgi-emulate-psgi-perl* libclass-inspector-perl*
libdevel-stacktrace-ashtml-perl* libfile-pushd-perl* libfile-sharedir-perl*
libfilesys-notify-simple-perl* libhash-multivalue-perl* libhttp-body-perl*
libmodule-refresh-perl* libpath-class-perl* libplack-perl*
libtest-requires-perl* libtest-sharedfork-perl* libtest-tcp-perl*
libyaml-libyaml-perl* libyaml-perl*
0 upgraded, 0 newly installed, 17 to remove and 0 not upgraded.
After this operation, 2207 kB disk space will be freed.
Do you want to continue [Y/n]? Abort.
I'm sure the problem is the unanswered question from the system (Webmin). A "Y" in this case.
Do you know a solution to uninstall via webmin?
Best Regards
Maurizio
Comments
Submitted by Maurizio1230 on Thu, 11/28/2013 - 17:33 Comment #1
Same problem with packages without dependencies, BUT ONLY IF SELECT "YES" NEAR "REMOVE UNUSED DEPENDENCIES AS WELL"!!!
If I select "No" near "remove unsed dependencies as well", webmin removes it!
Submitted by JamieCameron on Fri, 11/29/2013 - 04:49 Comment #2
Thanks for pointing this out - Webmin should be running
apt-get autoremove
with the-y
flag to skip prompting. I'll fix this in the next release.Submitted by Issues on Fri, 12/13/2013 - 18:21 Comment #3
Automatically closed -- issue fixed for 2 weeks with no activity.