Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Sorry, that was a typo. I am on Debian Unstable. I installed fslint using the following command:
Code:
apt-get install fslint
Ok, but it hasn't been in Debian since Debian 10 (now oldstable). I guess you must have old or third party repositories configured. The output of the following should explain it:
There is an interesting alternative, do not remove the duplicates, but hard link to each other. Useful if you don't know which one is important or you need them in every directory. Works only on a single filesystem.
Ok, but it hasn't been in Debian since Debian 10 (now oldstable). I guess you must have old or third party repositories configured. The output of the following should explain it:
Code:
apt-cache policy fslint
Cheers,
Evo2.
Interesting. I don't think I have it configured for old repositories. Below is what my sources.list has along with the result from the command you recommended:
Code:
root@StarKnight:~# apt-cache policy fslint
fslint:
Installed: 2.46-1
Candidate: 2.46-1
Version table:
*** 2.46-1 100
100 /var/lib/dpkg/status
root@StarKnight:~# cat /etc/apt/sources.list
# Debian packages for unstable
#deb http://mirror.0x.sg/debian/ testing main contrib non-free
deb http://mirrors.kernel.org/debian/ unstable main non-free contrib
root@StarKnight:~#
I first installed it back in 2014 and have never removed it after that. But have been constantly upgrading the system. I think that is why I still have the package even though it is no longer available in the repository.
This should have shown me the repository path and other details about the package and from where it was installed. So it looks like it is no longer there.
This should have shown me the repository path and other details about the package and from where it was installed. So it looks like it is no longer there.
Yeah, seems you installed it before it was booted from Debian :-)
If you still have that on your system, you've probably got a bunch of other old, obsolete stuff lurking around. Might want to look into cleaning it up.
Yeah, seems you installed it before it was booted from Debian :-)
If you still have that on your system, you've probably got a bunch of other old, obsolete stuff lurking around. Might want to look into cleaning it up.
Cheers,
Evo2.
Yup. That sounds like a smart idea. Any suggestions on how to find the old stuff? One option I can think of is to get a list of all the packages installed and run the apt-cache showpkg command on each of them. If the result is blank for the repository location etc then it would indicate an obsolete package. Is there a better/simpler way to do this?
Yup. That sounds like a smart idea. Any suggestions on how to find the old stuff? One option I can think of is to get a list of all the packages installed and run the apt-cache showpkg command on each of them. If the result is blank for the repository location etc then it would indicate an obsolete package. Is there a better/simpler way to do this?
The Debian release notes has a section on this, since they recommend removing such packages before upgrading from one version of Debian to the next. Eg have a look at:
Another option is to use fslint. It is a fantastic program that finds duplicates and allows you to delete/rename them if required. It has both GUI and command line modes but I have only used the GUI mode
Going down the route of apps I have moved to czkawka; an online search takes you to Polish websites but the homepage is https://GitHub.com/qarmin/czkawka . The latest release of 24th April has a feature to find files with the wrong extension. One feature came out after I installed it allows you to choose a folder as containing the originals so they don’t get deleted.
It can be installed in Debian although I don’t think it is in their repositories.
The Debian release notes has a section on this, since they recommend removing such packages before upgrading from one version of Debian to the next. Eg have a look at:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.