On Sunday 14 July 2024 10:51:07 Mike Bird via tde-users wrote:
On Sun July 14 2024 10:41:28 William Morder via tde-users wrote:
I don't know if this will solve my problem, though, as I already save all my downloaded and installed packages (for situations just like this), and everything seems up-to-date.
If you have a saved copy of your "apt" package you can just reinstall it with "dpkg -i ..." without downloading it again.
--Mike
Okay, so progress is sometimes made in baby steps, and I hope this is some progress.
I used dpkg to purge all the apt-* type packages in my system, to wit:
sudo dpkg --purge --force-all apt-transport-https apt-utils apt-file_3.3_all apt-mirror_0.5.4-2_all apt-transport-https_2.6.1devuan1_all apt-utils_2.6.1devuan1_amd64 apt_2.6.1devuan1_amd64 aptitude-common_0.8.13-5_all aptitude_0.8.13-5_amd64 devuan-apt-mirror-config-override_2.6_all dpkg-repack_1.52_all libapt-pkg-perl_0.1.40+b2_amd64 synaptic_0.91.3_amd64 apt_2.6.1devuan1_amd64
Then I figured that I would reinstall them one-at-a-time, using dpkg, or moving to apt, aptitude, whatever, to finish up.
I already had the package you named, but I thought, well, let's download a fresh one, just to be sure mine isn't corrupt. Now ... mind you ... I had already purged the old package from my system. Yet when I tried to reinstall apt-utils_2.6.1devuan1_amd64, I get this message:
dpkg: version 2.6.1devuan1 of apt already installed, skipping
So, it is uninstalled, yet it is also already installed? There must be some traces left in the system that makes dpkg say it is already installed. Maybe this is a clue; maybe even a useful clue.
Bill
P.S. I will be out this afternoon, so I may not reply until later this evening.