15 Jul
2024
15 Jul
'24
3:32 p.m.
On Mon July 15 2024 08:01:40 William Morder via tde-users wrote:
On Sunday 14 July 2024 13:59:41 Mike Bird via
tde-users wrote:
Those are the exact package names (less the extension, .deb) of those in my
folder of saved packages having to do with apt. When I reinstall them,
nothing much changes, just the same message.
A file name is not a package name. A file name includes a package name,
a version, an architecture, and more.
dpkg -i (install) uses file names.
dpkg --purge and apt use package names.
Hi Bill,
On Sun July 14 2024 13:15:02 William Morder via tde-users wrote:
But when I tried reinstalling a new apt package (which was the same name as
my saved one), I still got that same message.
I used dpkg to purge all the apt-* type packages
in my system, to wit:
Not recommended. TTBOMK only your apt package is broken. 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
Many of those are partial file names, not package names, so I
don't know how much it actually did. The package names themselves were copied directly from
those packages.
sudo dpkg -l | grep apt | cut -b-78
Here is the output:
iU apt 2.6.1devuan1
ii apt-config-icons 0.16.1-2
iU apt-file 3.3
ii apt-listchanges 3.24
ii apt-mirror 0.5.4-2
iU aptitude 0.8.13-5
ii aptitude-common 0.8.13-5
ii devuan-apt-mirror-config-override 2.6
ii feedbackd 0.0.3-1
ii klaptopdaemon-trinity
4:14.1.2-0debian12.0.0 ii kmilo-trinity
4:14.1.2-0debian12.0.0 ii laptop-detect
0.16
ii libaec0:amd64 1.0.6-1+b1
ii libapt-pkg-perl 0.1.40+b2
ii libapt-pkg6.0:amd64 2.2.4+devuan1
ii libatk-adaptor:amd64 2.46.0-5
ii libcapture-tiny-perl 0.48-2
ii libfeedback-0.0-0:amd64 0.0.3-1
ii libfreeaptx0:amd64 0.1.1-2
ii liblavfile-2.1-0:amd64 1:2.1.0+debian-7
ii liblavjpeg-2.1-0:amd64 1:2.1.0+debian-7
ii liblavplay-2.1-0:amd64 1:2.1.0+debian-7
ii libmjpegutils-2.1-0:amd64 1:2.1.0+debian-7
ii libmpeg2encpp-2.1-0:amd64 1:2.1.0+debian-6
ii libmplex2-2.1-0:amd64 1:2.1.0+debian-6
ii libopencore-amrnb0:amd64 0.1.6-1
ii libopencore-amrwb0:amd64 0.1.6-1
ii libpcap0.8:amd64 1.10.3-1
ii libraptor2-0:amd64 2.0.15-4
ii libsz2:amd64 1.0.6-1+b1
ii mjpegtools 1:2.1.0+debian-7
ii mjpegtools-gtk 1:2.1.0+debian-7
ii python-apt-common 2.6.0
ii python3-apt 2.6.0
ii python3-wrapt 1.14.1-2+b2
ii r-cran-doparallel 1.0.17-1
ii r-cran-earth 5.3.2-1
ii r-cran-maptools 1:1.1-6+dfsg-1
ii r-cran-rcmdcheck 1.4.0-2
iU synaptic 0.91.3
ii task-laptop 3.73devuan1
I am dying to hear what's up.
Please show me exactly what happens when as root and in the directory
containing this package file you do:
dpkg -i apt_2.6.1devuan1_amd64.deb
--Mike
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
Probably because your purge was told to purge apt_2.6.1devuan1_amd64
which is not a package name.
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.
"dpkg -l | grep apt | cut -b-78" will tell us where things stand.
--Mike