Quote:
Quote:
Quote:
|
Yes, no error or warning output from either command is good. You should run both commands (dpkg: not for specific packages but for your whole system as it was given), whether you think you need to or not.
I don't know the equivalent in Synaptic because I don't use it, to be honest. I just wanted to check your package basics, given that you had experienced problems with the package manager's directories and the lock file. Your software sources next? Code:
cat /etc/apt/sources.list{,.d/*} |
I thought so. That is good, but I wanted to confirm.
About your command, see some output from my terminal now. The command I used is inspired in yours: Code:
me@here: /dev/shm (LQ Debian 9 (stretch) - why 'apt-get update' cannot write tmp files?) Debian 9 - why 'apt-get update' cannot write tmp files? (: |
Nice adaptation of the command. :) For interest, if you install inxi, then inxi -r produces a nice repository listing.
Referring to the example sources.list at https://wiki.debian.org/SourcesList#...e_sources.list: given that you have decided not to include the contrib and non-free repos, that you have decided to disable the debian-security updates (why is that, out of interest? - I would have thought those were important) and, very pedantically, that you don't need the forward slash at the end of the urls, e.g. http://deb.debian.org/debian, all appears to look normal. So, on to the next stage: checking that all your packages are fully installed: Code:
dpkg -l | grep -v "^ii" |
Forgot to say before! 'apt-get check' reported no problem - just the successful progress lines.
Another small comment, to use just one post: most of the time, I prefer Synaptic instead of aptitude (not so easy and fluid interface) or the apt/dpkg commands. And I am thinking about asking the question: " 'apt-get check' and/or 'dpkg --audit' are done automatically by Synaptic?" in its mailing list. You are right. Updates are not important for me, but I enabled security repos. Indeed a silly idea of "who" commented that... inxi... never heard that name. Less than 600KiB? I installed it. :D But the problem happened again, exactly like I said in #3. The package had no dependencies and was installed fine - apparently normally, since we found no problem since I started this thread, except the (before) absent partial folder. I repeated/done a few commands now: Code:
sudoed@here /dev/shm /-: |
I do not understand you. in post #3 you explained the following:
Quote:
This problem is not related to the apt database and package consistency at all, therefore the commands posted/tried will not address it. Actually I don't know what permission is missing from where (if the download was successful but the result was unreadable, or it was not downloaded at all). The missing dir /var/cache/apt/archives/partial is a clear sign: your installation (at least the apt related structure) is corrupted, damaged. This may cause a huge amount of different and diverse error messages. I don't know how serious is it and if there was any way to find and fix all of these failures. apt itself will not able to detect them (it assumes the system was properly installed). By the way reinstalling apt (with dpkg) may help. |
Until we've finished checking your system, you shouln't be using Synaptic. We're only half-way through. We will probably end up reinstalling Synaptic manually anyway (and, if necessary, apt etc. as pan64 mentions).
So, with that in mind, if you could run the command in post #19, that would be great. |
dpkg -l | grep -v "^ii"
Command output:
Code:
$ dpkg -l | grep -v "^ii" |
probably some google on it?
https://askubuntu.com/questions/1880...ike-ii-rc-mean |
"rc" means that you have removed a package but have not yet purged its residual configuration.
Which leads me to the question, why have you deleted pulseaudio and ffmpeg - did you have specific problems? I would expect these two packages to be present on a normal Mint/Ubuntu system, and perhaps a Debian one too (although I don't know much about Debian so can't be sure). If these have been deleted intentionally, then we can continue with the purging of the packages. Either you can do this manually, one by one, with: Code:
sudo apt-get purge package_name Code:
sudo apt-get purge $(dpkg -l | grep '^rc' | awk '{print $2}') |
sorry guy, it is out of topic here, but do not need to use grep:
Code:
sudo apt-get purge $(dpkg -l | awk '/^rc/ {print $2}') |
Quote:
|
Files to check when each package was touched are just "/var/log/dpkg.log*" ?
Quote:
I had not deleted or uninstalled those packages. The strangest thing, and probably the only one related to installed programs and packages, that happened to my computer is that I installed skype for linux in it. Without the dependencies being clearly pointed before installing (id est, they were not mentioned in the official page where I downloaded the installed package from). After installing it, I noted that several things, that I did not have, were installed. Wine is one - this is why I think that what I run today is the same that win users run. I need examine my systems logs to point exactly which packages were added before (a few minutes, at most) skype was first installed. Thank you also for saying what 'rc' in that context means. "residual configuration" -> So it is not as bad as I imagined from what you all said. Do any of you reading here think that this information (and others related) should be added to the dpkg documentation? A new bug report for that is a good idea? I want to find what happened to uninstall packages. In the last week, I was about to install [something] and aptitude said that several packages needed to be updated. I found that very strange! The files I need to look to check when each package I have were installed or removed are just "/var/log/dpkg.log*" ? Do those include all things installed in every possible ways, like synaptic, aptitude, etc.? |
@pan64 in #24: I did try to find the answer before posting here
@pan64 in #24: I did try to find the answer before posting here.
And I will write free ads just to search engines with good principles. |
Offtopic question: awk '/^rc/' will accept which regexes?
Offtopic question:
The command awk '/^rc/' will accept any regex between the slashes? Which regex standard (or type)? I am thinking about the categories of regexes that grep uses, depending on a few switches it has. Since a single quote was used for the command above, no escaping should be needed for any kind of symbols. Right? |
All times are GMT -5. The time now is 01:42 PM. |