Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

sudo apt autoremove

Post Reply
Message
Author
TJ Hoye
Forum Regular
Forum Regular
Posts: 196
Joined: Thu Dec 18, 2014 11:21 pm

sudo apt autoremove

#1 Post by TJ Hoye » Mon Mar 05, 2018 2:50 pm

@ MX-devs

The dist-upgrade process often requires a separate apt autoremove
operation to reclaim some space formerly occupied by outdated material.

Couldn't this separate operation just as well be included as a final step
in the normal dist-upgrade process and not be left as a separate step?

TIA & thanks for this outstanding distro.
64-bit MX-17.1 LiveUSB boot/Frugal install with lz4 remastering, using 4.15.0-1 kernel
on dual-cpu Dell 1545 laptop with 4Gb ram, 200Gb hdd, Broadcom wifi with wl driver, and Intel GM45 Graphics.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 17034
Joined: Fri Dec 15, 2006 8:07 pm

Re: sudo apt autoremove

#2 Post by Stevo » Mon Mar 05, 2018 2:58 pm

You can add it as an option in the MX updater.

Since this command can also destroy a system if a beginner starts messing with metapackages, as it has so many times in the past, I would not add it as an automatic option. People have said, "sure, remove 800 packages? Seems legit" way, way, too many times in the past.

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 10086
Joined: Sun Dec 16, 2007 1:17 pm

Re: sudo apt autoremove

#3 Post by dolphin_oracle » Mon Mar 05, 2018 2:59 pm

we have thought about that in the past. however, a badly packaged deb, or one from an outside repo with conflicting dependency information, can create package conflicts that apt-get has interesting solutions for. like removing all your desktop environment for instance. if we did the autoremove automatically, it could be disastrous, even if we had a confirmation prompt and the user wan't paying real close attention.

better safe than sorry.

***ninja'd by stevo :happy:
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
chrispop99
Forum Guide
Forum Guide
Posts: 2503
Joined: Tue Jan 27, 2009 3:07 pm

Re: sudo apt autoremove

#4 Post by chrispop99 » Mon Mar 05, 2018 3:00 pm

Just to be clear, apt autoremove is not a required step, only an optional one.

With the size of disks currently in use, the relative amount of free space recovered is minimal, and it's something I have never bothered with.

Chris
Test machines:
32-bit non-PAE - Thinkpad T41, 1.6GHz Pentium M, 1GB RAM.
32-bit PAE - DELL Latitude D610, 1.73GHz Pentium M, 2GB RAM.
64-bit - Lenovo T61, 2GHz Core 2 Duo, 2GB RAM
64-bit - Gigabyte Z77P-D3, Intel i3-3220, GeForce 8400 GS, 4GB PC3-12800.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 17034
Joined: Fri Dec 15, 2006 8:07 pm

Re: sudo apt autoremove

#5 Post by Stevo » Mon Mar 05, 2018 3:05 pm

You can also use aptitude to manage packages, which will autoremove by default. Luckily, it asks first before proceeding to nuke your system.

TJ Hoye
Forum Regular
Forum Regular
Posts: 196
Joined: Thu Dec 18, 2014 11:21 pm

Re: sudo apt autoremove

#6 Post by TJ Hoye » Mon Mar 05, 2018 8:35 pm

Thanks to all for your cautionary advice.

I know its a terrabyte world for most folks, but I'm exclusively 'live'.
My Cruzer world is at most only 16 Gb of which I usually use only a few Gb
for my LiveUSB. Happily so with MX. It's a delight. Still...

The mere thought of a few Kb going to no good use seems like something
to respond-to. And...

It does seem a little inconsistent to take all of the automatic, unchallenged
changes in any given dist-upgrade on faith that nothing bad might happen,
yet be hesitent about the suggestions on recouping some unused space after
all the magic of the upgrade has occurred.

I get it. I'll not automatically autoremove.

TJH
64-bit MX-17.1 LiveUSB boot/Frugal install with lz4 remastering, using 4.15.0-1 kernel
on dual-cpu Dell 1545 laptop with 4Gb ram, 200Gb hdd, Broadcom wifi with wl driver, and Intel GM45 Graphics.

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 10086
Joined: Sun Dec 16, 2007 1:17 pm

Re: sudo apt autoremove

#7 Post by dolphin_oracle » Mon Mar 05, 2018 8:40 pm

TJ Hoye wrote:Thanks to all for your cautionary advice.
....

It does seem a little inconsistent to take all of the automatic, unchallenged
changes in any given dist-upgrade on faith that nothing bad might happen,
yet be hesitent about the suggestions on recouping some unused space after
all the magic of the upgrade has occurred.

I get it. I'll not automatically autoremove.

TJH
ah, but remember grasshopper, our default updater settings let you look at the updates before they are installed. this can also point out bizzare conflicts.

the options are there if you want to use them dude. autoremove just isn't the default.
You do not have the required permissions to view the files attached to this post.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
Jerry3904
Forum Veteran
Forum Veteran
Posts: 23028
Joined: Wed Jul 19, 2006 6:13 am

Re: sudo apt autoremove

#8 Post by Jerry3904 » Mon Mar 05, 2018 8:51 pm

I love that feature!
Production: 4.15.0-1-amd64, MX-17.1, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 8 GB, SSD 120 GB, Data 1TB
Testing: AAO 722: 4.15.0-1-386. MX-17.1, AMD C-60 APU, 4 GB
Personal: XPS 13, 4.18.0-19.3-liquorix, 4 GB

Post Reply

Return to “Package Requests/Status - MX 17”