On 28-07-17, Greg Wooledge wrote: > On Fri, Jul 28, 2017 at 05:39:39PM +0200, Dejan Jocic wrote: > > So, same question as above, did and of those they messed up? Are there > > opened bugs that autoremove from any of used tools in debian removes > > packages it should not? And qualifications for that statement are years > > of use of both apt-get and aptitude with autoremove following > > update/upgrade. Never had any trouble with it. > > The concern is that you may have used some shared library to compile a > third-party program which is installed in /usr/local or /opt, or anywhere > else that's outside of Debian's knowledge. Debian would not know that > the library is still being used, and therefore might autoremove it. > > The impact of this is directly proportional to how many things you > compile yourself, and how important those things are to you. >
If you manually installed shared library, did autoremove removed it/proposed to removed it? Or, it was installed as dependency of some other package that you removed? If former, it is bug. If later, you should have mark it as manually installed, if your compiled software depends on it. Also, if you compile third party programs, there are ways to make debian packages out of them and keep yourself and your preferred debian package tool happy. Just saying.
