The deb names may be unconventional but the executables worked (at least v4.2.8 worked).
Can you please suggest suitable Debian package management commands to use to investigate the current status of the v4.2.8 and v4.3.1 data in the Debian system. On Thu, Jan 30, 2025, 4:26 PM <to...@tuxteam.de> wrote: > On Thu, Jan 30, 2025 at 04:14:00PM +0000, Michael wrote: > > Thanks very much for your help and suggestions. > > > > I am running Debian 12 on a desktop. > > > > My aim is to set up and use a TOTP authenticator app called Ente Auth. > > > > I ran, as root :- > > > > dpkg -i ente-auth-v4.2.8-x86_64.deb > > [...] > > > dpkg -i ente-auth-v4.3.1-x86_64.deb > > I don't know who packaged this, but at least they don't seem to > know how to make a Debian package. The names seem to suggest > different versions of the "same" package, but as far as Debian > is concerned, they are just totally different packages. > > See here [1] for how Debian packages are supposed to be named. > In short, <package>_<version>_<architecture>.deb, separated > by underscores. > > Possibly, ente-auth_v4.2.8_x86_64.deb might be a good package > name (but we don't know what on earth is *in* those things, that > might be as wrong as the name!) > > A newer version will replace the older version's files. In your > case, if you try to install the second one... > > > This should overwrite the previous executable enteauth. > > ...and it tries to overwrite files installed by the first one, > you *should* have got an error message from dpkg. Did you? > > Cheers > > [1] > https://www.debian.org/doc/manuals/debian-faq/pkg-basics.en.html#pkgname > -- > t >
