[13:37] <OvenWerks> Eickmeyer[m]: it sounds like a good sw updater is more difficult than thought?
[14:21] <Eickmeyer[m]> OvenWerks: Yeah. This is going to require some collaboration, which is OK. we can't do this on our own.
[14:25] <Eickmeyer[m]> Ubuntu Flavors aren't an island. We should always be collaborating with each other. The idea of being separate from the rest of Ubuntu isn't a thing. Tribalism gets us nowhere. The more we work together, the better things are for everyone.
[14:25] <Eickmeyer[m]> What I thought was funny was it attracted the attention from KDE (Neon) and Fedora.
[14:27] <OvenWerks> :)
[17:10] <Eickmeyer[m]> OvenWerks: FYI, the update-manager autoremove tells you exactly what it's removing and gives you the option to unselect stuff to keep it from removing it.
[17:48] <OvenWerks> Thats good. Is there also a way to flag packages set to auto remove as user installed?
[17:49] <OvenWerks> otherwise they remain in the autoremove list
[18:45] <Eickmeyer[m]> OvenWerks: Only way I know of to do that is "apt-mark manual {package}".
[18:51] <OvenWerks> exactly
[18:53] <OvenWerks> a GUI that shows a list of autoremove packages should have two check marks, one for yes remove and a second for keep this package. One could even argue, though I am not sure they would be right, that anything that remains un checked for removal, should be marked manual
[18:54] <OvenWerks> The main reason for not marking unchecked packages as manual, is that there is no "I don't want to make this decision right now button"  :)
[19:03] <Eickmeyer[m]> That sounds like a feature enhancement request, which is a form of bug report.
[19:03] <Eickmeyer[m]> That said, it would come up on the next time upgrade-manager runs.
=== arraybolt3_ is now known as arraybolt3
=== arraybolt3_ is now known as arraybolt3